Hi As it turns out the problem is NOT the curly brackets but rather the internal double quotes.
- Andy > On Feb 1, 2021, at 12:05 PM, Andreas Schaefer <schaef...@me.com.INVALID> > wrote: > > Hi > > If I try to create a property with a curly brackets in it then the parsing > fails: > > set properties on /var/dxml/folderprofiles > set globalDefaultConfigs{String} to \"{\"type\":\"one\"}\" > end > > I tried to escape the curly brackets with \{ and \} but to no avail. > > Is there a way to use unicode or ascii codes or any other way to fix it? > > Should this be considered a bug as curly brackets in a string properly is a > valid value? If so I will create a ticket for it. > > - Andy