4

We have added a field to the Purchase requisition creation flyout through out-of-the-box personalization. We added the field "Reason" to a view and made it mandatory so users can input that information there and not forget about entering it on the actual order. However, when we enabled this feature, Saved views performance enhancement (https://learn.microsoft.com/en-us/dynamics365-release-plan/2022wave2/finance-operations/finance-operations-crossapp-capabilities/saved-views-performance-enhancement) it breaks the personalization.


The result is the dropdown not showing any values when selected, but a value is actually selected it just does not show up for the user. I have a document written up on this if that would be helpful.

STATUS DETAILS
Declined
Ideas Administrator

Thank you very much for your input. Enabling this cross application feature with the ripple effect of breaking personalization may be an unintended design consequence that than as by explicit and cognizent design decision that you should log through the support channels to have assessed.