Currently, if there is a one-way AutoCAD title block system property mapping from Vault that changes during release, it will not properly populate the title block upon job server property synchronization during release unless "create" is set to "Yes".
This works if there is only one title block. If there are multiple title blocks listed in the property mapping list however, there is a permanent noncompliant equivalence error for that item because the other blocks do not exist in that file.
The idea is to have an option that creates the entry, but only if the attribute exists in the file. Alternatively, allow the property noncompliance check to ignore attributes that cannot be created because it does not exist in the file. This would allow for the same property to populate different title blocks depending on the file without Vault being angry.
Support case reference: 14762667
Forum reference: https://forums.autodesk.com/t5/vault-forum/job-processor-property-synchronization-issue-quot-initial...