Dataverse Lookup Permission Matrix

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 privilege on RelatedTable entity(OTC=1). Consider adding missing privilege to one of the Calleruser roles for the request to succeed
Child Table - Employee (lookup column lives here)
Permission Required Level Why Needed If Missing
Read Business Unit or Organization Allows form to load and show current value Form errors or missing data
Write Business Unit or Organization Allows changing the lookup value Lookup shows 🔒 lock; cannot edit
Append Organization Allows child to attach itself to parent record Lookup shows 🔒 lock
Quick Checklist to Remove the Lock
  • Parent: Read = Organization, Append To = Organization.
  • Child: Read = BU/Org, Write = BU/Org, Append = Organization.
  • If the lookup column has column-level security enabled, ensure the user is in a proper Column Security Profile.
  • If you use Azure AD security groups, ensure the security role is assigned to the group (not just the app shared).
  • Confirm whether the record is team-owned (team membership can allow access).
Note: If everything above looks correct but the lock remains, re-check the user's effective roles (direct + via teams + via Azure AD group) and column security profiles.

Comments

Post a Comment

Popular posts from this blog

Part 1: Creating Code Apps in Power Apps - A step-by-step guide (with real errors I faced & how I fixed them)

Image
Intro In this post I’ll walk you through how I set up a code-based app for Power Apps (React/Vite front-end + Power Platform CLI for packaging/deployment), the exact errors I ran into, and how I solved them. If you want a hands-on, copy-paste able guide that covers Node versions, pac auth, environment issues, and packaging tips, this is for you. Prerequisites Microsoft 365 account with access to a Power Platform environment Node.js ( 20.19+  recommended LTS) VS Code Install power platform tools extension in VS Code. Steps: Step 1 : Open Visual Studio Code and launch the integrated terminal. Step 2: In the terminal, run the following commands one by one.   mkdir D:\CodeApps - Force cd D:\CodeApps npm create vite @latest myfirstapp -- -- template react - ts cd D:\CodeApps\myfirstapp npm install Initially, I ran the command: npm create vite@latest MyFirstApp -- --template react-ts This gave the error: Invalid package.json name The issue was caused because package...
Read more

Calling Microsoft Graph API from Power Automate Using Azure App Services – Step-by-Step Guide

Image
Step 1: You should have an Azure subscription, or if you have access to the Microsoft Entra Admin Center, you can create an app from there. This app can then be used in Power Automate to connect to Microsoft Graph API. Step 2: Click on "New registration" , provide a name for your app, assign the required API permissions (such as Microsoft Graph permissions), and then click "Register" to complete the app registration process. Step 3: After registration, you'll be redirected to the app's overview page. From there, navigate to the API permissions tab and click "Add a permission" to assign the necessary Microsoft Graph API permissions. Step 4: Select Microsoft Graph as the API, and based on your requirements, choose the appropriate permissions. In my case, I selected Application permissions , which do not require user sign-in and are suitable for background services or automation. Step 5: Select the required Microsoft Graph API permissions. Yo...
Read more

Step-by-Step Guide: Power Automate Custom Connector Using Graph API from Azure App Service

Image
Step 1: Open Power Automate, navigate to the Custom Connectors tab, and select Create from blank as shown in the image below. custom connector(click image for better resolution) Step 2: In the General tab, upload an icon (less than 1MB), add a description, select the correct scheme (in my case, HTTPS ), and provide the host name. For example, if your API URL is https://graph.microsoft.com/v1.0/users/{email} , the host name will be the highlighted part — graph.microsoft.com . Step 3: Go to the Security tab. Here, you need to select the authentication method. Choose OAuth 2.0 as the authentication type, as shown in the image below. Step 4: Select the Identity Provider as Azure Active Directory . Check the box Enable Service Principal Support . This option allows you to create a connection using a Client ID and Client Secret instead of using the user's own authentication. Next, provide the Client ID , Client Secret , Tenant ID , and other required details as shown in t...
Read more