Steps to configure retail when copying or restoring database between environments in Dynamics 365 Retail

Hi Guys,

The general business scenario we will be moving database from Production servers to Sandbox, UAT, DEV servers and after every restore there are few steps we need to follow to make system up and running.

I would like to list out the steps needs to be followed to configure retail when copying or restoring database between environments in Dynamics, please find the same below.

1. Run the Environment retargeting tool from LCS.

When you do any kind of copying between environments in Dynamics there are some settings related to Retail which are copied that are actually wrong for the destination environment.

To fix these you need to apply tool called Environment retargeting tool  and also its knowsn Retail Reprovisioning tool.

This tool needs to be run every time we do restore and all the environments. Irrespective if they use Retail components or not.

a.      Please make sure that we have the latest version of the tool.

b.      To check the same go to LCS – Asset Library. Go to Software Deployable Packages – Import  and Select the latest Environment Reprovisioning tool.

c.      Please select the latest tool and click on Apply.

d.      Once its applied then it will get Queued and start servicing, this operation will finish within 30 min (Please make sure to use latest version of tool).

      2. Once retargeting tool applied then you need to run these five steps.

a.      Navigate to the “Organization administration > Number sequences > Number sequences” and click on “Generate” 

b.      Open the "Retail Parameters" form, and press the "Initialize" link under the "General" tab. Answer "Yes" to the prompt. This will provide any new Retail seed data. 

c.      Open the "Initialize Retail Scheduler" form, and run it with "delete existing configuration" set to "yes". 

d.      Restart the "Microsoft Dynamics AX Batch Service" on all AOS VMs. This will update any cached connection credentials that may be used when running a CDX data sync. (done by DSE if PROD) 

e.      Navigate to the "Channel Database" form and run a CDX 9999 sync (full sync). This should succeed if everything is properly configured for retail. 

And also please have a look at blog to understand about Datawriting batch job

 Hope this helpful and Next post will be explain common issues we face when we run distribution scheduler job.

Thanks for reading!

All about Data writing job "Default channel database batch job(RetailCdxChannelDbDirectAccess)" in Dynamics 365 Retail

Hi Guys,

Today I would like to discuss about the importance of  "Default channel database batch job(RetailCdxChannelDbDirectAccess)" in Dynamics 365 Retail and its role.

This job main duty is to check all Download sessions and Upload sessions with status “Available”, then it will apply the data to respective target DB's (AX or channel DB).

There will be few case we could see all distribution schedule jobs struck in executing state and not Applied, there could be following reasons for this issue.

1. Please check if the “Data writing job” assigned to channels

2. Make sure “Default channel database batch job(RetailCdxChannelDbDirectAccess)” is running

3. Restart the “Microsoft Dynamics AX Batch Service” on all AOS VMs. This will update any cached connection credentials that may be used when running a CDX data sync. (done by DSE if PROD => you need to raise a ticket)

How to setup Data writing batch job or recreate the same if existing have issues:- 

      The DataWritingBatchJob is automatically generated by the system when we run a full sync- 9999 job, it will create the batch job and update that field.

    

      Please run a Full Sync-9999 job and it will recreate the missing Retail DataWritingBatchjob.

      If the issue is still persists and the system thinks it already exists, then you need to reset DataWritingBatchJob in your UAT AX DB as shown below for RCSU channel database.   

      Restart the “Microsoft Dynamics AX Batch Management Service” under Services.msc on all AOS VMs.

      Now the next time when you run a Full sync-9999 job it should automatically recreate the the DataWritingBatchJob and update the field.

Hope this helps, I will come up with next blog post about Retail configuration and how to make distribution schedule jobs up and running when we do restore DB in D365 Retail.

Thank you!

User personal information like Favourites, Cues Personalization’s and User roles access in AX 2012 R3

Hi Guys ,

I would like to discuss today about "User personal information in AX", recently I was working for one of our customer and we are using AX 2012 R3 Retail with Store front.

They planned to move servers from one hosting partner to another hosting partner.

I am sure here many people could have done this for many customers earlier and  I would like to share one of the business criteria which customer requested, as we all know when customer is working in daily basis in our ERP system, it’s more important for them to save their personal information as well.

In the process of moving server from one hosting partner to another there is a chances to loose this info as we gonna import users from new active directory and there might be chances that users Id’s would be different compared to old system based of their user creation process.

So just to save user info we have dig into system and came across following tables which holds user personal info.

1.     Personalized Favourites

a.      SysPersonalization

2.     Personalized Cues on roles centre

a.      SysCue

b.     SysCueGroup

c.      SysCuePersonalization

3.     Form Personalization’s.

a.      SysLastValue

     4.     User security roles based on organization access
                  a.     SecurityUserRole
                  b.     SecurityUserRoleCondition
                  c.     OMUserRoleOrganization

These all tables has a User Id relation, so what I have done is , I have listed and matched the all users from Hosting partner A and B in CSV file. then written a script to update their Id's from Old to New

This applies for Dynamics 365 as well except Cues.

Hope this info helpful!

Your feedback is always welcome and meet you guys with new post!