Microsoft Dynamics
Infoveave Data Automation — RESTful
Dynamics 365 CRM data in your workflow — without custom connectors or scripting.
Microsoft Dynamics 365 is the primary CRM for thousands of mid-market and enterprise organizations. Sales orders, account records, contacts, invoices, and opportunities all live in Dynamics — and all need to flow into analytics dashboards, reporting databases, and downstream business processes. Microsoft Dynamics activity connects directly to Dynamics 365 CRM via its native API, retrieves entities using OData filter syntax, and returns a structured table ready for transformation and loading. Multi-company support means a single activity can query across Dynamics business units or legal entities in one workflow run.
What Microsoft Dynamics does
Connect to Microsoft Dynamics 365 CRM and retrieve accounts, contacts, sales orders, and other entities inside your Infoveave workflow. Native Dynamics integration with OData filter support, multi-company queries, and configurable retry handling.
When to use Microsoft Dynamics
- You need to extract accounts, contacts, sales orders, invoices, or other entities from Microsoft Dynamics 365 CRM
- You want to filter Dynamics entities using OData expressions before ingesting them into a pipeline
- Your organization runs multiple Dynamics legal entities and you need to query across companies using the Cross Company flag
- You are building a pipeline that syncs Dynamics CRM data to a data warehouse, analytics platform, or reporting database
When to avoid it
- You are connecting to an OData service that is not Dynamics 365 — use Retrieve OData for generic OData endpoints
- You are calling a standard REST API — use Execute API
- You are querying a relational database — use Execute Query
- You are querying a GraphQL endpoint — use Execute GraphQL
Where it fits in your Infoveave automation
Microsoft Dynamics is one step inside a multi-step Infoveave workflow. Chain it with other activities — no code, no manual hand-offs.
Build this workflow visually in Infoveave Data Automation — drag, connect, and schedule with no infrastructure setup.
How teams use Microsoft Dynamics
Real scenarios where this transformation saves hours of manual work.
Sales Order Sync to ERP
A daily finance workflow retrieves confirmed sales orders from Dynamics 365 CRM filtered by 'fulfillmentStatus eq Confirmed and orderDate ge 2026-04-10', then loads them into the ERP database via Insert into Database. Cross Company is enabled to pull orders across all business units in a single workflow run.
Customer Account Master Data Sync
A weekly data governance workflow extracts the full customer account master from Dynamics CRM — including billing address, credit limit, payment terms, and account manager — and loads it into the customer master table in the data warehouse. The filter 'statecode eq 0' ensures only active accounts are included.
Opportunity Pipeline Report
A monthly reporting workflow retrieves all open opportunities from Dynamics 365 filtered by estimated close date in the current quarter, with retry set to 3 to handle peak CRM load periods. The opportunity table feeds into a pipeline probability model and generates a forecast dashboard for the leadership team.
See Microsoft Dynamics in action
Input data (left) is transformed using the configuration below. The output table (right) is ready for dashboards or downstream steps.
dynamics365-prodsalesorders3fulfillmentStatus eq 'Confirmed' and orderDate ge 2026-04-0101000trueInput Data
| (Dynamics 365 connection and entity configuration — no row input required) |
Output Data
| OrderID | CustomerName | OrderDate | TotalAmount | Status |
|---|---|---|---|---|
| SO-20260401-001 | Acme Corp | 2026-04-01 | 15800.00 | Confirmed |
| SO-20260402-002 | Global Industries | 2026-04-02 | 9250.00 | Confirmed |
Configuration
Key fields to configure in the Infoveave workflow builder. Full reference available in the documentation.
Connection
The registered Microsoft Dynamics 365 connection in Infoveave Studio. Configured using OAuth (Azure AD app registration) or API key authentication with the Dynamics 365 instance URL. Required permissions are scoped to the entities being accessed.
Resource Name
The Dynamics 365 entity set name to query — such as 'accounts', 'contacts', 'salesorders', 'invoices', or 'opportunities'. Uses the Dynamics CRM logical entity set names as defined in the Dynamics metadata.
Number of Retries
Number of times the activity retries the Dynamics request on transient failure (timeout, HTTP 429, HTTP 503). Default is 3. Useful during peak CRM load periods when Dynamics API responses may be delayed.
Filters
OData $filter expression for filtering Dynamics entities. Supports standard OData operators (eq, ne, gt, lt, ge, le, and, or) applied to Dynamics field names. Examples: 'statecode eq 0' for active records, 'createdon ge 2026-01-01' for recent records.
Cross Company
When enabled, the query runs across all companies (legal entities) in the Dynamics 365 environment rather than being scoped to the default company. Required for multi-entity organizations that need consolidated data across all business units in a single request.
Frequently asked questions
Everything you need to know about Microsoft Dynamics in Infoveave.
Also in RESTful — and what runs before & after
Transformations in the same family as Microsoft Dynamics, often chained together in the same Infoveave workflow.
Part of Infoveave Data Automation
80+ transformations. Zero manual steps.
Microsoft Dynamics is one of over 80 transformation activities available inside Infoveave workflows. Chain transformations together — no code, no exports, no waiting for IT.
Ready to see Infoveave in action?
