Forum Discussion
Power Apps Usage Rights with a Dyanmics 365 Enterprise License for non-restricted Dynamics tables
LicensingConcierge1 - Appologies I think i now understand your reply.
In summary, if a user possesses only a Customer Service Enterprise license and wishes to perform Create, Read, Update, Delete (CRUD) operations on the Order table (which is included in the Sales license but remains a non-restricted table) within their own environment, they will require ONE of the following additional licenses, depending on what suits their needs best:
- Power Apps Per App (to gain CRUD operations to non-restricted Dynamics tables within a custom Power App).
- Power Apps Premium (to gain CRUD operations to non-restricted Dynamics tables within a custom Power App).
- Dynamics Sales Attach (to gain CRUD operations to non-restricted AND restricted tables within the Sales license usage rights).
This requirement also holds true if the customer user has a Sales base license and intends to perform CRUD operations on non-restricted tables included in the Customer Service license.
The rationale behind this lies in the fact that the Dynamics license (be it Customer Service or Sales) exclusively covers usage rights for its own tables as outlined in the Dynamics 365 Licensing Guide. Additionally, the limited Power Apps usage rights included with that license constrain the utilization of Power Apps capabilities within the context of the licensed Dynamics 365 application, i.e., only for the tables included in the license.
Microsoft
I can confirm that order entity is included with the D365 Sales license. As mentioned in my previous post, Order entity (Sales Order) is included with the Sales license and not the Customer Service license.
I cannot confirm that order entity is included in the Customer Service license because the D365 LG & documentation does not state such.
If you require additional clarification and configuration assistance, you can continue this discussion on the Power Apps community that I've started on your behalf here.
Regards,
Microsoft CSP Licensing Concierge
LicensingConcierge1 My appologies I missed that link when I last viewed the thread. But its good to get final confirmation of my original question from an MVP of my original question. So the answer to my original question is Yes.
You can perform CRUD operations on the Order entity with a Customer Service Enterprise Licence because its a non-restricted table as long as it is within a custom Power App.
However its also useful to know you should not be using any of the the Sales apps requiring a license such as the Sales Hub to access the tables. This would require a Sales license.Please can you suggest to Microsoft to make this topic clearer in both licensing guides. The Dyanmics and Power Platform guides it would be very useful. But thank you so much for all your help.
For clarity here is the other thread with the answer here- LicensingConcierge1
As mentioned, I feel that your question can be better answered on the Power Apps community:
Regards,
Microsoft CSP Licensing Concierge
Thank you for your response, Microsoft. I appreciate your effort to address my query, but the information provided appears to be somewhat vague and does not directly address my specific question. It would be greatly beneficial if you could confirm the accuracy of my statement regarding valid licensing options to resolve the issue.
In my previous communication, I mentioned that CRUD (Create, Read, Update, Delete) access is not inherently included in the Customer Service Enterprise license for the order entity, as it is covered under the Sales license. Given that our organization has Sales users who work with the order entity in their Dataverse, it seems necessary to clarify whether an additional license, in addition to the Customer Service license, is indeed required to address this concern.
I kindly request your confirmation regarding the validity of this approach. It would be highly advisable to include such clarifications in your licensing guides to ensure complete transparency and eliminate any potential confusion.
