Configure distribution schedules
The data distribution framework is a Commerce Headquarters (HQ) tool that maps and facilitates the transfer of asynchronous (non-real time) groups of data between Commerce HQ and groups of Commerce channel databases. Master data is configured in Commerce HQ and distributed to the Commerce channels, which is called a Download. Transactional data is created in the Commerce channels and then pulled back into Commerce HQ, which is called an Upload.
The data distribution framework is driven by distribution schedules. Distribution schedules are records that link logical groupings of tables and fields, called Scheduler jobs, that are distributed to logical groupings of channel databases, called Channel database groups.
Each distribution schedule has a data direction (Download or Upload). All stores can be inserted into the Default channel database group.
When the seed data is initialized, all required data is automatically populated with standard names and identification numbers. This process will be consistent for all base configurations across all implementations globally.
For example, the 1120 Modes of delivery distribution scheduler job will push all Commerce HQ tables that are relevant to the modes of delivery configuration to the channel databases that are defined in the channel database groups. By default, only one of each distribution job grouping is created. Additional copies of the distribution schedules can be created for business needs, such as pushing or pulling data more often than other stores.
A 9999 job is also created. The job contains all available scheduler jobs, which can help when you are pushing all the data that is needed.
The Distribution schedules page can be found under Retail and Commerce > Retail and Commerce IT > Distribution schedule.
The distribution schedules should be configured to run in predetermined intervals by using the Create batch job functionality or manually through the Run now button. The history of these records is tracked for user visibility to confirm whether the data did or did not successfully push to the stores. If a failure occurs, the process can be run again from within the History page.
The distribution schedule records use SQL change tracking in the system to determine what data should be inserted, updated, or deleted in the channel database groups, called a delta (or changes only).
The first time that the job is run, or when the SQL change tracking settings dictate that a full push is required (typically around three days), a full push of all data can be sent to the store. Existing data in those tables will be truncated (fully deleted) and the new data will be inserted. SQL change tracking is aligned to the Distribution scheduler records, to the tables, not just the scheduler jobs. This Full data sync process can also be manually run through the Channel Database page. This process does not use a change tracking engine.
The following page can be found under Retail and Commerce > Headquarters setup > Commerce scheduler > Channel database.
The Channel database groups are each defined as having a Commerce channel schema. The schema aligns to a version of a database, such as AX2012R3 or AX7. This alignment allows for use cases for different versions of the Dynamics Store Commerce in the field and for constructing schemas and mappings for non-Dynamics Store Commerce databases.