Publish D365 FO Apps to Microsoft AppSource: Technical Configuration in Partner Center

In this blog post, I would like to go through the technical configuration details that need to be entered while publishing an ISV solution built on Dynamics 365 Finance, Supply Chain Management or Commerce applications to Microsoft AppSource. That means, the technical details you need to enter when creating a Dynamics 365 Operations offer in the Microsoft partner center. Non-technical information like videos, screenshots and other marketing collateral are not covered here.

Basically, the following two details need to be provided along with other supporting marketing content that you would be uploading for your solution.

1. Customization Analysis Report (CAR)
2. Solution ID or Solution Identifier

Customization Analysis Report (CAR):

• If any custom objects or extensions exist for your solution, you will need to generate a CAR report by running the following command.

xppbp.exe -metadata=<local packages folder path> -all -model="<model name>" -xmllog=c:\temp\BPCheckLogcd.xml -module="<package name>" -car=<File location for CAR Report>

• Xppbp.exe is available in the bin folder of your PackagesLocalDirectory
• Metadata is the PackagesLocalDirectory path on your Developer VM

For example, I have created some sample objects under model D365FODemo in the package D365FODemo. And here is my command to run CAR report for my customizations.

xppbp.exe -metadata=K:\AosService\PackagesLocalDirectory -all -model="D365FODemo" -xmllog=c:\temp\BPCheckLogcd.xml -module="D365FODemo" -car=c:\temp\CAReport.xlsx

If there are any best practice violation errors or warnings, they will be listed on the command prompt. The generated CAR report has all the details of your extensions and any errors or warnings as well. Please find the sample screenshots below.

Please fix any errors or warnings listed in the CAR before submitting the solution in the partner center.

• If the solution exists outside of FO and is purely a data integration leveraging out-of-the-box entities, there will not be any customizations and hence no CAR. In this scenario, please upload a PDF or a word document with a couple of lines stating the same.

Solution Identifier:

For Solution GUID, you need to create a solution within your LCS project Solution Management Tile. If the solution integrates with D365 Finance or Supply Chain Management, create solution under your Finance and Operations project within LCS. If the solution integrates with D365 Commerce, please create under D365 Commerce project within LCS.

Please follow the below steps to create a solution

• Make sure you are within your LCS project. Select Solution Management tile

• Click '+' to add new Solution

• Create solution package. If it is solution with D365 Commerce, please select Commerce and Retail Implementation Methodology Below.

• On this page, add deployable package of your customizations, solution approvers and any licensing and policy agreement links under Branding. For Commerce, today you will not see these options to add and please proceed to next step.

• Click 'Publish' and it generates a Solution Identifier for your solution. Select Organization in the below dialog box.

Click 'Yes' on the next dialog box.

Provide the above Solution Identifier in the partner center where it asks for Solution ID while generating a Dynamics 365 Operations Offer.