Sunday, September 23, 2018

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!





3 comments:

  1. 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.

    ReplyDelete
  2. Thank you Ammar for adding additional info and its is very helpful and updated the same in blog as well.

    ReplyDelete