Maintain versioning for custom Sage 300 mod

By | August 25, 2022

Sage 300 provides a functionality to create a custom view, allows customizing the standard screens with the help of views. Here in this blog we will be discussing about the maintain versioning for custom mod with the changes or new release for the mod. The view is created and the module is built and successfully working in an environment. But after a while, some additional functionality needs to be added or make it compatible with the new PU (Product update).

New Stuff : Sage 300 Error: Can’t Create Control

At this time the customization is done and OCX is remake and register. Additional functionality is working, but for the user understanding or for a developer how to know the module is compatible with a new PU or any changes made into it. For this in sage about section in the system information details are mentioned so the user may not confuse about the functionality covered or latest fix applied in the mod.

Refer the below screenshot:


The above displayed image for the GD65A module version mention is only 2018. The changes or an additional customization is done in this module and a new setup is created with all the new changes, but module name is same it will not change then user might get confused regarding the setup installed i.e. whether latest one or the older. To avoid this confusion, version name can be changed through the configuration file for a module. The configuration file is present in a project folder of a module.

Example: C:\Dev\GD\Source\Project\GD.INI.

Open the INI file and make changes in a General section.

Refer the below image for the changes:


Add a producteUpdate line in it as per above image and save the file. Open the command prompt with administrative rights. Change the directory to the path where an INI file is present(c:\dev\GD\Source\project\GD.INI)

Make the project using make -a command.


Refer to the above screenshot for commands:

Copy the runtime folder files to sage\GD folder.

Reopen the sage and check the system information.

It has been changed as per the INI file.


You can refer to above image for changes are made. From the above image the user will know the difference of all uploads and will not get confused.

About Us

Greytrix – a globally recognized and one of the oldest Sage Development Partner is a one-stop solution provider for Sage ERP and Sage CRM organizational needs. Being acknowledged and rewarded for multi-man years of experience, we bring complete end-to-end assistance for your technical consultations, product customizations, data migration, system integrations, third party add-on development and implementation competence.

Greytrix offers unique GUMU™ integrated solutions of  Sage 300 with Sage CRM, Salesforce(listed on Salesforce Appexchange), Dynamics 365 CRM and Magento eCommerce along with Sage 300 Migration from Sage 50 US, Sage 50 CA, Sage PRO, QuickBooks, Sage Business Vision and Sage Business Works. We also offer best-in-class Sage 300 customization and development services and integration services for applications such as POS | WMS | Payroll | Shipping System | Business Intelligence | eCommerce for Sage 300 ERP and for Sage 300c development services we offer, upgrades of older codes and screens to new web screens, latest integrations using Data and web services  to Sage business partners, end users and Sage PSG worldwide.

Greytrix offers 20+ addons for Sage 300 to enhance productivity such as GreyMatrixDocument AttachmentDocument NumberingAuto-Bank ReconciliationPurchase Approval SystemThree way PO matchingBill of Lading and VAT for Middle East. The GUMU™ integration for Dynamics 365 CRM – Sage ERP is listed on Microsoft Appsource with easy implementation package.

The GUMU™ Cloud framework by Greytrix forms the backbone of cloud integrations that are managed in real-time for processing and execution of application programs at the click of a button.

For more details on Sage 300 and Sage 300c Services, please contact us at, We will like to hear from you.