Right now, if you have a screen with a button called BtnA that has a .Fill attribute of "Orange", for example, you can, on another screen, create a button called BtnB that will have a .Fill attribute of "BtnA.Fill".
My suggestion is to allow using the ".OnSelect" attribute the same way.
The reason for this is that I am currently using labels as functions (as seen in the screenshot below). I put all my operations in their ".OnSelect" attribute and they can call each other by doing Select(Lbl_SomeFunction), or a button can have an operation to select one of the labels. It is a great way to have some sort of "user defined functions", but my issue is when these blocks of code are repeated across multiple screens. If I need to modify one line in one of these labels, I need to go into all the other screens and edit that label's ".OnSelect" attribute.
If I could only have my operations written in unique labels on a screen, and then simply point to that screen's labels the same way you can point to another screen's component's fill color, as seen in my initial example, I wouldn't have to repeat my modifications on every single screen.
- MichaelSaroka on: support lookup-fields of CDS-entities in dataflows
- WT35 on: 'word-wrap'-feature for ComboBoxes and Dropdown li...
-
HaydenSinclair
on:
Inbuilt 3D image conversion
-
RussW
on:
Word wrap in data tables
-
jhyatt
on:
Repeating form section with rich text fields?
- Shanir on: View in MR - Lock distance of object from user
- imranakram on: Bring option to hide header in Xrm.Navigation.open...
-
Oskarkuus
on:
RTF control does not work to create hyperlinks to ...
- tlmadison on: Map Pins - customize the color of the selected pin
- s3r3n3 on: Mention someone with @