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
If }bedrock.cube.data.import is used and the cube has at least one multi-hierarchy dimension, the element checks will fail (e.g. Data Line: 544) if the element is not in the standard hierarchy.
Solution
Maybe it's better to use the leaves hierarchy to check the elements in a dimension with multiple hierarchies. I'm not sure if there are any side effects that I haven't seen, though. This change would affect a lot of rows. Here is a small example.
onefloid
changed the title
}bedrock.cube.data.import: Data checks fail with multi hierarchy dimensions
}bedrock.cube.data.import: Element checks fail with multi hierarchy dimensions
Jun 5, 2024
Hi @onefloid yes that's a good point.
Possibly however, there's an easier and less effort and less obtrusive fix. In the Prolog at section ### Determine dimensions in target cube I think it might be possible to do the testing for the leaves hierarchy upfront and modify the sDimx variable, e.g.
I believe (but could be wrong) that within the context of a function reference that TM1 will evaluate 'myDim':'Leaves' the same as 'myDim:Leaves' which is what the above would rely on.
I don't have a chance to test this myself this week but if you are able to and confirm if it works then this woudl be a quick and easy fix.
(Also IMO always best practice to make sure that all leaves are always present within the same named hierarchy.)
Hi @lotsaram,
Thanks. This is indeed an easier and less obtrusive solution. I can confirm that this solution works as expected for my use case.
I agree that it's best practice to have all leaves in the same named hierarchy. I know a use case where a dimension has for every year a hierarchy and the requirement is that only the current year is in the same named hierarchy.
Description
If }bedrock.cube.data.import is used and the cube has at least one multi-hierarchy dimension, the element checks will fail (e.g. Data Line: 544) if the element is not in the standard hierarchy.
Solution
Maybe it's better to use the leaves hierarchy to check the elements in a dimension with multiple hierarchies. I'm not sure if there are any side effects that I haven't seen, though. This change would affect a lot of rows. Here is a small example.
Old
Data line: 505 and line 544
New
Alternatives
Pass a hierarchies list as a TI Parameter
Discussion
I look forward to your feedback
The text was updated successfully, but these errors were encountered: