Ellipse Gradient for Header

Integrate Microsoft Dynamics 365 with Martini

Integrate Microsoft Dynamics 365 applications through the Dataverse OData v4 Web API and Dataverse event mechanisms. Martini provides the workflow orchestration, REST API consumption, transformation, scheduling, webhook handling, authentication configuration, and operational controls needed to synchronize accounts, contacts, leads, opportunities, quotes, orders, and invoices with enterprise systems.

Integration PointSupported by Microsoft Dynamics 365Common use casesHow Martini supports it
Reporting and analytics extractionYes, through REST APIsExtract accounts, contacts, opportunities, orders, and invoices for a data warehouse, forecasting model, or operational reporting process. Use targeted queries and paging rather than retrieving unnecessarily broad payloads.Martini can call Dataverse REST endpoints to extract selected columns and related data for a warehouse or reporting process. For read-oriented analysis, Dataverse TDS access may be considered by the overall architecture, while the Web API remains the preferred interface for transactional integration operations.
Bulk and batch operationsYes, through REST APIsLoad ERP customers, contacts, orders, or invoices into Dataverse and group create, update, or upsert operations. Capture failed records separately so successful operations do not require unnecessary reprocessing.Martini can orchestrate Dataverse bulk or OData batch requests through REST services and can process large source datasets with mapping, batching, controlled concurrency, and error handling. Batch sizes and throughput should be tested against the target environment.
Incremental export APIsYes, for tables with change tracking enabledSynchronize modified accounts and contacts to an ERP or warehouse without repeatedly scanning every row. Persist continuation state only after downstream processing succeeds and retain a recovery strategy if the state is lost.Martini can use Dataverse change tracking when enabled, sending the required preference and persisting the returned delta link for subsequent cycles. When change tracking is unavailable, a modified-date or watermark approach can be implemented subject to table behavior and resynchronization requirements.
WebhooksYes, through HTTP endpointsProcess lead creation or qualification, opportunity changes, and other registered Dataverse events. Add idempotency, authentication checks, logging, and retry handling for repeated or failed deliveries.Martini can receive Dataverse webhook calls through a webhook trigger, ad-hoc REST URL, or dedicated REST API endpoint. The workflow can validate the request, retrieve the authoritative row when the payload contains only execution context, and route the event to downstream processing.
REST APIsYesProvide controlled internal access to accounts, contacts, opportunities, quotes, orders, or invoices while hiding Dataverse-specific contracts. Integrate Dynamics 365 with ERP, finance, marketing, fulfillment, databases, files, and other APIs.Martini can consume the Dataverse OData v4 Web API using OAuth 2.0 and expose its own REST API façade around Dynamics 365 operations. Workflows can map canonical requests to Dataverse logical names, invoke GET, POST, PATCH, DELETE, association, and action operations, and translate responses.

Exposes data and business events

Dynamics 365 REST APIs

Use the Dataverse OData v4 Web API to retrieve, create, update, delete, associate, and upsert Dynamics 365 records. Martini can normalize Dataverse payloads and route them to ERP, data warehouse, marketing, finance, or internal API processes.

How This works in Martini

In Martini, configure a REST-consuming service for the environment-specific Dataverse URL and OAuth bearer-token flow. Select only the required columns, process @odata.nextLink values for paging, map the response into a canonical model, and invoke downstream services or databases. For writes, use the appropriate HTTP operation and apply alternate-key upserts where a stable external identifier is available.

Example Martini workflow

Schedule workflow
Authenticate request
Query Dataverse
Page results
Map fields
Upsert records

Dynamics 365 Webhooks

Dataverse webhooks can notify Martini when a registered event occurs, such as a lead or opportunity change. The event commonly contains execution-context information rather than a complete business record, so the integration may need to retrieve the changed row before forwarding it.

How This works in Martini

Expose a Martini HTTP endpoint through a webhook trigger, ad-hoc REST URL, or REST API operation. Validate the inbound request, extract the table and row identifiers, retrieve the current Dataverse record when necessary, and route the normalized event to downstream processing. Add idempotency and error handling so repeated deliveries do not create duplicate effects.

Example Martini workflow

Receive webhook
Validate headers
Extract identifiers
Retrieve record
Map event
Route downstream

Scheduled Synchronization

Scheduled synchronization is appropriate for recurring account, contact, order, or invoice exchange with an ERP, warehouse, or reporting platform. Dataverse change tracking can reduce repeated full-table reads when it is enabled for the relevant table.

How This works in Martini

Configure a Martini scheduler-triggered workflow that calls Dataverse with a stored delta link or carefully designed modified-date watermark. Persist the returned continuation state only after successful downstream processing, then apply controlled paging, mapping, batching, and retries. If continuation state is lost or unavailable, implement a defined full-resynchronization strategy.

Example Martini workflow

Start schedule
Load continuation state
Fetch changes
Map records
Write downstream
Persist state

Common Integration Patterns

Pattern 1

When to use this pattern

Use this pattern when an ERP or analytical platform needs recurring account and contact updates without a full-table extraction on every run. It supports an initial load followed by change-tracking or watermark-based synchronization.

Data Flow
Microsoft Dynamics 365
Martini
ERP or data warehouse
Example Mapping
Microsoft Dynamics 365 FieldCanonical FieldTarget Field
namecustomerNamecustomer_name
accountnumbercustomerNumberexternal_customer_id
primarycontactidprimaryContactIdprimary_contact_key
modifiedonmodifiedAtlast_modified_at
Martini Implementation

Create a scheduled Martini workflow that obtains an OAuth token, queries the Dataverse Account and Contact entity sets, and follows the returned paging or change-tracking continuation links. Map Dataverse logical names and lookup values to the ERP or warehouse model, perform downstream create or upsert operations, and persist the continuation state after successful processing. Apply request filtering, controlled concurrency, and retry handling for transient failures.

Martini features used:
  • REST API consumption
  • Scheduler trigger
  • Mapping
  • JSON handling
  • Error handling

Pattern 2

When to use this pattern

Use this pattern when lead creation or qualification should initiate near-real-time enrichment, marketing notification, assignment, or onboarding work. It is also suitable for opportunity events that require downstream processing.

Data Flow
Microsoft Dynamics 365
Martini
Marketing platform
Example Mapping
Microsoft Dynamics 365 FieldCanonical FieldTarget Field
leadidleadIdsource_lead_id
emailaddress1leadEmailemail
statuscodeleadStatuslead_status
leadsourcecodeleadSourcesource
Martini Implementation

Configure a Dataverse webhook to call a Martini HTTP endpoint. The workflow validates inbound headers and extracts the execution context and row identifier, then retrieves the current Lead through the Dataverse Web API when the event is not a complete record. Martini maps status, source, contact details, and identifiers into the marketing platform contract and applies idempotency and operational logging before forwarding the event.

Martini features used:
  • Webhook endpoint
  • Start Trigger Node
  • REST API consumption
  • Mapping
  • Error handling

Pattern 3

When to use this pattern

Use this pattern when the ERP owns external customer, order, or invoice identifiers and Dynamics 365 must be kept current. Alternate keys provide deterministic matching while batch processing improves throughput for controlled migration or recurring loads.

Data Flow
ERP
Martini
Microsoft Dynamics 365
Example Mapping
Microsoft Dynamics 365 FieldCanonical FieldTarget Field
customer_numbercustomerIdaccountnumber
customer_namecustomerNamename
order_numberorderIdordernumber
total_amountorderTotaltotalamount
Martini Implementation

Receive ERP customer, order, or invoice records through a supported API, file, database, or message source. Map them to Dataverse table and relationship structures, resolve references using alternate keys where configured, and issue PATCH upsert requests to prevent duplicates. For larger loads, group requests into tested batches, record returned Dataverse identifiers, and isolate failed records for controlled reprocessing.

Martini features used:
  • REST API consumption
  • Mapping
  • JSON handling
  • Batch processing
  • Error handling

Pattern 4

When to use this pattern

Use this pattern when internal applications need controlled Dynamics 365 access without directly depending on Dataverse table names, OAuth configuration, lookup syntax, or customer-specific business rules. It centralizes validation, transformation, auditing, and error translation.

Data Flow
Internal applications
Martini
Microsoft Dynamics 365
Example Mapping
Microsoft Dynamics 365 FieldCanonical FieldTarget Field
customerNamecustomerNamename
customerExternalIdcustomerExternalIdaccountnumber
ownerIdrequestedOwnerownerid
closeDaterequestedCloseDateestimatedclosedate
Martini Implementation

Expose a Martini REST API with a stable canonical request contract. Validate headers, parameters, and body data at the workflow entry point, map the request to Dataverse entity set and logical field names, and invoke the required Web API operation using centrally managed authentication. Translate Dataverse responses and errors into the internal contract so consumers are insulated from environment URLs, table naming, and implementation details.

Martini features used:
  • REST API creation
  • Start Trigger Node
  • Mapping
  • Authentication and secrets
  • Error handling

How to build a Microsoft Dynamics 365 integration in Martini

Objective

Establish the actual Dataverse contract before building Martini services. Dynamics 365 applications and customer environments can vary, so the integration should be based on stable logical names, relationships, permissions, and documented API behavior rather than display labels alone.

Instructions in Martini

  • Identify the Dynamics 365 application and Dataverse environment in scope.
  • List the tables, logical names, entity sets, relationships, choice values, and operations required.
  • Define source and target identifiers, alternate keys, ownership rules, and idempotency behavior.
  • Choose REST, webhook, scheduled, or messaging-based processing for each data flow.

Objective

Prepare secure unattended access to the target environment. Test with the actual application user because token acquisition alone does not confirm table, record, business-unit, or field-level access.

Instructions in Martini

  • Register an application in Microsoft Entra ID.
  • Create the corresponding Dataverse application user.
  • Assign only the required Dataverse security roles.
  • Configure the environment URL and OAuth client settings per environment.
  • Store secrets and certificates using Martini-supported mechanisms.

Objective

Implement the Dataverse API layer in Martini. Keep queries focused, preserve continuation URLs, and use alternate-key upserts or explicit relationship handling where the source system must create or update related records.

Instructions in Martini

  • Create REST-consuming services for Dataverse operations.
  • Set targeted OData queries with selected columns and filters.
  • Implement paging using the returned @odata.nextLink.
  • Add create, update, delete, association, or upsert operations as required.
  • Use JSON handling for request and response payloads.

Objective

Orchestrate the business workflow around the API calls. Martini can combine scheduled and event-driven processing with transformation and routing logic so each integration path has a clear trigger, data contract, and downstream action.

Instructions in Martini

  • Add a scheduler for recurring synchronization.
  • Add a webhook or REST trigger for inbound Dataverse events.
  • Validate inbound headers, parameters, and payload structure.
  • Retrieve the authoritative row when an event contains only execution context.
  • Map Dataverse data into canonical and downstream models.

Objective

Make the integration operationally reliable and maintainable. Dataverse paging, continuation state, service-protection limits, repeated webhook delivery, and environment-specific configuration should be treated as core design concerns rather than late-stage exceptions.

Instructions in Martini

  • Handle authentication, permission, validation, lookup, mapping, and downstream failures separately.
  • Apply controlled retries and backoff for transient failures and throttling.
  • Log processing identifiers, source keys, response statuses, and outcomes.
  • Persist delta links or watermarks after successful processing.
  • Deploy configuration separately for each environment and monitor runtime behavior.

Common Data Objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
AccountSynchronize customer organizations, addresses, ownership, classifications, and external customer identifiers.ERP, data warehouse, finance platformMartini reads and writes Account rows through Dataverse REST operations, including lookup resolution, external-key upsert, and mapping to the target customer model.
ContactKeep individual customer, communication, consent, and account-association data aligned across systems.ERP, marketing platform, customer data platformMartini maps Contact fields and parent-account relationships, resolving the related account by GUID or an alternate key before creating or updating the contact.
LeadCreate leads from forms or campaigns and synchronize qualification status and source identifiers.Marketing platform, enrichment service, sales systemsMartini receives or extracts Lead rows, maps qualification and source values, and can route records for enrichment, ownership assignment, or downstream onboarding.
OpportunitySynchronize pipeline, expected revenue, close dates, owners, and sales-process status.ERP, forecasting platform, data warehouseMartini retrieves or upserts Opportunity rows, maps customer references and sales-stage values, and translates currency, probability, and value fields for downstream systems.
QuoteTransfer commercial proposals and their pricing context into fulfillment or document processes.ERP, document generation, finance platformMartini handles Quote data and related product-line structures through REST requests, with explicit mapping for prices, discounts, terms, and opportunity references.
Order or InvoiceSynchronize confirmed purchases and billing documents with operational and financial systems.ERP, accounting, tax, fulfillmentMartini maps Order or Invoice records, resolves related account and product references, and uses paging, batching, and controlled retries for larger exchanges.

Authentication and security considerations

Use Microsoft Entra ID and OAuth 2.0

Dataverse Web API requests require OAuth 2.0 bearer tokens issued by Microsoft Entra ID. For unattended integrations, register an application, create an application user in the target Power Platform environment, and assign the security roles required for the tables and operations in scope.

Configure the Dataverse environment URL, tenant information, client ID, and client secret or certificate through Martini environment configuration and supported secret-management mechanisms. Do not embed credentials in workflows or request definitions. A valid token does not by itself provide broad access; Dataverse security roles, business-unit rules, record permissions, and field-level permissions still apply.

Protect inbound events

When Dataverse webhooks or Azure-based event integrations call Martini, validate the configured headers, parameters, or authentication information before processing the event. Treat event payloads as execution context unless the delivery mechanism provides the complete record, and retrieve the authoritative Dataverse row when required.

Operation considerations

Plan Dataverse-specific contracts

Dynamics 365 applications do not share one universal schema. Confirm which application and environment are in scope, then use Dataverse logical names, entity set names, relationships, option values, and customer-specific metadata rather than relying only on display labels.

Use targeted OData queries with $select and appropriate filters. Process @odata.nextLink values without modifying them, and persist delta links or watermark state durably. Avoid unnecessarily large expansions and batch payloads.

Handle relationships and state

Design lookup binding, alternate-key resolution, association order, currencies, choice values, status fields, ownership, and business-unit permissions explicitly. A successful OAuth token acquisition does not guarantee that the application user can access or modify every row.

Design for service limits

Separate authentication, permission, validation, lookup, mapping, downstream, and transient HTTP failures. Apply controlled retries and backoff for throttling, limit concurrency, use appropriate batch sizes, and make webhook and write processing idempotent.

Why use Martini

Connect Dataverse-backed applications through REST

Martini provides a developer-oriented integration layer for Microsoft Dynamics 365 scenarios that use the Dataverse Web API. It can consume REST APIs with OAuth 2.0, expose REST endpoints, receive webhook events, schedule recurring workflows, and transform JSON payloads without coupling every consuming application directly to Dataverse implementation details.

Orchestrate reliable enterprise flows

Use Martini to coordinate account, contact, lead, opportunity, quote, order, and invoice synchronization with ERP, finance, marketing, fulfillment, database, file, and analytics systems. Workflow logic can address paging, change-tracking continuation state, alternate-key upserts, relationship resolution, batching, throttling, validation, and error handling.

Centralize security and operations

Keep environment URLs and sensitive credentials outside integration logic, apply the permissions of a dedicated Dataverse application user, and use Martini logging, debugging, and metrics capabilities to support troubleshooting. This creates a maintainable boundary between Dynamics 365 data contracts and downstream enterprise systems.

Frequently asked questions

Does Martini require a native Dynamics 365 connector?

Not necessarily. Martini can consume the Dataverse OData v4 REST Web API with OAuth 2.0, map payloads, expose HTTP endpoints, and orchestrate workflows without assuming a native Dynamics 365 connector. Product-specific Dynamics 365 applications may require their own documented APIs in addition to Dataverse.

Which credentials are required?

For an unattended integration, typically configure the Microsoft Entra tenant, application ID, client secret or certificate, Dataverse environment URL, and an application user associated with the app registration. The application user must have Dataverse security roles granting the required table and operation privileges.

How can records be synchronized incrementally?

Use Dataverse change tracking where it is enabled and persist the returned delta link as opaque continuation state. If change tracking is unavailable or the state is invalidated, use a carefully designed modified-date or watermark strategy and retain a full-resynchronization option.

How can duplicate records be avoided?

Define alternate keys based on stable external identifiers, such as an ERP customer number, and use PATCH-based Dataverse upsert operations. This is more reliable than matching only on names or email addresses.

How are Dynamics 365 events delivered to Martini?

Use a Dataverse webhook or an Azure messaging integration to deliver event notifications to a Martini HTTP endpoint. Martini can validate the request, retrieve the complete row when the event contains only context or identifiers, and route the normalized event to downstream systems.

How should large data loads be implemented?

Use OData paging and process each @odata.nextLink exactly as returned. For writes, use bulk or batch operations where appropriate, control concurrency, and implement retries with backoff for transient failures and HTTP 429 throttling responses.

Related Martini documentation

APIs

Workflows

Transformation

Reliability

Security

Build Maintainable Dynamics 365 Integrations

Use Martini to connect Dataverse-backed Dynamics 365 applications with APIs, databases, files, messaging endpoints, and enterprise workflows. Start with the Dataverse Web API contract, define stable external keys and relationship mappings, externalize credentials and environment URLs, and design paging, continuation state, idempotency, throttling, and operational handling into the integration from the beginning.

EXPLORE MARTINI
BOOK A DEMO