Let’s look at why we think it’s important to upgrade.
Important reasons for upgrading:
We think it’s important to upgrade as regularly as possible, at least with every major release – because you get new features, fixes, and tools from Business Central. In the last couple of releases Microsoft provided the performance tool, snapshot debugger and profiler, as well as increased performance overall.
PrintVis has also been releasing new fixes and features such as RapidStart, Estimation Automation enhancements and integrations to Kodak Dynamic Print Planning, EasyPost, 2Ship and others.
When you don’t have to spend time on implementing bug fixes, you’ll have more time to work on new features or customizations which add value for your customer.
On the other hand, when you don’t upgrade, you risk spending time manually implementing fixes that affect your customer.
You can end up with a customized base or PrintVis app which would make upgrading much more difficult and expensive.
And of course, you would also miss new features that your customer would really like to have.
It’s important to check the Upgrade Compatibility Matrix where you can see if the version you are planning to upgrade to is compatible with your current version.
You would need to consider new Business Central server configuration settings and how they can affect the upgrade.
Make sure the infrastructure meets the new system requirements of the target Business Central version.
Plan and test the upgrade process to measure expected downtime – and remember to document all steps for future upgrades.
You could also consider migrating to Cloud or running in Hybrid mode while finishing the migration.
Microsoft provides a lot of information about upgrading that can be very useful, you can find that here.
You could also look at our example script for upgrading a localized PrintVis database with other 3rd-party and per-tenant extensions. We would like to encourage you to test it out and submit Pull-Requests to improve it.
Below you can see a short presentation about this topic we held for one of our PrintVis Developer Open Office Sessions.