parentId of OPT-300-Procedure-SProvider #132
-
During conversion from our visual model to our conceptual model, we are experiencing issues with the field "OPT-300-Procedure-SProvider". |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Hi Jasper, Thank you for the excellent explanation you provided on this topic in #126! I understand your problem. Indeed when "reusing" the created nodes in the conceptual model we need to be a bit "smart" about it. Reusing either all or none of the existing nodes is not going to work. My first thought on this is that you need to use instance identifiers. What I mean is that a I need to reflect on this for a while with my team to double-check first of all that the hierarchy of the specific I will answer to you in #126 where your clear description of the problem will also help others follow this important point more clearly. Thank you. I really appreciate your feedback on this. Regards, |
Beta Was this translation helpful? Give feedback.
Hi Jasper,
Thank you for the excellent explanation you provided on this topic in #126!
I understand your problem. Indeed when "reusing" the created nodes in the conceptual model we need to be a bit "smart" about it. Reusing either all or none of the existing nodes is not going to work.
My first thought on this is that you need to use instance identifiers. What I mean is that a
display-group
which is not repeatable should not be a problem to map to anode
in the conceptual model because it appears only once. However, when you map a repeatabledisplay-group
to anode
you need to tag that node with an instance identifier of the repeatabledisplay-group
so that you can find thatnode
again wh…