Validation of Customization Projects: ISV Solutions

The validation of a customization project is especially important when the project is a part of an independent software vendor (ISV) solution.

Attention: To learn the technical requirements for an ISV customization project, open the MYOB Partner Portal and click ISV Program > ISV Solution Assessment.

To prepare your solution for technical validation, you can use the tools and validation techniques described below.

Validation of Customization Projects

You can validate any number of customization projects to be sure each project meets the following criteria:
  • The database schema changes included in the customization project are valid.
  • The customization project does not replace or modify any files distributed as part of MYOB Acumatica.
  • The data types of custom database columns correspond to the data access class (DAC) fields bound to them.

You can perform this type of validation on the Customization Projects (SM204505) form. On the More menu (under Validations), click Validate Highlighted Project or Validate Multiple Projects.

Validation of Data Consistency in Published Customization Projects

The validation of data consistency in published customization projects checks whether the data types of DAC fields match the field states generated by field attributes at runtime. To perform this validation, you use the commands on the More menu (under Validations) of the Customization Projects (SM204505) form as follows:
  • To verify that the data types of DAC fields match the field states generated at runtime, click DAC Field Types (Runtime Validation).
  • To check for PXAttributeFamilyAttribute violations on DAC fields, click DAC Attributes (Runtime Validation).
  • To verify that PXDimensionAttribute attributes properly handle foreign key segments, click Lookup Definitions (Runtime Validation).

Validation of a Project Prefix

In the Customization Project Editor, you can specify a prefix that should be added to all objects of the customization project. If a prefix is used, all project item names must start with it.

When validation of the customization project is performed, the platform checks all objects to be sure they have the prefix.

To add a prefix for a customization project and validate the project's items for the added prefix, do the following:

  1. On the main menu of the Customization Project Editor, select File > Validate Project Prefix.

    The Customization Project Prefix dialog box opens.

  2. In the Project Prefix box of the dialog box, type the prefix for the customization project. The prefix can be two to four case-insensitive Latin letters (A through Z).
  3. Click Save.
  4. Click Validate Project Items. In the Validation Result area, the result of the validation appears.

Format of the Validation Results

If any errors or warnings have been detected during project validation, the validation results have the following format:

  • <CustomizationProjectName>
    • <CustomizationRuleName>
      • <PathToTheDLL> | <ProjectItemType> | <NameOfTheProjectItem>

        List of rules broken down by the specified item

        Tip: The <PathToTheDLL> field is optional and appears only if a dll file included in the project is analyzed.

Analysis of Assemblies Included in the Customization Project

You can analyze assemblies included in a customization project to verify that the project doesn’t replace or modify files distributed as part of MYOB Acumatica.

To run the analysis, on the main menu of the Customization Project Editor, click Extension Library > Analyze Referenced Assemblies. A CSV file is downloaded with all references made in the project's custom files.

Generation of a Workbook with Project Items

When you submit your solution for technical validation in MYOB, you need to provide an Excel workbook with project items. You can generate this workbook in the Customization Project Editor by clicking File > Export Project Items Workbook.

The generated workbook contains a list of solution objects and integration scenarios grouped into the following types:

  • Site map nodes
  • Mobile site map nodes
  • BLСs and BLC extensions
  • DACs and DAC extensions
  • Push notifications
  • Import or export scenarios