With the latest DM feature release, we transitioned creation of DOM instances with multiple sections from ViewStructure to the new AllowMultipleSections field on the DefinitionLink. This has worked and allowed for successful creation of instances in the low-code app. However, code that worked previously for creating multiple sections in an instance now no longer works, returning the “MultipleSectionsNotAllowedForSectionDefinition” error.
I have double checked, recreated the DOM Instances, and the AllowMultipleSections field is set on the SectionDefinitionLink and/or the DomStatusSectionDefinitionLink (tried all combinations). Also checking the RawView via ClientTest shows the AllowMultipleSections = true.
Any ideas as to the issue I’m having creating the instances? Thanks in advance.
If you are using a status system, then you will have to set the AllowMultiple Sections property to true in the DomStatusSectionDefinitionLink when creating the definition (as you already did). See RN here.
And then, when creating the instance via code, make sure to also set the statusId to the DomInstance object, as shown below:
DomInstance domInstance = new DomInstance
{
DomDefinitionId = DomDefinition.ID,
StatusId = “draft”,
};
Hi Blake, you are right to be surprised, and so were we (DOM team). It seems that you have actually found a little bug. Nice! We have already fixed it & is waiting on the quality assurance. By default, you are not required to assign a status. The initial status should be filled in, but the order is incorrect when using the multiple sections feature. Thanks for reporting. 🙂
Quick update. The fix has been merged. It will be available in DataMiner main release version 10.4.0 and feature release 10.3.6.
That worked! A bit surprised but after a quick test that seemed to create the instance correctly.