Retrieve Pov Account name in XFBR
Hi everyone,
I need to retrieve the account name from a certain line in a cube view in an XFBR rule.
So, it boils down to the need for an api.Pov.Account.MemberId XFBR equivalent.
Is there...
Forum Discussion
There is no api.Pov.Account for xfbr, because the function is called when rendering the outline of the cubeview. You might pass a parameter to the xfbr function, but this is not working with the data of the cubeview only with headers (:name()).
In your case, I would probably use a ud8 dynamic member formula, then you have access to api.Pov.Account.MemberId.
Member formulas can also work with annotation views, so you can show + or - if you like, or a complete formula.
Dimension that only hold dynamic members don't need to be allocated to a cube, they will work in every cube.
I hope this helps and cheers
Christian
Hi Christian,
Thanks so much for your answer, appreciate it.
My whole problem actually started when I had it set up with UD8 'signage indicators' so to say. 😁I moved to XFBR because I was not able to retrieve the bound parameter outcome (that I use with the navigation) in my UD8 dynamic calc.
Long story short, if there is a way to retrieve the outcome of a bound parameter in a dynamic calc, my problem is also solved 😀
If you can help me with that, it would be very much appreciated.
Thanks, Christian!
BR,
Floris
FlorisvdPoel wrote:I was not able to retrieve the bound parameter outcome (that I use with the navigation) in my UD8 dynamic calc.
Sorry to say, but this isn't possible either.
I start to understand the problem: You need two account dimensions, source and target. But that's not possible with a cube.
But would it be possible, to place the CF in a UD? That's how we are doing this kind of reporting. In the beginning, it sounds a little strange, but it has a lot of advantages. With this concept, you get a CF statement by Account and by Flow.
Hi Christian,
Thank you for your reply.
Placing the CF in a UD doesn't sound too strange, and I will definitely consider it at new implementations. However, this is quite a big change for an up and running system and requires some more discussion.
Thank you for your help.
BR,
Floris