Connect your customers' Dynamics 365 Finance and Operations environments so your product can read and write OData entities across their legal entities. The customer's admin consents on Microsoft's screen; Askel stores the environment base URL, the aadTenantId, and the dataAreaId for each legal entity.
Fetch Customer entity records including account number, name, customer group, currency, and payment terms from the customer's D365 F&O environment.
POST SalesOrderHeader and SalesOrderLine entities to create sales orders in the target legal entity, or read open orders filtered by customer account, status, or date range.
Fetch vendor master records and purchase order headers and lines. Useful for procurement-visibility workflows that need to surface open POs or receipt status from F&O.
Read the chart of accounts and posted general ledger transactions for financial reporting or reconciliation workflows that need actual ledger data from F&O.
Fetch released product records with item numbers, descriptions, unit of measure, and storage dimension assignments so your product can map SKUs without a separate data export.
Read Worker entity records with employment status, department, and position for HR-integrated onboarding workflows that need to cross-reference employees between your product and F&O.
You sell a configure-price-quote (CPQ) platform. A new customer, Vantage Industrial Solutions, uses D365 Finance and Operations for order management and fulfilment. When a quote is accepted in your CPQ tool, Vantage wants a confirmed sales order to appear in their F&O environment automatically, scoped to the correct legal entity (VIS-UK).
Vantage's IT admin clicks Connect Dynamics 365 F&O in your product. Askel redirects to Microsoft's consent screen. After approval, the admin provides their environment base URL (vantage.operations.dynamics.com) and the legal entity code VIS-UK. Askel stores all three values.
Askel reads the released products from the F&O environment scoped to the VIS-UK legal entity. Your CPQ tool's admin maps each CPQ product code to the matching F&O item number. Unmatched products are flagged for manual resolution.
When a quote is accepted for a named buyer, Askel checks whether a matching customer account exists in F&O by querying the Customers entity with the buyer's name or external reference. If no match is found, Askel creates a new customer account.
Askel POSTs a SalesOrderHeader and SalesOrderLine set to the F&O OData endpoint, with dataAreaId=VIS-UK on the request. The order header includes the customer account, requested ship date, and delivery address from the CPQ quote.
F&O returns the new order number. Your CPQ tool stores it on the quote record and displays it to Vantage's sales rep as confirmation. Vantage's order management team sees the order in F&O immediately and begins the fulfilment process.
The customer's Microsoft admin consents on the standard Microsoft identity platform screen. Askel stores the refresh token, the aadTenantId (read from the token claims), the environment base URL, and the dataAreaId (legal entity code) provided by the customer. Every OData request is sent to the environment base URL with the dataAreaId in the request body or query where required. Access tokens are minted per request and expire after one hour.
© 2025 Askel.ai. All rights reserved.