-
Enable Power Fx function 'User()' in model-driven-apps
Currently, the Power FX function 'User()' is not supported in model-driven apps.
This should also be enabled in model-driven apps so that
- the visibility of buttons can be adjusted based on the logged-in user
- the current user can be automatically written to a field via a button
- ...
-
Visibility rules in the command bar designer via Javascript
In the command bar designer, you can define what happens when a command is activated - execute formula or JavaScript.
For visibility, you can only choose between 'Display' or 'Display with condition from formula'. This means that for simple buttons with more complicated display conditions, the entire button must be created using the XRM Toolbox, as the requirements in the visibility rule can only be implemented to a limited extent with Power FX.
This problem would be solved if the visibility could also be defined with Javascript.
-
Allow/integrate field translation for text fields on all entities
It is already possible to translate product names into other languages, but this function is also required for other entities. Translations are currently very laborious to implement.
Implementation suggestion: Add a checkbox in the advanced settings of a text field in which you can select whether the value can be translated. If the field can be translated, the translation could then be done in the same way as the translation of the product name.
Ideally, it should also be ensured that the translated values can also be filled from Business Central Integration.