Model-Driven App Components

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
View Personal View User-created view; visible only to creator unless shared Not visible to everyone by default; must be shared
View Associated View Shows related records in subgrid on another entity form Limited filtering and customization options
View Quick Find View Used by search box to find records quickly; defines searchable fields Cannot be used for all advanced filtering; only for search functionality
Dashboard Interactive / Classic Dashboard Displays charts, lists, and key data in one place for insights Interactive dashboards are limited to certain entities; layout customization is limited
Chart Bar / Pie / Line / Funnel Visual representation of data for analytics Dependent on views; complex charts may require Power BI for advanced analytics
Business Process Flow Linear / Stage-based Flow Guides users through processes with stages and steps Cannot be highly customized beyond defined stages; limited branching support
Business Rule Client-side / Server-side Enforces logic like showing/hiding fields or setting values without code Limited to simple logic; complex scenarios require JavaScript or plugin
Relationship 1:N, N:1, N:N Connects tables; used in lookups and subgrids Complex N:N may require junction tables; performance impact if large volume
Key Primary / Alternate Key Ensures uniqueness of records Alternate keys have limit on number and size; must be planned carefully
Column / Field Text, Number, Choice, Lookup, etc. Holds actual data in a table Must choose type carefully; changing type later can be complex; size limits apply
Command / Ribbon Custom Button / Action Adds custom actions to forms, grids, or subgrids Requires JavaScript or action configuration; limited layout control
Plugin Server-side / Real-time Custom code executed on create/update/delete events Requires development skills; affects system performance if heavy

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