You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using the }bedrock.hier.import process I can see that where the process looks to create a parent child relationship (prolog line 71) it checks if sVar2 exists within the Leaves hierarchy and skips if true.
In this case sVar2 is the child and could reasonably exist in the Leaves hierarchy, I believe this should check if sVar3 (being the Parent) exists in the Leaves hierarchy as the risk is clear that a N level element would then try to be created as a C.
I believe this should be
Without this change any structure created will effectively only have C level structure with N levels orphaned.
Version
OS: IBM Cloud (SaaS)
TM1 Server Version: 11.8.02300.10
The text was updated successfully, but these errors were encountered:
Describe the bug
When using the }bedrock.hier.import process I can see that where the process looks to create a parent child relationship (prolog line 71) it checks if sVar2 exists within the Leaves hierarchy and skips if true.
In this case sVar2 is the child and could reasonably exist in the Leaves hierarchy, I believe this should check if sVar3 (being the Parent) exists in the Leaves hierarchy as the risk is clear that a N level element would then try to be created as a C.
I believe this should be
Without this change any structure created will effectively only have C level structure with N levels orphaned.
Version
The text was updated successfully, but these errors were encountered: