Purpose
Once the Package is created (Pls have a look on the previous blog for more information on how to "Create Deployable Package in development environment") now its time Upload and Release Package in Microsoft Dynamics LifeCycle Services (LCS).
Supported environment: All environment are supported except production environment. In case of production environment request should be submitted to Microsoft to apply package.
Once the Package is created (Pls have a look on the previous blog for more information on how to "Create Deployable Package in development environment") now its time Upload and Release Package in Microsoft Dynamics LifeCycle Services (LCS).
Supported environment: All environment are supported except production environment. In case of production environment request should be submitted to Microsoft to apply package.
Important: Regardless of the project type, if you have a build environment, you can only use LCS to apply Binary updates and Data upgrade packages. You can't use LCS to apply an Application Deployable package.
Prerequisite Steps:
· Make sure that the package which should be applied is valid. A package must pass validation before it can be applied in an environment by using the following procedures. The status of the package will be updated in the Asset library to indicate whether the package is valid. We require validation to help guarantee that production environments aren't affected by packages that don't meet the guidelines.
There are three types of validations:
o Basic package format validations
o Platform version checks
o Types of packages
· Make sure that the package is applied in a sandbox environment before it's applied in the production environment.
For an application (AOT) deployable package that results from an X++ hotfix, or from application customizations and extensions, create the deployable package in your development or build environment, and then upload it to the Asset library.
Follow the below steps to upload Deployable package into Microsoft Dynamics LifeCycle services (LCS).
Sign in LCS and Click the Asset Library as defined in previous part of this blog:
- Deployable package can be uploaded in Asset Library using (+) sign in LCS under Software Deployable package.
2.
Upload Deployable
package file on the clicking of “Add a file” button.
3.
Browse and upload Deployable package file, which was created from Visual studio in earlier steps:
4.
Once package file is
uploaded, successful upload will be visible on the screen, now press ‘confirm”
button to upload the file in asset library on LCS:
5.
Deployable package is
uploaded on LCS but it is not valid as shown below Valid check box is unchecked:
so validate the package on the basis of defined validation on the Prerequisite section.
6.
Once validation is successful, click Release candidate.
This will mark “Valid” to the package along with other Released details ie.
Asset ID, Package Id, Platform version and Platform build etc.
7.
Once package is released, package will be visible
in Shared asset library too, so that package could be imported in other available projects in
the LCS as well.
Once the package is uploaded and released, now its time to apply it on End customer development environment:
To get more information on how to Install Application Deployable package on Development Environment. Click here
To get more information on How to Create Application Deploayable package - Click here
In case if you have any query or concern, please feel free to reach me at my personal email- daxmanish@outlook.com
To get more information on how to Install Application Deployable package on Development Environment. Click here
To get more information on How to Create Application Deploayable package - Click here
In case if you have any query or concern, please feel free to reach me at my personal email- daxmanish@outlook.com
No comments:
Post a Comment