set-form-fields

To replace form fields on a NovaDB form object, you perform a complete ordered replacement of attribute 5053 for typeRef 50 objects using the novadb_cms_update_objects tool, ensuring each field is an individual CmsValue entry with incrementing sortReverse values.

The safest way to enforce precise field ordering during a form migration is to replace the entire form field list at once, providing each field as an individual CmsValue entry with incrementing sortReverse values to prevent array-based mistakes and accidental deletions.

Form field replacement fails with array values because the attribute 5053 replacement requires individual CmsValue entries for each field with incrementing sortReverse values, preventing array-based mistakes and ensuring deterministic ordering across the novadb_cms_update_objects transaction.

Yes, you can use novadb_cms_update_objects to restore canonical field sets across branches by performing a full replacement transaction of attribute 5053 on the target Form objects to enforce precise field membership and ordering.

You need to replace the complete ordered list of fields on an existing NovaDB form during schema migrations, form redesigns, or when restoring canonical field sets to avoid inconsistent form definitions and manual edits.

Yes, replacing form fields with attribute 5053 requires individual CmsValue entries for each field using incrementing sortReverse values to ensure deterministic ordering and prevent accidental deletions during the novadb_cms_update_objects transaction.