web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Errors accessing custo...
Microsoft Dynamics AX (Archived)

Errors accessing customers after uploading changes from stating to production (model)

(0) ShareShare
ReportReport
Posted on by mikefern 170

I have a serious issue and wondering if anyone can help.  I have uploaded some modifications from a partners that were tested in a development environment.  I was given the green light to upload to production tonight and now I have errors accessing customer records and/or simple sales orders in production after it successfully uploaded.

I get the error attached...

I know you all can't possibly know what these errors are but how can I go about troubleshooting or reversing the development changes from model (dev) to model (production)?

Any help is greatly appreciated. 

Thank you,

devchanges_2D00_ss1.jpg

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Vilmos Kintera Profile Picture
    Vilmos Kintera 46,149 on at

    Changes to metadata (edt/enum/table/view, etc.) would require you to do a Data dictionary synchronization during the release process in your target environment (Production in this case), without any errors. Have you done that?

    Also how did you release the code? Ideally it should have been imported and merged in a Build/Staging environment, where you would have compiled the application, synchronized the dictionary, generated full CIL, and exported the modelstore, ready to be applied on top of your Production environment. If this is not your process, you are most likely doing it wrong.

    Reverting a model installation would be to delete that model, however, if you mean to revert changes in the same model to a previous version is not possible, unless you have a backup of that model / modelstore, or an SQL backup of your _model database before the release. That is also a best practice to keep the previous modelstore/_model DB backed up before a release, so you could fall back in case of an issue.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Joris dG Profile Picture

Joris dG 5

#2
Alexey Lekanov Profile Picture

Alexey Lekanov 2

#2
Henrik Nordlöf Profile Picture

Henrik Nordlöf 2 User Group Leader

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans