Hello!
I have existing DOM instances (around 1000). I recently added section definitions to extend the model with new fields.
When I create a new instance, I can see the new sections and fields correctly in the form component. However, when editing older instances, the new sections and fields are not visible in the form component.
Also, if I try to edit and save an existing instance, I get an error related to empty sections.
(See screenshot)
Do you have any workaround to fix this issue, or is it necessary to create a migration script (adding new section to existing instances)?
Hi Kévin,
This is unfortunately a known issue where the form component will not show the fields for a section, for which no actual section already exists on the DOM instance. Since by default, a section is mandatory when a SectionDefinition is reference on the DOM definition, the form then also complains that no section was provided.
If you do not need to enter data for these new SectionDefinitions on the existing DOM instances, you could opt to mark having Sections for the SectionDefinitions optional on the link in the DOM definition. That will stop the UI from blocking updates on the existing fields.
However, if you need to enter & see values of these new SectionDefinitions, you will indeed have to create a migration script that will have to add at least one empty section for these SectionDefinitions to the existing DOM instances. (with a value for the required fields as well then if applicable)
We'll evaluate internally if this issue should be bumped in priority.
Hi Thomas,
Thanks for your feedback. I hope you’ll be able to find a solution to this problem. I’ve decided to use an Automation Interactive Script to move forward.
Regards
Kévin