CSM Administration - Automations and Job Queues
Understanding and setting up CSM Automation Routines and Job Queues to run in the background.
CSM's automation routines handle key commerce activities (order retrieval, sales order creation, inventory sync, fulfillment updates, and listing management) on a defined schedule. A set of predefined routines is loaded automatically during setup.
Accessing Automation
- Walmart / Magento
- Search for API Automation and select the related link
- Amazon / Shopify / BigCommerce / WooCommerce
- Search for CSM Automation List and select the related link
| Field | Example Value |
|
Base: Enabled Include this routine in scheduled job queue execution. Uncheck to skip or run manually. |
|
|
Base: Sequence Execution order. Some routines depend on others completing first. |
10 |
|
Base: Type References the CSM module being involved. |
CSM Order Management |
|
Base: Code Unique routine identifier. Do not modify. |
ORDER_MANAGEMENT |
|
Base: Description Plain-language summary of what the routine does. |
Build retrieved acknowledged Sales Orders. |
|
Steps: Automation Type API: routines that run against an entire API Set rather than a specific Sales Channel. Useful for shared activities like Order retrieval, where a single routine pulls orders across all Channels using that API Set. Order: routines that process CSM Orders. These can create Business Central Sales Orders from data held in the CSM Order table, or retrieve additional order details from an external Sales Channel into that table. Fulfillment: routines that push fulfillment data (Shipments, Invoices, and Credits) from Business Central to an external Sales Channel. Required when the Sales Channel is configured to send fulfillment information on a scheduled basis rather than automatically. Listing: routines that exchange listing data between Business Central and an external Sales Channel, including creating Products on the external platform, sending Inventory updates, and pushing Price changes. |
|
|
Steps: Scheduled Frequency How often the routine runs within a given automation cycle. |
1 Minute |
|
Steps: Last Run Timestamp Auto-updated on successful execution. Used with Scheduled Frequency to determine next run eligibility. |
|
|
Steps: Parameter String Assigns a routine to a specific job queue group. Useful for separating execution by Channel or volume. |
|
|
Steps: API Set Code The API set providing the routine's underlying functionality. |
SHOPIFY |
|
Steps: API Function Code The specific API function used to move data, if applicable. |
|
|
Steps: CSM Properties Execution criteria or action instructions specific to this routine. |
|
|
Steps: Update Last Run Timestamp on Error Check to update the timestamp even when the routine fails. Default: only updates on success. |
Automation Codeunits
CSM includes two out-of-the-box codeunits:
| Automation Routine Type | Codeunit | Automation Code |
| Order Management | 70338249 | ORDER_MANAGEMENT |
| Listing Management | 70338246 | LISTING_MANAGEMENT |
Running a codeunit executes all enabled routines assigned to its automation code.
Housekeeping Automation
A platform-agnostic routine that handles maintenance:
- Deletes API Messages and Data Buffers per the retention period defined in CSM Setup
- Archives CSM Orders per each Sales Channel's archiving settings
Note: We recommend using Business Central's standard retention policies for data deletion. The housekeeping automation remains necessary only for CSM Order archiving.
Schedule housekeeping during low-activity periods (e.g., overnight). Running it regularly is strongly recommended. Unaddressed tables will grow until additional storage is required.
Maximum Run Time
By default, housekeeping identifies all eligible records and commits deletion as a single transaction. This is efficient, but any interruption rolls back all progress.
If record volume is too large for the routine to complete reliably, populate the Maximum Run Time field. This causes the routine to delete records one at a time for the specified duration, making each deletion permanent regardless of interruption; this is slower, but guaranteed.
Remove the Maximum Run Time once record volume returns to a manageable level.
Configuring Job Queue Entries
Manual execution is suitable for testing. For production, schedule routines using standard Business Central job queue entries.
To create an Order Management job queue entry:
- Search for Job Queue Entries and select the related link
- Choose New
- Set Object Type to Run to Codeunit
- Set Object ID to Run to 70338249
- If using parameter strings, enter the appropriate value in the Parameter String field
- Configure recurrence per standard Business Central practices
Note: Role Center automation buttons are hard-coded to default automation codes. Custom parameter string routines will not be triggered by those buttons.
When to use multiple job queues: In high-volume or multi-channel environments, assigning separate parameter strings per channel and running dedicated job queues per string reduces processing load and isolates failures.