Dynamics 365 Finance & Operations label printing: X++, REST and file integration
Print product, license-plate and shipping labels from Dynamics 365 F&O / Supply Chain Management through the REST API, watched folders or direct database views — with warehouse scenarios and a checklist.
Dynamics 365 Finance & Operations (now Supply Chain Management) runs warehouses through advanced warehousing: license plates, work orders, waves and mobile device flows. Each of those steps produces a label, and the standard document routing is tied to Windows print management. EtikStudio takes the same events and prints on any printer, in any language, at any site.
Which integration paths fit Dynamics 365
| Path | Fit | Why |
|---|---|---|
| REST API | Best | From X++ (System.Net.Http) or from a Power Automate / Logic Apps flow on a business event: the REST API with the record's fields; job status back to D365. |
| Watched folder / FTP | Good | Data management exports (CSV/XML) or a recurring data job drop files; EtikStudio prints the batch. No X++ needed. |
| Embedded data (ODBC) | Complement | Read-only views on the BYOD / Azure SQL export or entity store: item, batch, license plate and customer data pulled at print time. |
| Connector + relay | Good | Cloud-hosted D365 prints to on-premise printers without VPN through the linked connector at each warehouse. |
Warehouse and production scenarios
| Process | Label | Trigger |
|---|---|---|
| Inbound | License-plate label at receiving, batch and expiry | Registration of purchase order lines, license plate creation |
| Production | Finished-goods and container labels with batch and serial | Report as finished, production order status change |
| Outbound | Shipping, SSCC pallet and carrier labels | Wave processing, work completion, shipment confirmation |
| Retail | Shelf and price labels from released products | Price change, assortment update |
Recommended flow
Use business events (or a Power Automate trigger) for the step that needs the label — license plate created, work completed, shipment confirmed — and call the REST API with the fields; keep the label design in EtikStudio and the printer mapping per warehouse. For sites that cannot reach the D365 tenant from the printer network, the connector + relay path prints locally with no inbound firewall rule.
Implementation checklist
- Choose the trigger: X++ extension, business event + Power Automate, or a data management export schedule.
- Map D365 warehouses and printers to EtikStudio printer names; one connector per site.
- Decide which fields travel in the call and which the label reads from a view (item description, allergens, prices).
- Validate license-plate barcodes and SSCC with a verifier on the target printers.
- Keep document routing in D365 for reports; move only labels to EtikStudio.
How EtikStudio handles it
The REST server answers each call with a job id and status, so D365 can log success or retry. Templates are versioned centrally, and the same design prints on the Zebra printers in one warehouse and the TSC printers in another.
Integration details vary by ERP version, deployment and licensing. Adapters and worked examples are provided during implementation.