(No) Bug in DT3.5: custom data

Hello,

creating custom data fields leads to errors on present custom data fields. It looks like new custom data is written in the wrong section in the plist-file because when disabling one cd-column another one disappears too (this issue has been fixed two times in 2019, i think :wink: )…

Thanks!
Chris

Actually only once and version 3.5 didn’t change custom metadata at all, maybe it’s a relict of custom metadata definitions dating back to earlier versions/betas? A copy of the file ~/Library/Application Support/DEVONthink 3/CustomMetadata.plist might be useful.

It’s strange. After opening the plist file and adding/deleting some custom data fields everything is ok now.

Thanks for helping with the magic hand…

The file would be nonetheless useful if this should happen again.

I checked the plist file from my yesterday backup an compared the content with the actual file, but didn’t find any obvious issues…

CustomMetaData.plist.zip (1.2 KB)

The file seems to be okay.