Share
Report
355Hi everyone,
I need some guidance regarding deployment and upgrade handling in Business Central AL extensions.
I initially developed a customized solution in AL, downloaded symbols, created the extension, and deployed it successfully in the client environment with all required configurations.
Now, there has been a major change in the solution architecture, where the entire code has been migrated to use a new API / different implementation, so I created a new AL package, downloaded symbols again, and completed all code changes.
My concern is this:
If I deploy this new package to the client environment, the App ID is different from the previous extension, so the old configuration/data setup may conflict with the new deployment.
What is the best approach in this situation?
-
Should I keep the same App ID and treat it as an upgrade?
-
If the App ID has already changed, how can I safely replace the old extension without losing configuration/data?
-
What is the recommended way to handle upgrade and migration in Business Central for such major changes?
Any best practices or upgrade strategies would be highly appreciated.
Thank you.
All responses (
Answers (
