Forum Discussion
Path function error
- 9 years ago
First off, there's a great blog post by the Italians on this topic here: Parent - Child Hierarchies. I've personally used their technique to successfully build a SSAS tab cube based upon essbase financial data with lots of ragged hierarchies.
Anyway, I believe I ran into this issue when I was building my cube. What I found was that there were "alternative hierarchies" in the base data that caused me to have duplicate "children." So in your application, I would examine your data. You likely have a member in the [person name] column that has multiple supervisors. Again, this may be because of an error in the base data and/or there's an alternative hierarchy listed in the data.
So I would go back to your query editor, remove duplicates from the [person name] column to test if your formulas will work then.
First off, there's a great blog post by the Italians on this topic here: Parent - Child Hierarchies. I've personally used their technique to successfully build a SSAS tab cube based upon essbase financial data with lots of ragged hierarchies.
Anyway, I believe I ran into this issue when I was building my cube. What I found was that there were "alternative hierarchies" in the base data that caused me to have duplicate "children." So in your application, I would examine your data. You likely have a member in the [person name] column that has multiple supervisors. Again, this may be because of an error in the base data and/or there's an alternative hierarchy listed in the data.
So I would go back to your query editor, remove duplicates from the [person name] column to test if your formulas will work then.
Assuming you've got a unique list of child [argument 1] entities:
Also important is that "" is NOT the same as null, regarding the parent [argument 2] entities (i.e. multiple employees without supervisors, where supervisor is marked as "" and not null).
"" (an empty cell) may flag as a duplicate, and as missing in the index column, whereas null will not.
A simple replace values will solve that issue.
Something like this in the M Code:
Table.ReplaceValue(<<your table>>,"",null,Replacer.ReplaceValue,{"<<Your ManagerId>>"})
Or Select<<your column>> Transform -> Replace Values -> "" -> null