Answered

Using Sales entities in a custom application - licensing

(0) Share

Report

Posted on by OuiChef

Hi,

I'm creating a dataverse application that will reside in my Client's tenant. The application will make use of some Power Automate flows. The aim is to sell this application to multiple clients.

The Client will have internal access to the Application, possibly via a Model Driven App, but it may be via Power Pages.

Third Parties will have external access to the application, and they will login via Power Pages to perform certain functions in my application, similar to the internal users.

I plan for my application to use the out of the box Lead, Opportunity, Quote, Product Catalog (and related) entities, with some customisations made. to each of the entities (linking to new entities, new columns etc.).

Can someone please advise if my Client will require the full Dynamics licensing to use these entities in my application, or are there alternative licences I could use? I read somewhere about a "Team Member" licence, but I don't know if that is suitable in my scenario.

Thanks

Categories:

Governance & administering

I have the same question (0)

All responses (3)

Answers (2)

Verified answer

eraseu2 15 on at

Like (1)

Report
Copy link

Link copied!
The Team Member license could work in this situation, however there are some limitations. Users with that license can only use the Sales Team Member (msdyn_TeamMember_Sales) app. You can fully customize that app, however you can only add 15 tables/entities to that app. Tables that are accessed indirectly within your app through lookups also don't count as long as users have read only access.

Some tables don't count against that limitation but I have yet to find any documentation that lists them. We've also tried to get this information directly from our MS rep and could not get an answer. Through trial and error I identified the tables below that don't count against the 15 table limit (I suspect there are many more).
Activity
Account
Contact
Lead
Opportunity
If you exceed the limit you'll see this error when you publish the app.

Having made this transition at my company, I would probably not go this route in your situation. Since you want your app to work for multiple customers, you would effectively need to build the app around the lowest common denominator, the Team Member license. Additionally, if your app causes users to violate the Team Member license I suspect it would be an issue for your customers, as it would flag the violation on their environment/tenant.

Just my two cents, good luck.

Was this reply helpful? Yes No
Verified answer

velegandla 204 Moderator on at

Like (1)

Report
Copy link

Link copied!

@OuiChef

Here is the guidance from license doc.

You need additional licenses if you are using restricted tables.
Restricted tables requiring Dynamics 365 licenses - Power Apps | Microsoft Learn

====================================================

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

https://www.linkedin.com/in/devendravelegandla/

Was this reply helpful? Yes No
OuiChef 14 on at

Like (0)

Report
Copy link

Link copied!

Hi, thanks to the both of you for your replies.

Half-using stuff from the Sales app complicates things too much for what I want to achieve, so I've decided to create my own custom version of the entities I need as I won't really be utilising any of the out of the box functionality that comes with Lead or Opportunity. It won't be too much extra work to create the entities I need. It's just for some basic data capture and the rest will all be custom functionality.

Was this reply helpful? Yes No