Customizing Dynamics NAV
Discover different ways to customize the application to give you and your colleagues access to the features, functionality, and data that you need most.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
Please rename the personalization.xml to old_personalizaton.xml for that user or you can also delete records pertain to that page for that user from Page Personalization Data or User Metata table.
That worked. I renamed C:\Users\<USERNAME>\AppData\Roaming\Microsoft\Microsoft Dynamics NAV\PersonalizationStore.xml to C:\...\PersonalizationStore.xml-old. Then found all the records in the User Metadata table (2000000075) by running the table and looking at User ID, filtered on every record with that User SID and moved them to a backup table in case this didn't work. The user tested and their NAV client does not crash. Just FYI - the user had no customizations to the objects related to the ones used in applying a vendor ledger entry. That was the initial resistance to getting rid of the personalizations. Also I had not yet done the uninstall/reinstall of the NAV client or deleted the user from the Terminal Server. So it was definitely the removal of the personalizations that resolved the issue.
Business Applications communities