Talk to our team

Explore Uplyst

Esc

Popular places to start

platformEnterprise intelligence for the way you work.

Uplyst connects operational data, business relationships and real time events to support decisions across your enterprise.

integrationsConnect your enterprise systems.

Explore Uplyst integrations across business applications, data platforms, databases, event streams and industrial systems.

DocumentationTechnical guides for connected systems

Guides to enterprise architecture, semantic models, integration contracts, security and operations.

resourcesEnterprise intelligence in practice

Architecture, integration and governance guidance for connecting enterprise data with operational decisions.

Dynamics 365 integration

Dynamics 365 and the wider business

Customer records in a shared business model.

Dataverse tables describe accounts, contacts and commercial activity. Uplyst relates them to the orders, contracts and financial records held elsewhere.

Dataverse Web API
Tables, selected fields and record relationships
Microsoft Entra ID
Registered application identity
Uplyst
Customer context across sales, service and operations

Connect Dynamics 365 to Uplyst

For Dynamics 365 applications built on Dataverse, the Web API provides table data, metadata and relationships through OData 4.0. Selected records can be mapped into Uplyst's shared business model, connecting accounts, contacts and commercial activity with records in other systems.

Dynamics 365 is a family of applications. Finance and Operations exposes its own public data entities through a separate OData interface, so its connection is scoped independently of applications built on Dataverse.

Connect records through their relationships

The Dataverse environment, table and record ID identify each source record. Lookup fields relate accounts, contacts and other tables, while choice values describe business states.

Uplyst's model connects those identities and relationships to records elsewhere in the business. Map custom tables and calculated values using the definitions from the organisation's Dynamics implementation.

Dataverse dataConnected context
Account and contact recordsCustomer organisations and relationships
Lookup fieldsLinks between business records
Choice valuesBusiness states and classifications
Custom tablesProcesses specific to the organisation

Application identity and environment access

Dataverse API access uses OAuth with an application registered in Microsoft Entra ID. Automated access is associated with an application user and security roles in the Dataverse environment.

Those roles define the records and operations available to the integration. Permissions for each environment and credential management keep the connection aligned with the organisation's access policies.

UplystDataverse access example
Uplyst context readerDataverse application user
Environment
UK Sales
Security role
Customer context read
Table permissions
TableRead scopeWrite
accountOrganisationNot granted
contactBusiness unitNot granted

Create and delete privileges are not granted.

Configured column access

account.namecontact.fullnameReadable
account.creditlimitcontact.emailaddress1Restricted
Account relationship
contact.parentcustomeridaccount.accountid

Target type: account. Environment, table and record ID preserve source identity.

Table privileges and field security both apply. Reading customer context does not grant authority to amend it.

Work within Dataverse service limits

Dataverse service protection considers request count, execution time and concurrency. Rate-limited responses can include a Retry-After duration that controls when requests resume.

Request pacing, bounded concurrency and queued work allow synchronisation to progress within the service's capacity. Permissions and invalid records are handled separately from temporary throttling.

Synchronise customer and service changes

Dataverse change tracking provides delta links for retrieving subsequent changes on eligible tables where it is enabled. Supported paging and saved continuation state allow larger datasets to be processed over multiple requests.

Current customer records can then be related to order fulfilment, contractual commitments and financial activity. Plan reconciliation so relationships can be checked after changes, deletions or an interrupted synchronisation.

Related integrations

Salesforce integrationSQL Server integration

Connect your systems
with Uplyst.

Talk with our team about the systems you use and the decisions they need to support.

Discuss an integration