Validation of a Customization Project

A customization project must meet various technical requirements to integrate with and operate within the MYOB Acumatica application.

Acumatica ERP Capabilities to Validate and Check Customization Project Items

[1]janiceEven when the topic is broken into sections and this is the end of the intro, we need to revise this in a way that ties together the sections of the topic, and the functionality focus is not the answer. We say here that what follows is functionality, but that is not true for all of them. Look at the first one--it is just a requirement, NOT functionality. I am not sure what point we can make here because the listed items (and future sentences) do not seem to be similar (which is less important now that these will be sections instead of bullets--but we still need something to say. The list items (now sections cover the following): - Definition of a Prefix: This is a requirement placed on the customizer. - Validation Capabilities: This actually qualifies as functionality. (But note that we cannot stick with a list because there's no list intro that will tie together requirements and functionality. They're qualitatively different.) - Validation of Data Consistency: This describes not capabilities but things the SYSTEM does. It qualifies as functionality. - Analysis of Custom Files in the Customization Project: Apparently this is another capability available to the customizer. - Generation of Workbook of Project Items (I recommend this title--the other details can be in the text): This too is a capability, but I have no idea what it has to do with validation and that tie-in needs to be made clear. ***So I think we can just say in this paragraph that the sections that follow provide more information about the requirements that must be met and the functionality provided to validate the project. (You can of course work in the verbiage that is here as long as we don't claim the sections that follow are all about functionality.) But do we need to talk somewhere about the validation the system performs during publication and what it checks? Does it check all of these things? How does it relate to all of these things? I am really confused by this topic.2019/02/0118:23:11-05:00To help to develop a customization project that complies with technical requirements and to help to check the project for compliance with these requirements, MYOB Acumatica and Customization Project Editor provide the following functionality:

  1. Definition of a prefix for the project. All project item names must start with this prefix. You can define this prefix in the Customization Project Editor. For details on defining the project prefix, see To Manage Prefixes in a Customization Project.
  2. Validation of one customization project or multiple customization projects, causing the platform to check the following criteria:
    • The database schema changes included in a customization project are valid.
    • The customization project does not replace or modify the files distributed as part of the standard MYOB Acumatica application.
    • The data types of a custom database column correspond to all data access class (DAC) fields bound to it.
    Tip: These types of validations should be applied to ISV solutions only.

    You can perform this type of validation on the Customization Projects (SM204505) form. On the More menu (under Validations), you click Validate Highlighted Project or Validate Multiple Projects, depending on whether you want to validate one project or multiple projects correspondingly.

  3. Validation of the data consistency in published customization projects, which verifies the correspondence between the data types of DAC fields and field states generated by field attributes at runtime. To perform this validation, you invoke the commands on the More menu (under Validations) of the Customization Projects form as follows:
    • To verify that the data type of a DAC field matches the field states generated at runtime, click DAC Field Types (Runtime Validation).
    • To determine whether there are any PXAttributeFamilyAttribute violations on a DAC field, click DAC Attributes (Runtime Validation).
    • To verify that DAC fields with lookup boxes defined for a segmented key properly handle foreign key segments by means of PXDimensionAttribute, click Lookup Definitions (Runtime Validation).
  4. Analysis of custom files included in the customization project.

    You can analyze custom files (assemblies) included in the customization project to verify that the customization project does not replace or modify files that are distributed as part of the standard MYOB Acumatica application. To do this, 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.

  5. Generation of a workbook with project items.

    You can generate this workbook, which is in Excel format, 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 by 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

Customization as Part of an ISV Solution

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

To see technical requirements for a project in the ISV Software Certification Program guidelines, o[2]Tatiana.Davydovaon Acumatica Partner Portal, click ISV Program->ISV Solution Assessment.2025/02/0718:22:54+01:00n Acumatica Partner Portal, click ISV Program > ISV Solution Assessment.

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 by the specified item.

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