Implementing offline support for D365 MPOS, the details MS didn't document

-
If you haven’t discovered it on your own these are undocumented changes you need to do on top of the MS provided steps(See StoreHours example) to get offline custom entities actions working.

Update SDK namespace
Update the namespace for the C# proxy in RetailSDK_Dev\BuildTools\Microsoft.Dynamics.RetailSdk.Build.settings to match SDK namespace.

The namespace change will break the SDK compile in many places. Do a search and replace for “namespace Contoso” in your SDK to your root namespace as you specified in the settings file.

Specify adapter in MPOS request

In the POS service request you’ll need to make sure that entityType is specified.

When the MPOS core generates the request URL it will take the entityType value and append “Manager” to try construct the URL looking for your offline adaptor manager class. If entityType is missing POS core will look for your custom entity action in the StoreOperations adaptor

In the example below the request would be posted back to crt://offline/StoreOperationsManager/UpdatePurchOrdernum if entityType is missing.



Update the C# RetailProxy project (looks to be a bug, reported to MS)
In the current version of the SDK you’ll need to make a change to the parameter unpacking in the C# proxy project.

The function CommerceRuntimeRequest.prototype.formatParameters in the Commerce.Core.js will bundle up all parameters to a single object with the key entity. The C# proxy will compare the parameter names of the input parameters of your adaptor action with the values passed in the request. Because there will be only one parameter called entity the parameters will not be found and the execution will fail.

To fix the problem make the following changes to the Retail Proxy project.

Add project reference Newtonsoft.Json.Protable. The dll can be found in the reference folder of the SDK.

Change the constructor of the class CrtUri in Adapters\CrtUri.cs, add the code between the comments //Unpacking offline parameters.


 

Remove the parameter number check in the class AdaptorCaller and method CallCommerceRuntimeAsync found in Adapters\AdaptorCaller.cs



Comments

Post a Comment

Popular posts from this blog

How to disable auto enabled flight key using KillSwitch

-
Image
Microsoft is introducing new functionality into Dynamics 365 for Finance and Operations with flight keys in every other new release. For this they use  Flight  classes so that the changes are automatically applied and can be reversed.  Example of a flight class that control the functionality of a new set of functionality.  When a flight key that enable functionality can be found in the flight key table  SysFlighting To disable the functionality don't delete or change the enabled flag on the flight record, instead insert a KillSwitch  record. The KillSwitch record will ensure that the flighed functionality will stay disabled as long as it exist in the flight table.  In an environment that Microsoft maintain can raise a support ticket in LCS to disable specific flight keys.  SQL statement for insert the KillSwitch record.  DECLARE @flightName NVARCHAR(100) = 'WHSWorkCancelForcedFlight_KillSwitch' IF NOT EXISTS (SELECT TOP 1 1 FROM SysFlighting WHERE flightName = @flightName
Read more

Technical intro to Feature management in D365FO

-
Image
Feature management is an alternative to configuration keys for releasing and introduce a new features into D365FO.  MS is still releasing updates around the framework but the existing state as per 10.0.9 provide all we need to get started with releasing functionality that is controlled by the feature management framework.  The key to the feature framework is the feature class, in my example below see the class  pekTestingFeature. It is used as a descriptor for the feature and the flag to indicate if the feature is enabled or not. Once the class is created and compiled, users can navigate to Feature management  under System administration  and enabled/disable the feature. It is possible to make a feature enabled by default or disable the possibility to disable the feature. If the feature doesn't automatically appear, run the Check for updates button.   The feature class can be applied to menu items and menus. If enabled the menu item or menu will be visible to the
Read more

Continuous integration and deployment Power platform FinOps tweaking

-
Image
If you are working with the new unified development environments and CICD pipelines described here .  You might find the fact that we have to update the pipeline with the platform and application version annoying.  A quick way to get around this if you are using azure hosted agent pipeline as per this repo is to pull the number from the package.config and using it in the create deployable package task as per the two example tasks below.  The first powershell task will pull the version from the nuget files and save it to variable that can be reused in later tasks within the job. 
Read more