Use the Retail Server Test Client to verify that calling the new functionality succeeds.

8. Use the Retail Server Test Client to verify that calling the new functionality succeeds.

    - Define a C# proxy so other C# code can consume your Controller's endpoints

        - Open Proxies.RetailProxy.Extensions.CrossLoyaltySample.csproj from RetailSDK\SampleExtensions\RetailProxy\RetailProxy.Extensions.CrossLoyaltySample

        - Add the Contoso.Commerce.Runtime.CrossLoyaltySample.dll and Contoso.RetailServer.CrossLoyaltySample.dll as reference to the project

        - Build the proxy project.

        - Copy the output assembly and paste it into the RetailSDK\References folder.

    - Open the solution at RetailSdk\SampleExtensions\RetailServer\Extensions.TestClient\RetailServer.Extensions.TestClient.sln.

    - Uncomment all code that is marked with "SDKSAMPLE_STOREHOURS".

    - Add assembly references to Contoso.Commerce.RetailProxy.StoreHoursSample.dll and Contoso.Commerce.Runtime.StoreHoursSample.dll.

    - Compile the solution.

    - Run the Retail Server Test Client.

    - Enter the local Retail Server URL in the text box next to the "Activate New" button.

    - Click the "Activate New" button.

    - Enter the device and register id you would like to activate and click "Activate".

    - Sign in with the AAD credentials that has the needed registration privileges.

    - Wait a few seconds.

    - The Retail Server Test Client should now show that the device is activated.

    - Click the "Logon" button and log on with a workers credentials.

    - Click the "SDK Tests" button in order to call the new functionality.

    - Click the "Debug" button to see whether or not the your validation succeeded.

Step 1.

 - Define a C# proxy so other C# code can consume your Controller's endpoints
 - Open Proxies.RetailProxy.Extensions.CrossLoyaltySample.csproj from RetailSDK\SampleExtensions\RetailProxy\RetailProxy.Extensions.CrossLoyaltySample
- Add the Contoso.Commerce.Runtime.CrossLoyaltySample.dll and Contoso.RetailServer.CrossLoyaltySample.dll as reference to the project
- Build the proxy project.
- Copy the output assembly and paste in the RetailSDK\References folder.

Open Project of RetailProxy.Extension.CrossLoyaltySample

Path: K:\RetailSDK\SampleExtensions\RetailProxy\RetailProxy.Extensions.CrossLoyaltySample

Right Click on Project under Dependencies Section 

 


Select Browse and goto the Project dll to add as a refrence in Proxies.RetailProxy.Extension.CrossLoyaltySample


Build your Proxies.RetailProxy.Extensions.CrossLoyaltySample

Copy dll of projects and paste into RetailSDK/References

Source:

Path: K:\RetailSDK\SampleExtensions\RetailProxy\RetailProxy.Extensions.CrossLoyaltySample\bin\Debug\net472


Destination: 

Path: K:\RetailSDK\References 


Step 2.

    - Open the solution at RetailSdk\SampleExtensions\RetailServer\Extensions.TestClient\RetailServer.Extensions.TestClient.sln.


Step 3.

    - Uncomment all code that is marked with "SDKSAMPLE_STOREHOURS".


step 4.

    - Add assembly references to Contoso.Commerce.RetailProxy.StoreHoursSample.dll and Contoso.Commerce.Runtime.StoreHoursSample.dll.


Step 5.
    - Compile the solution.


Step 6.

    - Run the Retail Server Test Client.


Step 7.

    - Run the Retail Server Test Client.

You should first have to do or configure the basic configuration of MPOS

go to Devices Validate your device and Download MPOS exe file and the Basic Configuration file  


Download Installer after validation.


Open the MPOS Installer file and Click Next.


Step 8.
 - Enter the local Retail Server URL in the text box next to the "Activate New" button.
- Click the "Activate New" button.
    - Enter the device and register id you would like to activate and click "Activate".
    - Sign in with the AAD credentials that has the needed registration privileges.
    - Wait a few seconds.
    - The Retail Server Test Client should now show that the device is activated.
    - Click the "Logon" button and log on with a workers credentials.

Search POS in SearchBar and Click open.
 

Click Next.

Put your Retail Server Url in Text box with /Commerce and get your Retail Server Url from IIS.


Select your Store.


Select Your Register.


Activation Completed.
























 

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