You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In recent testing regarding using macros to initiate formatting of DAX, I've found that the DAX in the Expression Editor window won't be formatted unless outstanding changes are 'Accepted' first.
It would be great if the UI detected this situation when a macro is triggered and prompted the user to 'accept' or 'reject' the current outstanding changes. The behaviour could have an option to control the default selection; accept/reject/ask.
Also, is there be a function than can be run as part of the macro to force accepting of outstanding changes? This would be handy in the interim as I keep catching myself out when applying DAX formatting via a macro.
This discussion was converted from issue #315 on October 12, 2023 14:04.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In recent testing regarding using macros to initiate formatting of DAX, I've found that the DAX in the Expression Editor window won't be formatted unless outstanding changes are 'Accepted' first.
It would be great if the UI detected this situation when a macro is triggered and prompted the user to 'accept' or 'reject' the current outstanding changes. The behaviour could have an option to control the default selection; accept/reject/ask.
Also, is there be a function than can be run as part of the macro to force accepting of outstanding changes? This would be handy in the interim as I keep catching myself out when applying DAX formatting via a macro.
Beta Was this translation helpful? Give feedback.
All reactions