Microsoft Dynamics 365 Integration

Overview

Many sales organizations accelerate deals and increase margins by adding Oracle CPQ to their Customer Relationship Management (CRM) system. This allows sales representatives to get quotes in front of their customers quickly and accurately without help from their support staff. Microsoft Dynamics 365 for Sales CRM customers can integrate Oracle CPQ to allow their users to create quotes from opportunities with a seamless single-sign on experience.

Beginning in Oracle CPQ 24A, the Microsoft Dynamics 365 CRM integration type is added to the Oracle CPQ Integration Center. This feature streamlines the set up and management of the connection(s) between Oracle CPQ and Microsoft Dynamics. This new interface allows administrators to directly configure the details of the Dynamics environment without the assistance of customer support. Refer to Microsoft Dynamics 365 CRM Integration for more information.

Setting up the integration is simplified by installable integration packages delivered and supported by Oracle. The data integration is extensible and configurable using the urldata Patch method for session tokens, BML integrations, and Azure Active Directory user integrations.

The Microsoft Dynamics 365 - Oracle CPQ integration enables users to punch into Oracle CPQ from the Opportunity to create new quotes and edit existing quotes. Quote data and line items are synced back to Dynamics using REST web services.

Microsoft Dynamics 365 has introduced a Unified UI. Beginning with Oracle CPQ 20C, we added integration support for Microsoft Dynamics Unified UI. In addition Oracle CPQ continues to support the Microsoft Dynamics Legacy Web Client.

Note: This document describes Oracle CPQ enhancements to support the Oracle CPQ - Microsoft Dynamics 365 Integration. For detailed implementation instructions, refer to Oracle CPQ Connector for Microsoft Dynamics 365 Installation and Setup Guide.

Sales User Experience for Creating, Updating, and Deleting Quotes from Dynamics 365

This section gives an overview of the sales user experience once the integration is set up. Certain details may vary in each customers’ environment based on their CRM implementation.

ClosedCreate a Quote

ClosedUpdate a Quote

ClosedDelete a Quote

Administration

ClosedMicrosoft Dynamics Solution to Connect Oracle CPQ

ClosedOracle CPQ Migration Package to Connect to Microsoft Dynamics

ClosedBML Integration Type for Commerce

Notes

When integrating Oracle CPQ with the Mircosoft Dynamics Unified UI, note the following:

  • Prior to integrating Oracle CPQ with latest Microsoft Dynamics Solution package (1.0 or later), the site Process ID, Document ID, and Action ID must be recorded. The values in these fields are not retained and must be re-entered.
  • In order for the Return to Opportunity and Return to Account actions to function with the Dynamics Unified UI, administrators must set the return URL app ID. The app ID can be retrieved from the site URL from the Sales hub.
  • If an end user performs a page refresh while creating a quote in the Unified UI, a "Record is Unavailable" error may display. Provided the end user has saved and synched the quote to Microsoft Dynamics, no data is lost. The quote is available under their respective opportunity.
New customers planning to integrate Oracle CPQ with Microsoft Dynamics 365 should request the provision of a Base Reference Application as their initial site image and open a Service Request (SR) on My Oracle Support to specify Dynamics 365 as their CRM provider. The BML type integration option is then available on the Select Integration Types page. When the integration type is enabled, administrators can create an unlimited number of BML integrations for Dynamics 365.
If Dynamics administrators miss populating a field on a Return to Opportunity action, clicking the Return to Opportunity action could navigate the user to an unexpected Dynamics page with a blank navigation ribbon as opposed to navigating the user to the correct Opportunity page. For these actions, administrators should set the "External Object Name Attribute" to a text attribute that defaults to the entity name ("opportunity").

Related Topics

Related Topics Link IconSee Also