Infor CloudSuite and Microsoft Dynamics 365 Sales integration

What moves between them

Suppliers and customers flow from Infor CloudSuite into Microsoft Dynamics 365 Sales. ml-connector polls the CloudSuite supplier and customer list endpoints on a regular schedule, transforms each record into Dataverse account or contact schema, and writes or updates the corresponding record in Dynamics 365 Sales via OData. Purchase orders and invoices from CloudSuite can be mapped to Dynamics 365 Sales quote and order entities if sales-stage tracking is required. The flow is one-way: CloudSuite is the system of record for vendor and customer master data, and Dynamics 365 Sales consumes those updates.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the Infor CloudSuite side, it retrieves the OAuth token endpoint and base URL from the per-customer ionapi file, requests a bearer token using the service account credentials, and polls the supplier and customer list endpoints, filtering by modified date to detect changes. It handles CloudSuite's variable pagination: M3 list calls use cursor-based filtering, and some SyteLine calls require RecordCap and Bookmark. Tokens are refreshed proactively before expiry to avoid interruptions. On the Dynamics 365 Sales side, ml-connector authenticates via Microsoft Entra ID using client credentials, presents the bearer token on each OData request, and maps the CloudSuite supplier record (name, address, contact) to a Dataverse account or contact entity. Because Dynamics 365 Sales payloads are limited to 256 KB, large customer lists are broken into smaller batches. The integration polls on a schedule you define rather than using CloudSuite BOD/XML messaging, so there is no need to configure ION Desk document flows. Every record includes a job ID for deduplication, full audit trail, and can be replayed if a downstream write fails.

A real-world example

A mid-sized industrial distributor runs Infor CloudSuite M3 for procurement and finance across three regional warehouses. The sales team uses Microsoft Dynamics 365 Sales to manage accounts and the quote-to-order pipeline. Before the integration, sales reps would manually search for supplier contact details or customer information across both systems, and when a new vendor was added to CloudSuite for a direct-buy program, someone had to re-enter that vendor as an account in Dynamics 365 Sales by hand. With CloudSuite and Dynamics 365 Sales connected, suppliers automatically appear as accounts in the CRM with current contact information, sales reps can see procurement history alongside opportunity details without context-switching, and adding a new vendor to CloudSuite puts that vendor in front of sales within hours.

What you can do

• •Sync suppliers from Infor CloudSuite into Microsoft Dynamics 365 Sales as accounts or contacts with name, address, and contact details.
• •Maintain customer master data alignment between CloudSuite and Dynamics 365 Sales, automatically updating records when either system changes.
• •Handle OAuth 2.0 authentication on both sides, refreshing tokens proactively before expiry.
• •Poll CloudSuite on a schedule you define, supporting M3 cursor-based pagination, SyteLine Bookmark filtering, and other product-line variations.
• •Batch large supplier or customer lists to respect Dynamics 365 Sales 256 KB webhook payload limits, with full audit trail and replay on failure.

Questions

Which direction does data move between Infor CloudSuite and Microsoft Dynamics 365 Sales?

The main flow is from Infor CloudSuite into Microsoft Dynamics 365 Sales. Suppliers and customers created or updated in CloudSuite flow into Dynamics 365 Sales as accounts or contacts. Sales contact updates can flow back to CloudSuite customer records if desired. Because Dynamics 365 Sales is CRM-only and does not include AP/AR ledger entries or GL accounts, purchase orders and invoices can be mapped to quote and order entities for sales-stage tracking if needed.

How does the integration handle CloudSuite's variable pagination across different product lines?

Infor CloudSuite uses different pagination schemes depending on the product line: M3 uses cursor-based filtering, SyteLine uses RecordCap and Bookmark parameters, and LN/FSM may use OData. ml-connector detects the product line from the ionapi credentials file and applies the correct pagination method for each list call, so suppliers and customers are retrieved completely without manual configuration.

What happens when a Dynamics 365 Sales webhook payload exceeds the 256 KB limit?

When a large customer or supplier list would exceed 256 KB, ml-connector breaks it into smaller batches and writes each batch as a separate request. Because each batch carries a unique job ID, if one batch fails, only that batch is replayed, and the full customer list eventually reaches Dynamics 365 Sales without losing data.