Package configurations and deploy them to an online environment

This topic describes how to package configurations and deploy them to your Microsoft Dynamics 365 Commerce online environment.

When your local site configurations (modules, data actions, and themes) are ready to be deployed to your online environment, you must package and deploy them by using Microsoft Dynamics Lifecycle Services (LCS).

Package the local site configurations for upload

The yarn msdyn365 pack command creates a package of the local site configurations. You can then use the package to upload the configurations to an online environment via LCS.

The command should be run from the root directory of your local online software development kit (SDK) files. The output of the command is a new zip file in the same directory.

Here is an example.

c:\repos\D365.Commerce.Fabrikam>yarn msdyn365 pack

Upload a package by using LCS

To upload a site configuration package by using LCS, follow these steps.

  1. Go to (Alternatively, if you're using the test integration LCS server, go to You should see a sign-in page that resembles the following illustration.

    LCS sign-in page.

  2. Select Sign in, and enter your LCS-provided account credentials. The main dashboard appears.

    LCS main dashboard.

  3. Select the e-Commerce project that you will be using. The project dashboard appears.

    LCS project dashboard.

  4. Scroll to the right to see more options.

    LCS options when scrolling to the right.

  5. To upload the package, in the More tools section, select the Asset Library tile.

  6. On the Asset library page, in the left pane, select the e-Commerce package tab. If you don't see the e-Commerce package tab, you must enable e-Commerce features. Contact your Microsoft Commerce representative to obtain the required code.

    LCS asset library.

  7. Select the plus sign (+).

  8. In the Upload e-Commerce package file dialog box, enter a name and description for the package, and then select Add a file.

    LCS "Upload e-Commerce package file" dialog box

  9. In the Upload file asset dialog box, select Browse, and browse to the location of the package zip file that you created earlier. Select the file, and then select Upload.

    LCS "Upload file asset" dialog box

  10. When the upload is completed, you're returned to the Upload e-Commerce package file dialog box. Select Confirm to process the upload.

    LCS "Upload e-Commerce package file" dialog box after upload

While the upload is being processed, you might have to refresh the page to see status updates. The processing can take between 45 and 50 minutes. When it's completed, a success or failure message is shown.

Upload being processed in LCS asset library.

If the processing was successfully completed, a check mark appears in the Valid column.

Upload successfully processed in LCS asset library.

Deploy a package

To deploy a package, follow these steps.

  1. In LCS, go to the project dashboard, and select the environment that you want to deploy a package to. For example, in the following illustration, the RushE2E-TIE-SB3 pre-production environment is selected.

    Selecting an environment in the LCS project dashboard.

  2. In the Environment features section on the right side of the page, select Manage.

    "Environment features" in LCS project dashboard

  3. Select the E-Commerce (Preview) tab.

    "E-Commerce (Preview)" tab in LCS project dashboard.

  4. Select Apply extension to select the package to deploy.

    "Apply extension" in LCS project dashboard

  5. In the Update e-Commerce dialog box, select the package that you uploaded earlier, and then select Update.

    "Update e-Commerce" dialog box in LCS project dashboard

You can now track the deployment status in the Details section.

"Details" section of "E-Commerce (Preview)" tab in LCS project dashboard

After the deployment is completed, you should see your changes in the authoring tools or on pages that are rendered. For example, new modules or themes will be available to page authors, or changes are rendered and will appear in the online environment.

Additional resources

SDK and core library updates

Microsoft Dynamics Lifecycle Services