March 27, 2019 - By James French
Hello readers, this blog is going to discuss various things regarding the new AL programming language, which will be useful for those going behind the scenes in Business Central. Today’s tip is regarding field changes.
Have you ever seen an error that reads “Unsupported Field Change Reason X:” ? The reason for this is Business Central cements the schema of your table as soon as you first build it, and it is unable to forget what’s written in the schema.
So now that we know why the problem is happening the question is how do we solve it? Depending on your situation there are two solutions:
- If your app is in production you must uninstall and unpublish the application and all of its previous versions before installing the new version.
- If you’re in a container environment you can solve the issue by changing the schema update mode property from Synchronize to recreate.
There is one caveat to this solution, regardless of what route you take to the solution, recreating, or unpublishing and republishing will remove the data from your table! This is problematic but it is better than recreating your whole app from scratch.
Stayed tuned for my next post on writing install code units to make sure that there is always some test data in your tables!