Retrieve Parent property
SOURCE: ONESTREAM CHAMPIONS
Hi All,
I am trying to find a way to create a report that shows the Entity and the Parent in a column next to it. I tried to do this by using the functions =...
Forum Discussion
Hi Philip,
If you have the parent then it should be possible to retrieve a property.
This is a Text1 property of a member in Golfstream:
The Actual and 2019M1 can be “” and “”, if there is a default.
As you can see from this example, the property name drives which property is retrieved:
The response can be True/False.
The get relationship property returns relationship information such as e.g. Parent Sort Order:
It is possible to build member list business rules based on information about parent-child, ancestors and descendants, if the members cannot be derived with the built in member filter functions.
Hi Philip,
For that List I just used the grid view on the dimension editor (similar to a cube view member filter)
Generally I look top-down in the member list rules, as I only needed the parents or the children.
However, I tend to use the Metadata Editor from the marketplace to define the Parent-Child relationships in new apps. XML extracts of the Metadata for a given dimension allow an extract including relationships, this will not update automatically if transferred to Excel.
Using “.TreeDescendantsInclusive” shows a hierarchy that is not side by side.
Having a member chosen by a combobox (with parameter) could be an option in a dashboard including ‘Spreadsheet’ with an embedded cube view, there are ways of setting the member chosen into the Spreadsheet report.
In that case the Cube View, embedded in Spreadsheet, could have e.g. X#|!P_MyMemberParam!|.[detail] such as .Parents, .Ancestors and .descendants
If the member filter builder does not have enough logic then resort to a member list in business rules. I would recommend loading the snippet editor from the OneStream Marketplace:
Hi Philip,
If you have the parent set in a text field, you can pull it through in a UD (UD8 for example) so you can show it as a separate column in a CV. We’ve done it for something else entirely, but here’s how we set it up:- Set up the master data with the text field showing as you’d like it to be reported.
- Set up a UD8 (ours is called Scope) as a dynamic calc with the following calc in order to pull the text field in as text (we’re using UD1 and text2):
'This dynamic reporting member will show the Text2 property of each UD1 as an Annotation
If api.View.IsAnnotationType()
'Return the UD1’s Text2 setting for this text-based View member
Return api.UD1.Text(api.Pov.UD1.MemberId,2)
Else
'Return a NoData Datacell.
Return api.Data.CreateDataCellObject(0.0, True, False)
End If- Set up the CV column to pull in the details. Ours looks like this based on how we want to see all the data in the CV:
That’s a bit different than what you’ve been targeting above but simple and useful for us. Maybe not the best solution if you’re expecting the text field to change often and it can easily be pulled via a different formula. Good luck!
