Register assemblies for use in offline mode (equivalent to RetailServer controller but for local CommerceRuntime when the client is not connected) (Step # 7)

 7. Register assemblies for use in offline mode (equivalent to RetailServer controller but for local CommerceRuntime when the client is not connected)

    - This sample's Retail Server controller is written using the Microsoft.Dynamics.Commerce.Runtime.Hosting.Contracts, meaning the same controller assembly can be used by Retail Server and the offline runtime

    - Navigate to RetailSDK\Assets folder and open RetailProxy.MPOSOffline.ext.config

    - Under the composition section, register your new proxy library name. (The assembly generated after building your proxy project.

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

    - For manual testing, update the RetailProxy.MPOSOffline.ext.config under the C:\Program Files (x86)\Microsoft Dynamics 365\70\Retail Modern POS\ClientBroker\ext with the custom proxy library name under the composition section.

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

    - Navigate to RetailSDK\Assets folder and open CommerceRuntime.MPOSOffline.ext.config

    - Under the composition section, register your new CRT library name. (The assembly generated after building your proxy project.

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

    - For manual testing, update the CommerceRuntime.MPOSOffline.ext.config under the C:\Program Files (x86)\Microsoft Dynamics 365\70\Retail Modern POS\ClientBroker\ext with the custom proxy library name under the composition section.

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

    - add the proxy extension dll to customization.settings ---> <ISV_RetailProxy_CustomizableFile Include="$(SdkReferencesPath)\Contoso.RetailServer.StoreHoursSample.dll" />

Step 1.

 - This sample's Retail Server controller is written using the Microsoft.Dynamics.Commerce.Runtime.Hosting.Contracts,
meaning the same controller assembly can be used by Retail Server and the offline runtime

Step 2.

    - Navigate to RetailSDK\Assets folder and open RetailProxy.MPOSOffline.ext.config
    - Under the composition section, register your new proxy library name. (The assembly generated after building your proxy project.
 <add source="assembly" value="Contoso.RetailServer.StoreHoursSample" /> 

Path: K:\RetailSDK\Assets

Step 3.

- For manual testing, update the RetailProxy.MPOSOffline.ext.config under the C:\Program Files (x86)\Microsoft Dynamics 365\70\Retail Modern POS\ClientBroker\ext with the custom proxy library name under the composition section.

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

Path: K:\RetailSDK\Assets


Path: C:\Program Files (x86)\Microsoft Dynamics 365\70\Retail Modern POS\ClientBroker\ext


Step 4.

    - Navigate to RetailSDK\Assets folder and open CommerceRuntime.MPOSOffline.ext.config

Path: K:\RetailSDK\Assets\CommerceRuntime.MPOSOffline.Ext.config

Step 5.

    - Under the composition section, register your new CRT library name. (The assembly generated after building your proxy project.

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

Solution path: K:\RetailSDK\SampleExtensions\CommerceRuntime

Build the Project > Right on Project > take Properties.


Step 6.

- For manual testing, update the CommerceRuntime.MPOSOffline.ext.config under the C:\Program Files (x86)\Microsoft Dynamics 365\70\Retail Modern POS\ClientBroker\ext with the custom proxy library name under the composition section.

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

Source Path: K:\RetailSDK\Assets


Destination Path: C:\Program Files (x86)\Microsoft Dynamics 365\70\Retail Modern POS\ClientBroker\ext


Step 7.

     - add the proxy extension dll to customization.settings ---> 

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

Path: K:\RetailSDK\BuildTools  



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