Edit

Share via

Validate applications for finance and operations apps

Note

Community interest groups have now moved from Yammer to Microsoft Viva Engage. To join a Viva Engage community and take part in the latest discussions, fill out the Request access to Finance and Operations Viva Engage Community form and choose the community you want to join.

This article provides information about the requirements that verify custom code meets Microsoft guidelines, and that a solution package can be successfully bundled and delivered in a finance and operations apps environment.

Microsoft requires specific reviews to validate the following requirements:

  • A partner's custom code meets Microsoft guidelines.
  • A Microsoft Dynamics Lifecycle Services solution package can be successfully bundled and delivered.
  • Core independent software vendor (ISV) business scenarios can be transacted.

Currently, partners must demonstrate that they meet these requirements by doing test deployments and then sharing the results with Microsoft. Microsoft doesn't deploy any code on a customer environment that it hasn't validated. Partners must complete the following curation artifacts and tests:

  • Code analysis report (CAR)
  • Business process modeler (BPM)/test scripts
  • Business database backup
  • Project name and description
  • Data packages
  • Methodology
  • Binaries (optional)
  • Deployable packages
  • Models (code and tests)
  • Marketing content

Curation meeting

The following table describes the steps that you must complete before the validation meeting.

Phase Step Activity Process steps Success criteria
1 1 Validate code. Run all customer model files by using the CAR tool, then generate the report. Successfully create a CAR without any localization, accessibility, performance, or security issues.
1 2 Verify user experience (UX) guidelines. Follow UX guidelines to implement the workspace correctly. Reference best practice information in the Migrate and Create methodology section of Lifecycle Services.
2 3 Validate the solution package in Lifecycle Services. Create a solution package in Lifecycle Services that includes all the required artifacts. Publish a solution package in Lifecycle Services that includes all the required artifacts and create a globally unique identifier (GUID) for the solution.
2 4 Deploy an environment. Deploy a standard environment that has partner code, based on the package contents (code, binaries, and configuration). Successfully deploy at least one finance and operations environment without any errors. The environment configuration (including components and the configuration) is the same as the partner's reference environment. A user can successfully sign in to this environment without any errors.
2 5 Configure and deploy data. Deploy partner-supplied data in the environment without any errors. Demonstrate that partner-supplied master and reference data was successfully pushed into the environment without any errors.
2 6 Do a check. After data is loaded into the environment, users should be able to complete business transactions (as defined in the scope of the solution). Users can sign in to the data-loaded environment without any errors. Users can complete business transactions, as defined in the package scope, without any errors.

Detailed curation requirements

The following table provides more information about each curation requirement.

Requirement Description
CAR Address all major issues that the CAR highlights after you upgrade. Submit the CAR to Microsoft before the validation meeting.
BPM/test scripts Complete all task recordings for the industry vertical that the solution package is designed for and include end-to-end scenarios.
Business database backup Load a business database of your upgraded environment and best practice configurations into the Asset library in Lifecycle Services.
Project name and description Incorporate the project name and description into the beginning of the implementation methodology for the solution package.
Data packages Load all data packages into Lifecycle Services before the validation meeting. Create data entities for any other custom fields or tables for your custom functional features. You should be able to modify the data packages and load them into an empty environment, and then consume the data packages in Data Management Framework.
Methodology Incorporate an overview of the product. A guided experience to Conference Room Pilot 1 (CRP1) and any other implementation methodology that is tailored to your solution are optional.
Binaries (optional) Incorporate any required binary files.
Deployable packages Incorporate the deployable packages that are required to bring your custom features and functionality into your environment.
Models (code and tests) Incorporate any model files that are required for your solution.
Marketing content Add your marketing content, such as logos, descriptions, and screenshots of your solution package. The solution logo should be app-specific and shouldn't include your company name. The description should be aligned with your custom business processes.

Update and maintenance requirements

If you have a curated solution that you publish on AppSource, you must keep the solution up to date. After each major spring and fall release, you have eight weeks to upgrade your code. You must update and test the following artifacts:

  • CAR
  • Models (code and tests)
  • Deployable packages
  • BPM/test scripts
  • Data packages
  • Business database backup

Maintenance process steps

Phase Number Activity Process steps Success criteria
1 1 Validate customer code. Run all customer model files by using the CAR tool, and generate the report. Successfully create a CAR without any localization, accessibility, performance, or security issues. Address all major issues that the CAR highlights after you upgrade to the latest major release. Submit the CAR to Microsoft within eight weeks after each major Spring and Fall release.

Additional resources

Requirements for publishing apps on AppSource

  • Last updated on