Skip to content

Latest commit

 

History

History
60 lines (40 loc) · 3.94 KB

code-migration-lcs-solutions.md

File metadata and controls

60 lines (40 loc) · 3.94 KB
Raw
title description author ms.author ms.topic ms.date ms.reviewer audience ms.search.region ms.assetid
Migrate code for finance and operations apps solutions
Learn about how to upgrade and analyze your code in Microsoft Dynamics Lifecycle Services (LCS), include code examples for commands.
sericks007
sericks
article
06/13/2018
johnmichalak
Developer, IT Pro
Global
aa01254e-4c18-43e4-81a1-0ef42a27871d

Migrate code for finance and operations apps solutions

[!includebanner]

To complete your solution package, the first step is to upgrade your code by using the best practices in Migrate and Create finance and operations Apps Solutions in Microsoft Dynamics Lifecycle Services (LCS). After that step is completed, you must run the Customization Analysis Report (CAR). This report analyzes your customization and extension models, and runs a predefined set of best practice rules.

To generate the CAR, run the following command on a development environment.

xppbp.exe -metadata=<local packages folder> -all -model=<ModelName> -xmlLog=C:\BPCheckLogcd.xml -module=<PackageName> -car=<reportlocation>

Here is an example of this command.

xppbp.exe -metadata=C:\Packages -all -model=MyAppSuiteCustomizations -xmlLog=C:\temp\BPCheckLogcd.xml -module=ApplicationSuite -car=c:\temp\CAReport.xlsx

The xppbp.exe file is located in c:\packages\bin or I:\AosService\Packages\LocalDirectory\bin. You must resolve any warnings or errors that appear on the Issues tab of the report. You must then submit a copy of the CAR to Microsoft before your validation meeting. For more information, see Customization Analysis Report (CAR). For information about issues and exceptions, see the Customization Analysis Report: Exceptions and known issues post on the Dynamics 365 Community blog.

Extensibility

In Microsoft Dynamics 365 Finance version 8.0 (April 2018), all product models are sealed. Therefore, only extension-based customizations are currently supported. For more information about extensibility, see Extensibility.

The first step in completing your solution package is to upgrade your code using the best practices in Migrate and Create finance and operations Apps Solutions in LCS. After this step is complete, you must run the Customization Analysis report. This report analyzes your customization and extension models, and runs a predefined set of best practice rules.

To generate the Customization Analysis report (CAR), run the following command on a development environment.

xppbp.exe -metadata=<local packages folder> -all -model=<ModelName> -xmlLog=C:\BPCheckLogcd.xml -module=<PackageName> -car=<reportlocation>

Here's an example of how this command might look.

xppbp.exe -metadata=C:\Packages -all -model=MyAppSuiteCustomizations -xmlLog=C:\temp\BPCheckLogcd.xml -module=ApplicationSuite -car=c:\temp\CAReport.xlsx

The xppbp.exe file is located in c:\packages\bin or I:\AosService\Packages\LocalDirectory\bin). Any warnings or errors that appear on the Issues tab of the report must be resolved. A copy of the CAR report must be submitted to Microsoft prior to your validation meeting. For more information, see Customization Analysis Report (CAR) or refer to the Dynamics Community blog for issues and exceptions.

Additional resources

Requirements for publishing apps on AppSource

Develop and customize home page

[!INCLUDEfooter-include]