Validation of Customization Projects: Compatibility Validation

To prevent issues between a customization project and a new version of MYOB Acumatica, you need to validate the customization project before upgrading a customized instance of MYOB Acumatica. During publication, the MYOB Acumatica Customization Platform validates the compatibility of the project’s code with the application code of the instance.

Tip: By default, the validation that detects breaking changes is turned on in an instance of MYOB Acumatica. If you need to temporarily omit this validation, you can turn off the CheckCustomizationCompatibility key by including the following string in the <appSettings> section of the web.config file located in the website folder.

<add key="CheckCustomizationCompatibility" value="False" />

We don’t recommend turning off the validation permanently.

Before the Upgrade

In a development environment, test your customizations before a production upgrade to MYOB Acumatica 2025 R2:

Deploy a new instance of MYOB Acumatica 2025 R2. (See Deploying MYOB Acumatica Instances for details.)
On the Customization Projects (SM204505) form, import all customization projects that you need to upgrade for MYOB Acumatica 2025 R2.
Start the publication of these customization projects. The system first validates the projects for compatibility with the current version.

If validation errors occur:

Learn what each error message means. (See Validation of Customization Projects: Compatibility Validation Errors.)
Check the developer release notes for descriptions of specific issues. You can find the release notes, along with the needed MYOB Acumatica build, on the Acumatica Community website.
Replace updated or deprecated objects with the recommended alternatives. You can use AI tools to simplify update. (See Validation of Customization Projects: Using AI Tools.)
Redesign solutions if no alternatives are available for removed objects.

During Validation

This validation process executes the following checks in the code of a customization project to detect the breaking changes in the code of MYOB Acumatica:

In graph extensions:
- Checking the signature for each method that is overridden by using the PXOverride attribute
- Checking that each base graph exists
In data access class extensions when a field attribute is overridden:
- Checking that the field exists
- Checking that the field type hasn’t changed
In binary DLL files: Checking all the referenced methods, properties, fields, return types, and signatures

If the validation has completed successfully, you can upgrade an instance of MYOB Acumatica. For details, see Upgrading of MYOB Acumatica: General Information.

During the Upgrade

In the production environment, do the following during the upgrade to MYOB Acumatica 2025 R2:

Unpublish all customization projects. (See Unpublishing Customization Projects for details.)
Upgrade the MYOB Acumatica instance. (Learn more in Upgrading of MYOB Acumatica: General Information.)
Replace the old customization projects with those validated for MYOB Acumatica 2025 R2. (See To Replace the Content of a Project from a Package for more information.)
Publish the validated customization projects. (See Publishing Customization Projects for details.)