Power Platform

Dataverse Hierarchy Security - Manager & Position Clear steps, rules and a Position-hierarchy example-styled with Dataverse theme green. Manager Hierarchy - Setup & Notes When to use Use Manager Hierarchy when you want access to flow from a user to their manager(s) based on the Manager field in Azure AD / Entra ID. Important rule The subordinate must be in the same Business Unit or a child Business Unit of the manager. If not, you will see: This user is not a member of the manager's business organization. Quick checklist Table must be User or Team-owned . Record owner must be a User (not a Team). Manager must be assigned in Azure AD (Manager property). Step-by-step (Manager Hierarchy) Go to Settings > User Permissions > Hierarchy Security . Enable Manag...

1. Dataverse Table Ownership (Organization vs User/Team) Organization-Owned Table: Records do NOT have individual owners. Only None or Organization permission levels are allowed. Used for: Configuration tables, global reference data. User/Team-Owned Table: Records are owned by users OR teams. Allows scopes: None, User, Business Unit, Parent:Child BU, Organization . Used for: Operational data (Projects, Cases, Accounts). 2. Business Unit vs Team (They Are Not Same) Business Unit: Defines security boundary and data visibility. Every user belongs to exactly one BU. Cannot own records. Team: A group inside a Business Unit. Can own records (Owner Team). You can add/remove members. Roles assigned to Teams apply only to Team members. 3. Default Business Unit Team (Auto-created Team...

Dataverse Table Ownership & Security Permissions Clear explanation of ownership types and permission scopes (organization vs user/team) Overview In Microsoft Dataverse every table has exactly one ownership type . Ownership determines whether row-level security can be applied and which permission scopes are available in security roles. 1. Organization‑Owned Tables Records are owned by the organization , not by users or teams. Row-level scopes (User / BU / Parent:Child BU) are not available. Available permission scopes in security roles: None  - no user can perform the action Organization  - every user with the privilege can act on all records Typical use: global configuration, metadata, reference lists or settings where everyone can read or manage at org-level. 2. User or Team‑Owned Tables Each record has a...

D Dataverse Lookup Permission Matrix Many-to-One lookup: Child → Parent (example: Employee → Department) Quick summary To edit a lookup you must have matching Append / Append To plus appropriate Read/Write levels on the involved tables. Missing any required permission typically shows a 🔒 lock on the lookup. Parent Table -  Department (records you select) Permission Required Level Why Needed If Missing Read Organization Allows user to view/select parent records Lookup dropdown is blank Append To Organization Allows child record to attach to parent If it is not there while saving record it will show error like below Insufficient Permissions Calleruser(Id = 12) is missing prvAppendTosun_RelatedTable pri...

Model-Driven App Components Component Type / Variant Use / Purpose Limitations / Notes Form Main Form Display and edit single record details; most commonly used Complex forms can impact performance; may require role-based access control Form Quick Create Form Fast creation of a record with essential fields only Limited fields; cannot include all form components Form Quick View Form Embedded read-only display of related table record inside another form Cannot edit fields; limited formatting options Form Card Form Compact view for timelines, dashboards, subgrids Limited fields and layout options; mainly for mobile or card display View System View Default view provided by Dataverse; shows list of records Cannot be deleted; can be customized ...

Dataverse Column Types Column Type Description / Use Example Limitations / Notes Single Line of Text Stores text up to 4000 characters Employee Name: "John Doe" Max 4000 chars; no formatting (rich text limited to 100k if enabled) Multiple Lines of Text Longer text, supports multiple lines Description, Notes Max 1,048,576 characters; can enable rich text formatting Choice (Option Set) Predefined dropdown list of values Status: Active / Inactive Only allows values defined in option set; cannot add free text MultiSelect Choice Multiple options from predefined set Skills: Java, C#, Python Max 150 selections; cannot be indexed for filtering efficiently Whole Number Integer values Age: 25 Range depends on format; cannot store decimals ...

Step 1: Go to your solution and create a Canvas App page . Refer to the image below for guidance. Step 2: The Canvas App page will open in Power Apps Studio. In the OnStart property of the app, add the following code: Set ( a , Param ( "recordId" )) ;       // Returns the record ID Set ( b , Param ( "entityName" )) ; Next, insert a Label control and set its Text property to: "a: " & a & "" & Char ( 10 ) & " b: " & b & "" & Char ( 10 ) This will display the values of the parameters passed from the model-driven app. Finally, give your custom page a name and publish it. Step 3: Add the custom page to your Model-Driven App by editing the app in the App Designer. Refer to the image below for detailed steps. Then, select the custom page you added and uncheck the "Show in navigation" option. This ensures the page doesn't appear in the app’s left-hand navigation but can still be open...

Every organization must protect its data while ensuring that the right people have access when they need it. Microsoft Power Platform offers a feature called hierarchy security , which makes controlling access easier and more precise, even in complex environments. In this guide, we'll walk you through the basics in plain language. What Is Hierarchy Security? Hierarchy security is an extension of existing security models in Power Platform (like business units, security roles, sharing, and teams). It helps you define who can see what data by building a logical structure based on a company's management or job roles. Essentially, it lets you assign access rights using a "chain of command" or a "position" setup. This method is not only more granular (or detailed) but also reduces the effort required to manage many business units manually. The Two Key Models There are two common ways to organize hierarchy security: 1. Manager Hierarchy The manager hierarchy is ba...