Microsoft Dataverse
Microsoft Dataverse is the data platform underlying Dynamics 365 Sales, Customer Service, Field Service, and custom model-driven apps. Askel connects to each customer's Dataverse environment once and reads or writes rows across standard and custom tables.
What you can do
Read and write standard Dataverse tables
Access accounts, contacts, opportunities, cases, and any other standard table that the customer's Dynamics 365 apps populate, using the OData v4 REST API.
Work with custom tables and columns
Dataverse environments often have dozens of custom tables with publisher prefixes like cr7f3_. Askel reads the metadata API to discover them and includes them in the mapping editor.
Upsert records by alternate key
Use OData upsert semantics with a customer-defined alternate key to create or update records without first querying for existing IDs.
Traverse relationships
Follow lookup columns and many-to-many relationships in a single OData query using $expand, reducing the number of round trips needed to build a complete record.
Run server-side filters
Push OData $filter expressions to Dataverse so only matching rows are transferred. Useful for large tables where pulling all records is not practical.
Audit every API operation
Askel logs every OData request with the table name, HTTP method, filter expression, and response row count so your team can inspect any data movement.
Syncing new Dynamics 365 accounts into your onboarding platform
You sell an employee-training platform. Apex Systems runs Dynamics 365 Sales and wants every newly converted account to trigger an onboarding workspace in your product. The account record holds the contract tier and the primary contact's details.
- 1
Connect via Azure AD
Apex's IT admin clicks Connect Dataverse in your product. The Microsoft consent screen lists the Dynamics CRM user_impersonation scope; the admin approves. Askel stores the refresh token.
- 2
Discover tables
Askel queries the Dataverse metadata endpoint for Apex's environment. Standard tables like account and contact appear alongside custom tables like cr7f3_contracttier. A mapping draft is ready in minutes.
- 3
Map the fields
Your CS rep maps account name, primary contact email, and the custom cr7f3_contracttier column to your product's workspace fields. Askel validates the column types match.
- 4
Set up the trigger
Askel polls for accounts where statuscode equals 1 (Active) and createdon is newer than the last successful run, so only net-new accounts are processed.
- 5
Go live
Activate the workflow. Each new Active account in Apex's Dynamics 365 environment creates a workspace in your product within the next scheduled polling interval.
OAuth 2.0
The customer's Azure AD tenant admin or a delegated user clicks Connect and approves the Dynamics CRM user_impersonation scope on Microsoft's consent screen. Askel stores the refresh token and handles silent token renewal. For service-to-service scenarios, an Azure AD app registration with application permissions can be used instead; contact your Askel account team to configure that variant.
How Askel sits between your product and the customer's system
Related integrations
FAQ for Microsoft Dataverse
Does this work with all Dynamics 365 apps?+
What is the difference between this and the Dynamics 365 F&O integration?+
Do we need special Azure AD permissions?+
What happens if the customer adds a new custom column?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.