Cute Trick #2: Using Dynamic User Variables with Prompts

In the EPBCS project I’m working on we use quite a bit of dynamic user variables to control hardcoded vs selectable form columns. We also use a lot of run on save business rules with hidden prompts. We recently had a situation where we had to combine both. The documentation is a little vague on how to actually do it, so here ya go!

My starting point is a form with two columns: one points to my user variable, one is hardcoded to No Entity to enter assumptions.

The user variable is also selected under Other Options > Dynamic User Variables > Selected User Variables. Enable dynamic user variables is checked. This makes Entity selectable for my first column via the form’s page.

I have a run on save business rule that prompts for Entity, and I want it to automatically pick up whatever member is chosen from the user variable for column A.

To do this, in your business rule, type the name of your user variable in the Value field of your runtime prompt. The variable is not available in the selector, but it works if you type it!

If you test your form now, the prompt won’t be hidden, but it’s a good check to verify that the prompt is indeed picking up the name of the variable.

Now, go back to your business rule and check the Use as Override Value checkbox. This helps in hiding the prompt. You’d think the Is Hidden checkbox would take care of that, but in this case it makes no difference (there’s extensive documentation on when prompts can be hidden vs not in the Calc Manager guide).

That does it. Now, go back to your form and try again. There should be no prompts displayed, but you can verify the rule ran with your selection from the Jobs console. Try selecting a few different members to make sure it all runs smoothly!

2 Replies to “Cute Trick #2: Using Dynamic User Variables with Prompts”

    1. Hi! That I know of, there isn’t an exclude per se in the user variable definition like in forms. There is however a “Not Equal” function in the member selector. I’ve not played with this but it seems to only want to take attribute dimensions (at least per the error I’m getting).

Leave a Reply

Your email address will not be published. Required fields are marked *