How about $variable for a button name - giving us the variable value and not the literal string "$variable"
And while you are tinkering with that, how about more than 3 buttons????
4, 5 or even 6 will do just fine
Absolutely agree that calculations (or variables) should be possible in naming custom dialog buttons! Calculations should also be possible in object names!
$variable for a button name would be nice. As a workaround, I have set up a global repeating field for these and use a merge field with the bracket array notation, eg, "<<gRptButtonNames>>" to reference them.
If you mean regular buttons, you can use merge variables for the button name as well. :-)
How about a way to set a variable value from a button. Instead of having to create a global field to capture data entry, be able to just name a variable and have user input from a dialog box? Right now there is no way for a user to enter data directly into a variable, they have to go through fields. If dialog boxes could have data entered into variables, it would cut down on field clutter.
Yes it is crazy I have to create fields in my data structure so I can enter data in a dialogue.
Retrieving data ...