Forum Discussion
5 Replies
- db_pdxValued Contributor
Aw snap. That's definitely the better approach. Take my upvote!
- OS_PizzaContributor III
My apologies, I should have elaborate my ask.
- MikeGContributor III
Hi OS_Pizza , depending on how you are doing your Member Expansions in your Rows, you can use an XFBR and pass the Account and UD3 as |MFAccount| and |MFUD3| in the :Name. Then in your XFBR String rule you can use a condition statement and subsequently Return " " or Return "NameOfUD3".
Those packaged substitution variables don't always work as expected when using nested expansions, passing as a parameter to an XFBR so it may not work based on how your Row expansions are configured.
Hope this helps.
- db_pdxValued Contributor
Hi OS_Pizza: at least per the screenshot all members are using U1#Top, so you could remove the U1 expansion altogether and set it in the fixed POV.
If you need to modify the UD1 to something else further down your report, you could also do that with a single override where it is applicable (e.g. A#YourAccount:U1#NotTopAsRequired), rather than including it across all row blocks.
Related Content
- 2 years ago
- 2 years ago
- 11 months ago
- 2 years ago
- 3 years ago