Update the packaging config file (Step # 5)

Step # 5 

Update the packaging config file:

     - Configure the default channel in RetailSdk\Assets\commerceruntime.config:

        <storage defaultOperatingUnitNumber="052" />

    - Register the new CRT assembly in RetailSdk\Assets\commerceruntime.ext.config (Note: Please DO NOT edit commerceruntime.config file. This file is not meant for any customizations.):

        <add source="assembly" value="Contoso.Commerce.Runtime.StoreHoursSample" />

    - Register the new CRT assembly in RetailSdk\BuildTools\customization.settings:

        <ISV_CommerceRuntime_CustomizableFile Include="$(SdkReferencesPath)\Contoso.Commerce.Runtime.StoreHoursSample.dll" />

Step 1. 

- Configure the default channel in RetailSdk\Assets\commerceruntime.config:

        <storage defaultOperatingUnitNumber="052" />


step 2.

    - Register the new CRT assembly in RetailSdk\Assets\commerceruntime.ext.config (Note: Please DO NOT edit commerceruntime.config file. This file is not meant for any customizations.):

        <add source="assembly" value="Contoso.Commerce.Runtime.StoreHoursSample" />


Step 3.

    - Register the new CRT assembly in RetailSdk\BuildTools\customization.settings:

        <ISV_CommerceRuntime_CustomizableFile Include="$(SdkReferencesPath)\Contoso.Commerce.Runtime.StoreHoursSample.dll" />













Comments

Post a Comment

Popular posts from this blog

Creating a class, the best practice way in D365F&O

 Some time ago, I shared my thoughts on the 'construct' pattern, which is commonly used in AX. While I often make use of it, it’s not without its flaws—it can actually violate some best practices. (I’ll cover the issue of deep class hierarchies resulting from this pattern in a future post.) First, it’s worth noting that you can customize the compiler level and the best practice checks it performs. To do this, compile something to bring up the compiler output window. Then, click the Setup button to adjust the settings. For this example, I used compiler level 4 and enabled all best practice checks. Now, let’s create a simple class. This class will simply display information from an InventTable record. 1. ClassDeclaration As we start designing this class, it quickly becomes clear that we need to declare an InventTable record as a member variable. /// <summary> /// Class written to test the construct and new... patterns /// </summary> /// <remarks> /// De...
Read more

Package Deployment using LCS for Microsoft Dynamics 365 Finance & Operations

Image
Most of us are familiar with Lifecycle Services(LCS), and package deployment is one of its uses. Below are the steps that need to be performed for successful deployment or application updates.   Prerequisites: 1) Admin account access for package creation. 2) LCS account with project assigned. Visual Studio Steps Step 1: Open Visual Studio using Run as administrator. Step 2: Click Dynamics 365--> Deploy --> Create deployment package.  Step 3: Select the model(s) to be deployed and the location of the package file where it will be stored.  LCS Steps  Step 4: Log in to LCS and select Asset Library from the top left dropdown.  Step 5 : Navigate and select Software deployable package and select + button to add package to the folder and confirm. Refresh the screen and wait for the package gets validated, tick will appear once validated. Step 6: Navigate to the environment where the package will be deployed. Select apply update under the Maintain dropdown....
Read more

How to remove deployed model in Tier2 environment in D365FO

 How to remove the deployed model in the Tier2 environment Dear all, I have an issue with the deployed model in the D365FO Tier 2 environment. I have some models in the development environment: Model A Model B Model C Model D I want to apply only Models A, B, and C for the Tier 2 environment. For the first time for deployment, I created a deploy package(including Model A, B, and C) in development and applied an update for the Tier 2 environment. However, yesterday, developer X on my team deployed a new deployment package(Model A, B, C, D). So today I could not deploy the package in Tier 2 with Models A, B, and C. Solutions: 1. Download the same package from the Asset Library that was previously deployed. Add File ModuleToRemove.txt (with model listed). Reupload to Asset Library and deploy to UAT. When I do this,  there's a warning on LCS that "it will first reinstall the model and then delete it. In order to not reinstall, delete the model from the package." 2. Create a n...
Read more