With 25 years of experience working with Sage 300 (and its precursor, Accpac), Orchid Systems understands these issues and risks only too well.
That’s why we decided from the outset that Orchid add-on modules would be part of the solution, not part of the problem.
Here are some of the ways that Orchid products take much of the pain out of Sage 300 Upgrades:
- All Orchid modules are developed in the Sage 300 SDK (Software Development Kit).
As well as the more obvious benefits of tight integration with the Sage 300 core, this means all custom data used by Orchid modules is stored within the company database. After installing a new version of an Orchid module you simply activate it using the standard Sage 300 process, and your existing custom data is automatically upgraded for compatibility with the current Sage 300 version.
- Orchid Extender allows you to make version-independent Sage 300 customizations.
While the breadth of customizations that Extender can support is almost limitless, all of them (including Python scripts) are stored within the Sage 300 company database. This means that when you do a version upgrade the customizations are all carried forward seamlessly, rather than having to be rewritten and re-tested.
- Extender is also a platform for version-independent integration.
One of the many uses of Extender is integration, e.g. synchronization of data between Sage 300 and external applications. (See our article about the DIMO Maint Connector for just one example.) Such integrations share all the above-mentioned benefits of Extender customizations when it comes to ease of upgrading.