Posts

Showing posts from January, 2023

Official Deployment (Step # 12)

  12. Official Deployment:     - Add the channel DB change file to the database folder and register it in RetailSdk\BuildTools\customization.settings.     - Run msbuild for the whole RetailSdk (Note: All resulting packages will have all of the appropriate changes).     - Deploy the resulting packages via LCS or manually.
Post a Comment
Read more

Extend and test Modern POS and Cloud POS: (Step # 10)

  10. Extend and test Modern POS and Cloud POS:     - Open the solution at RetailSdk\POS\ModernPos.sln in admin mode.     - Follow the instructions in readme.md under the Pos.Extensions project, adjusting the steps for the StoreHoursSample extension accordingly.
Post a Comment
Read more

Generate contracts for TypeScript code to consume the Controller endpoints set up in step 6 "Enable and test Retail Server sample code" (Step # 9)

 9. Generate contracts for TypeScript code to consume the Controller endpoints set up in step 6 "Enable and test Retail Server sample code"     - Open the project at "RetailSdk\SampleExtensions\TypeScriptProxy\TypeScriptProxy.Extensions.StoreHoursSample\Proxies.TypeScriptProxy.Extensions.StoreHoursSample.csproj" and compile it     - This project uses the ExtensionsProxyGenerator package to generate DataService .d.ts files, and has a target that copies the generated DataService TypeScript contracts to "POS\Extensions\StoreHoursSample\DataService"         - Once the TypeScript proxy is built, those contracts are available for the POS extension code to be compiled
Post a Comment
Read more

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

Image
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 Co...
Post a Comment
Read more

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

Image
 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.Retai...
Post a Comment
Read more

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

Image
 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 folde r.     - 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 commerceruntim...
Post a Comment
Read more

Update the packaging config file (Step # 5)

Image
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 ass...
Post a Comment
Read more

Verify CDX (Step # 4)

Image
  steps # 4 Verify CDX:      - Run the 1070 job full sync (channel data group).     - Make sure the data has arrived through "Download sessions" and the channel DB. Step 1.     - Run the 1070 job full sync (channel data group). Go to Distribution Schedule and find 1070 job Click on Default in   Channel DataBase Group Tab  Select Channel Database. Click on Full data sync in Action Pane filter 1070 job & click OK (Optional) You can check your Job status in System Administrator  >  Batch Jobs Step 2.  - Make sure the data has arrived through "Download sessions" and the channel DB. Path: Retail & Commerce > Inquiries & reports > commerce Data Exchange See the status of the running job.
Post a Comment
Read more

Channel DB (Step # 3)

Image
  Step # 3 3. Channel DB      - Find the ChannelDBUpgrade.sql file from /SampleInstructions/StoreHours.     - Run it and ensure that it succeeds. Step 1. - Find the ChannelDBUpgrade.sql file from /SampleInstructions/StoreHours. Path: K:\RetailSDK\Documents\SampleExtensionsInstructions\StoreHours Step 2. - Run it and ensure that it succeeds. copy script and paste it into SQL Management tool & RUN
Post a Comment
Read more

CDX: Initialize the Retail scheduler.(Step # 2)

Image
 CDX:     - Initialize the Retail scheduler. Make sure "Delete existing configuration" is checked as "Yes". Search: Initialize Commerce Scheduler Path: Retail & commerce > Headquater setup > Commerce Scheduler
Post a Comment
Read more

Implement Retail SDK Store Hours Sample. (Step # 1)

Image
 1. AX customization:     - Import the project file AXchanges.axpp, compile the project, and run the job.     - Populate the database with some data by running the ContosoRetailStoreHoursInsertTestData job (make it a Startup object and hit F5).     - Create a new operation with ID 3001, add it to a button grid, and run the 1090 Registers job. Follow the Bellow Steps. Step # 1 - Import the project file AXchanges.axpp, compile the project, and run the job. Open VisualStudio on Action Pane Extensions -> Dynamic 365 -> Import Project OR Ctrl+R, Ctrl+P At the of Importing Project you are getting model not found related Error. Project Model is RetailTests you have to go on Descriptor file and comment out model name which was not found. go to path:  K:\AosService\PackagesLocalDirectory\RetailTests\Descriptor open RetailTests in notepad++ (Edited mode). Compile / Build the Project.  Step # 2  - Populate the database with some data by ...
Post a Comment
Read more