Upgrading Retail SDK extension to latest

In the past couple of months, there have been a lot requests for upgrading Retail from one version to another.

In this post, I will be describing how to upgrade RetailSDK from one version to another. For this exercise I am upgrading from 10.0.18 to 10.0.20.

  • Ensure that your current dev branch for 10.0.18 has been mapped to your local.
  • Get latest and ensure that there are no pending changes. 
  • Apply 10.0.20 update package to the environment.
  • Navigate to https://lcs.dynamics.com/
  • Select the environment that you need to update
  • Choose Maintain > Apply Updates
  • Select the 10.0.20 service package released by Microsoft.
  • Choose Apply
This will kick-off the update process once complete you will be notified via email or you can refresh the page to view progress and details.

Retail SDK 10.0.20 package
To get the RetailSDK 10.0.20 package, navigate to the K drive (referred to as SourceRepo)  for an LCS demo box. This may differ depending on the environment. Sometimes it is in the C drive.

Identify and navigate to the RetailSDK\Update folder. This folder contains all the update packages.

The latest package can be identified by the date modified field.



This folder is the latest 10.0.20 RetailSDK package that has been applied to the environment through LCS. As a best practice you can rename this folder before copying to ensure that you do not get errors in relation to the path name being too long. 

Once you have identified the correct folder, you can copy and add this folder to your source control. The Microsoft-version file displays the current version for the RetailSDK package.

As an example you can add this to your source control titled as either RetailSDKMirror-10.0.20 or RetailSDKMirror-10.0.886.48

This will ensure that you have a copy of the clean RetailSDK version for 10.0.20.


You should now be able to convert your RetailSDK 10.0.20 Mirror folder to branch if you have not done already and create a new branch of this which will represent your Retail SDK 10.0.20 Dev branch.

Once branching is complete and all changes are checked in to source control, we can begin with merge from the 10.0.18 branch to 10.0.20 branch.

First you will need to determine which files need to be merged. Ideally these are the files that usually have modifications and need to be merged.

RetailSDK\
Assets\
CommerceRuntime.Ext.config
CommerceRuntime.MPOSOffline.Ext.config
RetailProxy.MPOSOffline.ext.config
BuildTools\
Customization.settings
Packages\
RetailServer\
Code\
web.config
Pos\
Extensions\
extensions.json

Other than the above files you would need to locate any CRT or POS customizations.

CRT customizations are usually on the root folder, for example, RetailSDK\CRTExtensions.
POS customizations are located within the RetailSDK\POS\Extensions folder. The enabled extensions are usually defined within the RetailSDK\POS\Extensions\extensions.json file. You can use this as guidance to determine which files are required for merge.

Once you have identified the customizations you can proceed to merge the changes as per the source control guidelines. 

Compile and test all your customizations and ensure that there are no issues.




Comments

Post a Comment

Popular posts from this blog

D365FO - Create a multi-select lookup in batch jobs

Image
D365FO - Create a multi-select lookup in batch jobs In this article, I will be describing how we can create a multi-select lookup for display within the batch job dialog. Contract class Create a new variable of type 'List'. This will store the selected values of the user for the dropdown from the dialog. Create a parm method to access the new list object Ensure to specify the DataMember attribute Add an appropriate label Specify the data type for the list's content Ensure to specify the DataContract and SysOperationContactProcessing attributes above the class declaration. An UI builder is also required. The requirements for this is explained in the next section. Example: UI builder class Create an UI builder class that extends SrsReportDataContractUIBuilder Add a new variable of type 'DialogField'. This will be displayed on the UI for user. Implement the postBuild method. Initialize the contract from this.dataContractObject() and bind the dialog field variable to th...
Read more

Generate and download a csv file using X++

Within Dynamics 365 HQ we often need to be able to export data as a csv file. This article explains how we can generate a csv file. The following lines of code can be used to create and download a csv file Create a writable stream. CommaStreamIo streamIO = CommaStreamIo::constructForWrite();   streamIO.writeExp('Id', 'Title'); // These will represent the header of the csv file  streamIO.writeExp('001', 'Science'); // Row 1 streamIO.writeExp('002', 'Nature'); // Row 2 // Get the stream System.IO.Stream        stream              = streamIO.getStream(); const str               extensionCsv        = '.csv'; stream.Position = 0; // StreamReader to read as str System.IO.StreamReader...
Read more

Creating a batch job with query based filter in D365 back-office

There are often business processes that requires us to run specific operations as a batch process. Dynamics 365 Head quarters (HQ) allows us to be able to periodically execute batch jobs. To create a custom batch job you need to extend the  RunBaseBatch class. The following lines of code show how we can create a simple export job.  class InvoiceExport extends RunBaseBatch {      Query                   query;     QueryRun                invoiceQueryRun; // QueryRun object that will be used to generate data for invoices to be exported.      DialogGroup             dialogGroupSetup; // This is a dialog group.     DialogField      ...
Read more