MS Power Apps
Overview
The Smart CPQ managed solutions for MS Dynamics can easily be embedded in a Microsoft Power App. It allows benefiting from all the power of Smart CPQ with a limited CRM usage approach ruled by Power Apps licenses.
This solution is particularly interesting for organizations who do not have a CRM solution or have a CRM solution that does not have a supported integration between Smart CPQ and the CRM. Although Smart CPQ offers various APIs, a custom integration between Smart CPQ and another CRM solution can indeed be development intensive, initially and for ongoing maintenance. You can thus leverage a Smart CPQ solution running in a custom "host" solution on Microsoft's Power Platform, using a custom model-driven app built with Power Apps, in place of a full Dynamics 365 Sales app.
Key Considerations
Here are the points to be considered to assess whether this solution is viable for your organization:
- Your organization does not have a CRM or has non-CRM users who need to use Smart CPQ
- The solution is viable under the following conditions:
- Users work on a low-volume number of quotes a day. As Power Apps licensing is capacity usage based, users working on many quotes and complex approvals can consume the capacity. Potential usage should be evaluated against licensing capacity of Microsoft Power Apps.
- Users require basic approval workflows (same capacity constraints as above).
- Administrators in your organization can own (create, manage and maintain) a model-driven Power App
- The solution is not viable under the following conditions:
- Users work on a high-volume number of quotes a day and / or require complex approval workflows
- Administrators in your organization cannot own (create, manage and maintain) a model-driven Power App
SUPPORTED SOLUTIONS
The Conga offering includes three managed solutions for MS Dynamics:
- Smart CPQ
- Smart CPQ for Sales Agreements
- Subscriptions
Although all those solutions are supported in the Power App configuration, you must pay attention to the key considerations in the previous chapter. As the Power App approach is capacity-constrained, managing huge Agreements or complex Subscriptions for instance may lead you to quickly reach the limitations inherent to the Power App licenses.
All Conga solutions can be embedded in a Power App. Yet you are responsible to monitor the usage of the Power Apps so that you do not reach the limitations associated with Power Apps licenses.
Conga cannot be held responsible for the sizing of the solution for your organization.
LICENSING
- You must procure Microsoft licenses directly and/or through your enterprise agreement with Microsoft. The details given here are driven by Microsoft and are subject to change without Conga being accountable for them. Please refer to Microsoft documentation for more details.
- Power Apps licenses include capacity entitlements regarding API calls to Dataverse (e.g. CRUD type operations on tables in Dataverse), file storage, and data storage.
- Additional capacity packs can be purchased from Microsoft as and when needed.
- Capacity is pooled at the tenant level so that each user license contributes to the total capacity.
- Normal quoting workflows in Smart CPQ consume minimal capacity but other scenarios like mass price change operations and possibly complex, high volume product synchronizations from a Smart CPQ quote to the quote table in Dataverse.
All Conga solutions can be embedded in a Power App. Yet you are responsible to monitor the usage of the Power Apps so that you do not reach the limitations associated with Power Apps licenses.
Conga cannot be held responsible for the sizing of the solution for your organization.
- License Requirements for Microsoft Components (Details):
- At least one User License to Dynamics 365 Enterprise assigned to the user(s) that will create and maintain the custom Power App for Smart CPQ. See Capacity limits in Microsoft license details.
- Power Apps per User per App plan OR Power Apps per User plan.
- Additional, shared capacity available for heavy usage.
| Solution Requirement | Owner |
| Procure licenses from Microsoft | End Customer |
| Create custom Power App with Smart CPQ | Solution Integrator and/or Customer |
| Install and update the Smart CPQ managed package used in the Power App | Solution Integrator and/or Customer |
| Maintenance and management of the custom Power App | End Customer |
How to Create an MS Power App Embedding Smart CPQ Solutions
- Instead of a CRM, a custom Power App must be created to be the “host” of Smart CPQ.
- The custom Power App is created using the same basic entities in Dynamics 365 as in the Smart CPQ managed solution, such as Quote or Opportunity.
- The Power App utilizes the same Smart CPQ managed solution that is used in a standard implementation with Dynamics 365.
- The sales user experience of working with Smart CPQ in the custom Power App is the same as in Dynamics 365.
PRE-REQUISITES
You must have a full CRM license for the install and maintenance of the overall solution.
The Smart CPQ managed solutions you want to embed must be installed and configured prior to the creation of the Power App.
PROCEDURE
- Log in to make.powerapps.com and make sure you are in the environment.
- Click on Create in the left explorer and then click on Blank App.
- You must create a Model-Driven app and therefore click on Blank app based on Dataverse.
- Give your app a name and description and check the box to use components from a custom solution. Select Smart CPQ for Dynamics as the solution and use the Default site map.
- You then need to add a page and choose a Dataverse table as the content. Click on Next to select the tables you want to be part of the Power App.
The minimal requirements are: Quote, Quote Line, Opportunity, Opportunity Line and Account.
- Once done, you can customize the Power App as desired and click on Save and then Publish.
- Your Power App is now ready. Log in the CRM and click on the app switcher in the top bar. Your app must be visible.
- Once in the Power App, navigate and create quotes as if you were in the CRM default app.
