Enable and test Retail Server sample code (Step # 6)

 Step # 6

Enable and test Retail Server sample code:

    - Open the project at RetailSdk\SampleExtensions\RetailServer\Extensions.StoreHoursSample\RetailServer.Extensions.StoreHoursSample.csproj and compile it.

    - Use inetmgr to find the location of the local Retail Server folder.

    - Register the new Retail Server assembly in web.config file under <extensionComposition> (Note: If there is an assembly registered from a previous sample, then remove it.): 

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

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

        <ISV_RetailServer_CustomizableFile Include="$(SdkReferencesPath)\Contoso.RetailServer.StoreHoursSample.dll" />

    - Copy the changes you made to RetailSdk\Assets\commerceruntime.ext.config to the local Retail Server's commerceruntime.ext.config in its bin\ext folder.

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

    - Drop both the new CRT and Retail Server assemblies into the local Retail Server bin\ext\ folder. Alternatively, use the Retail SDK's AfterBuildDropBinariesToRetailServer target for rapid development (Note: If you use the AfterBuildDropBinariesToRetailServer target, then you have to rebuild the 2 assemblies at least once in order to binplace them automatically).

    - Use inetmgr to browse to the Retail Server's $metadata and verify that the StoreHours entity is exposed (i.e. open https://usnconeboxax1ret.cloud.onebox.dynamics.com/Commerce/$metadata and search for "StoreHours" in the XML).


Step 1. 

 - Open the project at 
RetailSdk\SampleExtensions\RetailServer\Extensions.StoreHoursSample\RetailServer.Extensions.StoreHoursSample.csproj and compile it.

Step 2.
- Use inetmgr to find the location of the local Retail Server folder.

Search IIS in PC Go to Sites > RetailServer > Explore


Step 3.

 - Register the new Retail Server assembly in web.config file under <extensionComposition> (Note: If there is an assembly registered from a previous sample, then remove it.): 

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

Step 4.
 - Register the new Retail Server assembly in RetailSdk\BuildTools\customization.settings:
        <ISV_RetailServer_CustomizableFile Include="$(SdkReferencesPath)\Contoso.RetailServer.StoreHoursSample.dll" />


Step 5.
 - Copy the changes you made to RetailSdk\Assets\commerceruntime.ext.config to the local Retail Server's commerceruntime.ext.config in its bin\ext folder.
          <add source="assembly" value="Contoso.Commerce.Runtime.StoreHoursSample" />


Step 6.
- Drop both the new CRT and Retail Server assemblies into the local Retail Server bin\ext\ folder. Alternatively, use the Retail SDK's AfterBuildDropBinariesToRetailServer target for rapid development (Note: If you use the AfterBuildDropBinariesToRetailServer target, then you have to rebuild the 2 assemblies at least once in order to bin place them automatically).

solution:
    You have to go to the Project root folder copy CRT and Retail Server DLLs and paste them into the Retail server.
 
Steps 1.
    Right-click on the project and go to the Open folder in File Explorer.

Path: K:\RetailSDK\SampleExtensions\RetailServer\Extensions.StoreHoursSample\bin\Debug\netstandard2.0




copy Contoso.Commerce.Runtime.StoreHoursSample.dll and Contoso.RetailServer.StoreHoursSample
and drop both in Retail server.
Path: K:\RetailServer\WebRoot\bin\Ext




Step 7.
    - Use inetmgr to browse to the Retail Server's $metadata and verify that the StoreHours entity is exposed (i.e. open https://usnconeboxax1ret.cloud.onebox.dynamics.com/Commerce/$metadata and search for "Store hours" in the XML).

url: https://demo-envd4a8206ce8b671d0ret.axcloud.dynamics.com/Commerce/$metadata


Comments

Post a Comment

Popular posts from this blog

D365FO – AX – Update Data Entity Target Entity fields with X++

Image
  Imagine you want to set the value of a field of the Target Entity of a Data Entity with X ++ code You have to create an extension class that extends the data Entity, extends the “mapEntityToDataSource” method, and adds your code inside. [ExtensionOf(tableStr(PurchPurchaseOrderHeaderV2Entity))] //Extends Data Entity final class Al0PurchPurchaseOrderHeaderV2Entity_Extension {     public void mapEntityToDataSource(DataEntityRuntimeContext _entityCtx, DataEntityDataSourceRuntimeContext _dataSourceCtx) //Extends method     {         switch (_dataSourceCtx.name())         {             case dataEntityDataSourceStr(PurchPurchaseOrderHeaderV2Entity, PurchTable):             PurchPurchaseOrderHeaderV2Entity purchPurchaseOrderHeaderV2Entity = _entityCtx.getEntityRecord(); //Get Data Entity buffer (Source Entity)             PurchTable purchTa...
Read more

How to Create Auto Lookup Using EDT with Table Reference in D365 F&O

Image
  How to create a lookup in D365FO using X++? Lookups are the standard way to display a list of possible selection values to the user. For a user, while editing or creating database records, a lookup makes the data entry easy and errorless. In Microsoft dynamics 365 finance and operations, there are many ways of creating lookups. EDT and Table Relation Type lookups are the simplest forms of lookups in Microsoft dynamics 365 finance and operations. In this article, I will describe the very simplest type of lookup, which is EDT lookup, for making an EDT type lookup, a developer does not need to worry more about writing x++ coding,   Normally, standard lookups are created automatically by the system in Dynamics 365 for Finance and Operations and are based on the extended data types and table setup.  They are based on table relations and appear automatically. No additional modifications are required. Setting Up an EDT Lookup If you are a beginner use  Microsoft's free ...
Read more