Licensing - What are Dataverse Restricted tables?
When we build Power Apps to extend Dynamics 365, it's important to be aware of 'restricted tables'. These are tables that are fully accessible with a Dynamics 365 license only. This post provides an introduction to this topic.
Why do restricted tables exist?
To answer this question, let's examine the licensing cost of Dynamics 365 Sales.
Let's compare this to the cost of the Power Apps per user and per app plans. A Power Apps per user licence (which provides access to Dataverse and unlimited custom apps) is $40/month. The per app licence (which provides access to Dataverse and up to 2 custom apps) is $10/month.
For certain use case scenarios, an organisation may choose to build custom Power Apps that integrate with the same tables that Dynamics 365 uses and in doing so, benefit from lower licensing costs.
To limit the scope of this practice and to help Microsoft protect their licensing revenues, certain Dataverse tables are restricted. With restricted tables, users with a Power Apps plan can read records from the table, but not create, update, or to delete records.
What tables are restricted?
The documentation site beneath provides the best up-to-date information on what tables are restricted.
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/data-platform-restricted-entitiesAt the time of writing, the restricted tables include the following:
Actual, Agreement Business Process, Booking journal, Booking Setup Metadata, Booking timestamp, Case, Case to Work Order Business Process, Configuration, Entitlement, Estimate Line, Estimate, Fact, Field service setting, Field Service System Job, Goal, Inventory Journal, Invoice Process, Journey, Knowledge article, Organizational Unit, Product Inventory, Project Parameter, Project Stages, Project Task Dependency, Project Task, Project Team Member, Purchase Order Business Process, Resource Assignment Detail (Deprecated), Resource Assignment, Resource Restriction (Deprecated), Routing rule set, Schedule Board Setting, Scheduling Parameter, SLA, System User Scheduler Setting, Transaction Connection, Transaction Origin, Transaction Type, Unique Number, Work Order, Work Order Details Generation Queue
Where can I find out more about Dynamics 365 licensing?
The PDF licensing guide provides the most comprehensive and accurate information on Dynamics 365 licensing. The official Microsoft Dynamics 365 website tends to be more marketing focused, with less detail on the precise details of licensing.
The link beneath should always return the latest version.
One thing to note is that for use-case scenarios where users require limited, mainly read-only access to Dynamics 365 data, the team license and Team apps can provide a cost-effective solution, at around $8/user/month. There are more details here:
- Dataverse - How to create Entity Relationship diagrams
- Dataverse - How you can more quickly bulk update data using the SQL language
- Dataverse - How to fix the bug in the 'Business Rules' editor that prevents numeric values from saving
- Dataverse - What are the benefits, and how to create formula columns
- Dataverse - How to sort the available choice items from a choice column
- Error - Unable to modify Dataverse tables with error message, Language id should not be null
- Dataverse - How to retrieve FetchXML or SQL for Dataverse views
- Data - Why is Dataverse so fast?
- Dataverse - How to create and use Dataverse views in Canvas Apps
- Dataverse - How to filter Dataverse choice columns
- Dataverse - How to switch to the classic designer when the option is not available
- Media - How to save and work with microphone recordings
- Dataverse - how to access tables from another environment
- Dataverse - How to Patch the 5 most complex data types