Bug - Option Display as Dynamic Expression

Just noticed this today, but believe this New Bug is due to the ‘improvements’ bubble made to the expression composer and the change of ‘literals’ in the expression that cause us to have to press enter after inputting a number.

The bug is that now, we can not use a dynamic expression of ‘get an option’ followed by a selected option of display and then go back to change which option by clicking onto the option display value in the dynamic expression.

Previously, and the way it should be, if I wrote a dynamic expression of ‘New Display’ (where New is the display value of an option set that is a status) and then I want to change the option by clicking into the dynamic expression ‘New’ component, I am able to see the list of options to chose a new option from that option set, but now, instead I have to clear the entire expression and start all over again because when I click onto the ‘New’ portion of the expression the list of options is not provided.

This is terrible. Makes copy and paste of elements with data sources pointing at specific option set values are needed to be redone instead of quickly and easily clicking into existing expression and choosing the new option from the list of options.

@fede.bubble can you confirm if the team intentionally made this change, or is it an unintentionally addition that snuck into the system due to how they altered the expression composer to allow for ‘literals’?

shared the post with the team, I’ll reply back with what I hear

I’m a little confused. Can’t you do this already? Any examples would help

Hi @fede.bubble Thanks for the reply. When I went back in to try and create an example, I see what the issue and I think it’s a me issue.

I was seeing this in a workflow action, to make changes to a thing, with two fields, one is the option set the other is text. The first field of option set, I click and see all options, select one and the expression is set.

What I had done, was simply copy that, paste it into the field that is text, and then completed with Display. My issue, was I didn’t recognize that I had not gone through the steps of creating the expression by first choosing ‘get option’ since the expression was copied from a field that already knew to expect an option.

So, no bug, just me bugging out.

This topic was automatically closed after 14 days. New replies are no longer allowed.