Setting up retail parameters in Microsoft Dynamics 365 for Operations is one of the first steps for setting up retail channels for your organization. Recently, Microsoft added descriptions to various fields throughout the parameters tabs. I have noticed that with each update more are added.
In previous versions of AX, you were able to hover over a field and see a field description at the bottom of the window. In Dynamics 365, you can hover over the field title and a description box will display.
As I mentioned, not all fields will display a description, and this is especially true in the Retail scheduler parameters form (Retail and commerce > Headquarters setup > Parameters > Retail scheduler parameters). This form is used to manage the distribution of data from the head office to stores and terminals. So, let’s go over the fields available in the Retail scheduler parameters form and what they are used for.
- SQL command timeout – Here you can enter the SQL command timeout.
- Try count – Here you can enter the number of times that a failed stage of the data transfer will be retried. If you enter a zero in this field, the number of retries is unlimited.
- Shared access signature timeout in minutes – A shared access signature, or SAS, is used to delegate access to resources in the storage account. An SAS can grant clients access to resources without sharing account keys. You can center the timeout in minutes in this field for SAS.
- Retention period in days – Here you can enter the number of days that upload session history, download session history, and data packages in the working folders will be retained.
- Current batch job – Here you can define the batch job; this is a link that will take you to the Batch jobs screen.
- Current batch status – This field will display the status of the current batch job that is displayed in the Current batch job field.
- Clean up irrelevant master data after sync – Here you can clean up irrelevant master data in offline database or Retail scale unit database to reduce volume.
Each of these fields are important, as they manage the communications between Microsoft Dynamics 365 for Operations and your retail channels. You will also notice that the fields in this form are quite a bit different than in AX 2012 R3.