D365 Finance & Operations and Dynamics AX Forum

Expand all | Collapse all

Commerce: Channel Database

  • 1.  Commerce: Channel Database

    Posted Jan 22, 2021 10:40 AM
    Trying to setup a second channel database in D365 Commerce and seems as though all the steps have been followed correctly from the functional setup side.   However, when running the distribution schedule jobs, they all stay in AVAILABLE status and not APPLIED.  We've even restarted everything.  I wanted to find out if anyone else had this problem or if I missed a step.  Perhaps someone has a cheat sheet on this setup.

    Here are steps I did:
    1) Created Channel Profile
    2) Created Channel Database Group
    3) Created Channel Database
    4) Assigned a store location
    5) Restarted server
    6) Run Distribution schedule for Full Sync from Channel Database
    7) Reviewed Download Session and saw the jobs in AVAILABLE status but never getting APPLIED.

    Any pointers would be greatly appreciated.

    Rod Helmick
    RTHGlobal, Inc
    Cave Creek

  • 2.  RE: Commerce: Channel Database

    Posted Feb 09, 2021 10:54 AM
    Problem resolved.  No need to reply.

    Rod Helmick
    RTHGlobal, Inc
    Cave Creek

  • 3.  RE: Commerce: Channel Database

    Posted Feb 10, 2021 04:29 PM
    Thanks for letting us know.

    Perhaps you could share how you resolved it?

    Daniel Zook
    Director of IT
    Dalton OH

  • 4.  RE: Commerce: Channel Database

    Posted Feb 11, 2021 11:18 AM
    The missing step was actually setting up the Scale Unit on LCS.  I've usually had infrastructure people doing this on past implementations so kinda took it for granted that it was there.  You need to login to LCS, go into the project, select the appropriate environment, select manage, select commerce scale unit, and then select Initialize.  You will need to select the region for this.  This may take a couple hours to run but once that is deployed, you need to apply any extensions you may have associated to customizations.   Once that is done, return back to D365 workspaces and begin to setup your channel profiles and database.

    Rod Helmick
    RTHGlobal, Inc
    Cave Creek

  • 5.  RE: Commerce: Channel Database

    Posted Mar 08, 2021 09:43 AM
    Hi Rod,
    Thanks for your reply.
    Just in case it helps anyone in the future, there are several status's for the distribution jobs, and it can be helpful to know the progression and what each means:

    Started -Indicates you have run the distribution job, but it has not finished gathering the data from the tables in the D365 database yet.

    Available - This means that the data has all been retrieved from the D365 tables, and the data has been stored in a file, that is put in the 'working folder'.  This is where the work that Dynamics 365 headquarters does stops.
    Note:  If nothing happens from here, it should indicate to you that the 'other piece', as you found out the Cloud scale Unit, or store scale unit, is not running.

    Downloaded - The CSU runs a service called the 'Async client service'.  It is the job of this service to constantly look for any files that are 'available'.  If you have a 'store scale unit' this runs as a windows service, and can be 'stopped' manually, so you may want to check that this is running if you are stuck before this step.  Once the Async client service runs and downloads the file that was created in headquarters to its local machine (either the CSU running in the cloud, or the store scale unit running on a store machine), it will change the status to 'downloaded'.

    Applied - Finally, the Async client service will read the file that it has downloaded and it will begin generating sql to insert/update/delete the records in the channel database.  If a sql error occurs, the system won't get to this status.  This could happen if there is a timeout in trying to apply a whole lot of records.  But typically this just takes some time for this to run, and eventually you will see a status of 'Applied'.

    In version 2012 there was a 'process status messages' button and batch job that you needed to run to update the status's that showed within headquarters. This is because these status's are actually in a 'Message' database, and headquarters is just reading the files from that database.  So if you don't see them updating in 2012, make sure you click this button in the form and run that job.

    Hope that helps some for the future.

    Peter Ramer
    Greenwood Village CO

If you've found this thread useful, dive deeper into User Group community content by role