2 of 2 people found this helpful
If you use the "save start trigger name" as an attribute to the event frames:
Then, this attribute will give you a "0" for parent event frames and the start trigger name (variable name) for the others. I am usually trying to look at overall events or just the children and struggled with this until I stumbled upon this. I would rather this be some other value than just "0," but it does work. It won't let you do splitting at the integrator level per se, but should let you filter it on the client side.
Here is a screenshot from both excel through OLEDB Enterprise and Power BI using the integrator to pull the data:
Now that's an excellent workaround. Not really a beaty, but you're just using it!
You did use this functionality obviously, where would you see the best solution? E.g. control over the Parent EventFrame template to use? Additional generic attributes on parents/childs, substitution variables to use to pull in the Parent/Child details into attributes?
3 of 3 people found this helpful
Yeah, it isn't elegant, but it works. I struggled with this for a bit as well, but stumbled on this and have been using it for a while now.
You know, as I dug further, there is a way to get the parent event frame name and use it, as I did it for the hierarchical slicer in Power BI. I had forgotten this (slept since then). Maybe this will also help you. I was using Power BI for my report here, but I don't see why you couldn't build something custom out of this if needed.
I created a parent event frame attribute in my EF template that is a string builder data reference, and it has the following configuration:
Then, in power BI, I created a hierarchy of the parent EF, along with the event frame name:
Then, I could use the hierarchical slicer in Power BI (this was grade runs (parent) and reels (children) on a paper machine as the events) - it would have been better if they were running AF 2017 and I could have used the @attrubute in the naming of the events, because then I would have had reel 1, reel 2, etc. in the name of the events:
It has been 6 months since I did this, so I had forgotten this other little tidbit. Maybe this helps you further.
That's also a nice one! I like his over the Start Trigger as this works on any setup of the Analysis, and does not require the EventFrame configuration to set the Start trigger name.
I decided your last approach comes quite close to a multi-purpose, generic solution. Fitting the bill, let me mark that as correct.
I still do feel we need some better ways to work with EventFrames hierarchies though, but that's another topic.
Yes, I agree. I am doing a fair amount with parent/child events, so I had to spend some time on these things. Glad I could help.