Substitution Formula in message

Edward · 2025-04-01T09:27:22+00:00

There was an error rendering this rich post.

I am trying to use a substitution formula in a message and for some reason I can't get it to show anything.

I feel like it should be straightforward but I couldn't find anything in the documentation that states something should be different when compared to a dataflow etc.

This procedure is a capsule procedure if that makes a difference.

Find more posts tagged with

Accepted answers

All comments

Yanis Bouayad

Hi Edward,

I hope you are doing well !

For the show message I believe this would be more appropriate as carriage return can be put at the end

Also the @selection won't show anything if there is no selection yet. Here I have a selection on 2024 and it shows

Can you test this changes (add selection and carriage return at the end) and let us know if it works better ?

I wish you a nice day !

Kind regards,

Yanis BOUAYAD

Premium Support Team Lead

Edward

Hi Yanis,

I made that change and I still have the same issue. The big text in the background is the same @selection in a label.

I would still expect the message to say All or as I have a pager set to 'no all' on the layout show the one site I have selected when removing all selections from screen.

Edward

I have just checked and if I apply the selection within the procedure it works and shows me that selection, but I would of thought it should work from the screen selection.

unknown

This content has been removed.

unknown

This content has been removed.

Helmut Heimann

Hi @Edward ,

you can try to use "@Selection_ex" instead (not using any parameter), like here

This works fine in B14.2

It even considers the "no all" pager's value on the week dimension, displaying the same information as the label does. The message itself is just "<b>Current Selection:</b><br> @Selection_ex"

And the procedure consists of just this step.

Best,
Helmut

Edward

Thanks Helmut,

I just tried your solution and it still didn't work but I have realised the error was mine.

At some point the default data model changed and it was running off a different one.

The confusing thing is that the debugger was showing the correct selections from the data model associated with the screen (and the model I was intending the procedure run on) but the procedure itself was operating on a different data model.

I appreciate the help nonetheless, I will check this out in the future.