AB-410 Cheat Sheet
Create a foundation for intelligent applications
Design Power Platform solutions with AI-enabled tools
Read full chapterCheat sheet
Sharp facts the exam loves — scan these before test day.
- Plans turns a business description into a proposed multi-component solution
When requirements span data, applications, and automation, use plans in Power Apps to develop a coordinated solution proposal. Supply the business use case in natural language and optionally add process diagrams, data models, or legacy-app screenshots to give Copilot context.
Trap Using the table-creation Copilot alone as the complete solution planner, although its output focuses on tables and relationships.
3 questions test this
- You're creating a plan in Power Apps to replace a legacy Access application. You have screenshots of the legacy screens and a diagram of the approval process, and you want Copilot to use both of them
- A maker described a new equipment inspection process by using Start with Copilot when creating tables, and Copilot generated tables and relationships. The team now needs Copilot to propose the apps an
- Contoso's facilities team describes a new process in a short paragraph. The solution must include Dataverse tables, an app for technicians, an approval flow, and possibly an agent, and the team wants
- Review user roles and needs before accepting the generated data model
Plans progresses from user requirements to the data model and then the technology proposal. Edit generated roles and needs inline or through Copilot before selecting Looks good, so later recommendations reflect the intended users and their work.
3 questions test this
- A plan in Power Apps generated employee and manager roles for a PTO solution. You need to add an HR admin role that monitors PTO across teams before the data model is generated, and you want Copilot t
- A plan in Power Apps has generated user roles and needs for a PTO solution. You reviewed them with the business owner, and they're correct and complete. You now want the Data Agent to suggest the tabl
- A plan in Power Apps generated user roles and needs for a facilities solution. Before the data model is generated, you must delete one generated need and add a Security Officer role, and you want to t
- Technology proposal details identify the requirements and tables each component serves
A proposed technology's information card identifies the user roles it supports and the data tables it uses. Review that mapping when deciding whether to accept the proposal or request changes, rather than evaluating the component name alone.
3 questions test this
- A plan in Power Apps proposes a model-driven app, a canvas app, and a cloud flow. Before accepting the proposal, a reviewer must confirm which user roles each proposed component supports and which dat
- Before accepting a plan's technology proposal, you hover over the information icon on each proposed technology. The info cards show that every user role is supported by at least one technology and tha
- A plan's technology proposal includes a canvas app named Field Visits. Its info card shows that the app supports only the Dispatcher role and uses only the Visit table, but technicians must also use i
- Save the plan and tables before creating the proposed solution objects
Save tables establishes the plan in a solution and asks for a solution and publisher, or an existing solution. After this step, create the proposed apps, flows, sites, or agents in their respective authoring experiences; a proposal is not already a published application.
Trap Treating acceptance of the technology proposal as deployment, although object creation and publication still remain.
3 questions test this
- A maker accepts a plan's technology proposal by selecting Looks good and tells business users that the new expense app is ready. Users can't find the app anywhere in Power Apps, and the plan hasn't be
- You're about to create the apps and flows that a plan in Power Apps proposes. Your team's ALM policy requires every object from the plan to be stored in an existing unmanaged solution named Ops, which
- You've accepted the technology proposal in a plan in Power Apps. You now want to create the proposed canvas app and cloud flow, and the plan and its tables must be stored in a new solution that uses y
- Plans can replace a proposed app with an existing app
When an existing app already meets the need, use Replace on the proposed app tile rather than create a duplicate. Add technology includes an additional existing app, but existing apps added to a plan are not automatically included in its new solution.
Trap Assuming an existing app attached to a plan is automatically packaged in the new solution, although its solution membership remains separate.
3 questions test this
- A plan proposes a canvas app and a cloud flow for an inventory solution. You also want to show an existing reporting app in the plan. That app isn't related to any of the proposed scenarios, and none
- You used Replace to swap a proposed canvas app for an existing app named App1 in a plan, and you saved the plan in a new solution named Sol1. You'll later deploy Sol1 to production and expect App1 to
- A plan for an HR onboarding solution proposes a new model-driven app for HR coordinators. Your team already has a published app named Onboard that meets every coordinator need, and maintaining two app
- Plans requires Dataverse and an eligible environment
Plans requires an environment with a Dataverse database and an eligible locale. If the current environment is unsuitable, eligible makers can be redirected to a developer environment; otherwise they must switch to an environment where they can create tables.
2 questions test this
- Your team will build business solutions with plans in Power Apps, and the plans will save new Dataverse tables. You're choosing which existing environment the makers should use so that the plans prere
- A maker opens Power Apps in an environment that has no Dataverse database and selects Create a plan. The maker is allowed to use developer environments in the tenant, and the plan must include several
- Plan copresence does not permit simultaneous editing
Plans can show multiple collaborators, but only one author can edit at a time. Later arrivals have read-only access until the editor leaves or becomes inactive, so shared edit permission does not imply concurrent coauthoring.
Trap Choosing copresence for simultaneous edits by several makers, although it provides only one active editing session.
3 questions test this
- Two makers who both have edit permission open the same plan in Power Apps a few minutes apart. The second maker sees the first maker's avatar in the command bar but can't change any part of the plan's
- You joined a plan in Power Apps while a colleague was editing it, so you have read-only access. You need to make several changes to the plan's user needs today, and you don't want to create a separate
- You'll run a workshop in which three makers, who are all Co-Owners of a plan in Power Apps, contribute changes to the plan's user requirements and data model. You want the session to run without anyon
- App-type selection depends on whether the experience or the data model leads the design
When a task needs a highly tailored interface and connections to multiple data sources, choose a canvas app. When the solution centers on Dataverse business data and related processes, choose a model-driven app whose forms and views generate a responsive interface from that model. The choice is about the dominant design requirement, not simply whether the app runs on a phone.
Trap Choosing a canvas app solely for mobile use, although model-driven interfaces also respond to device size.
3 questions test this
- Contoso's onboarding team needs an app over several related Dataverse tables, with standard forms, views, dashboards, and a business process flow. Users move between related records all day, and no on
- A team wants a simple app for logging equipment loans. The team's environment has no Dataverse database, and all of the data must stay in an existing SharePoint list. A maker proposes building a model
- Inspectors use phones and tablets in the field to work with inspection records stored in related Dataverse tables, guided by a business process flow. A colleague insists on a canvas app only because t
- Power Pages serves external website audiences using Dataverse
When customers or partners need an external-facing website connected to Dataverse, select Power Pages. It supports sign-in through a variety of identities and anonymous content browsing, allowing the solution to serve an external audience rather than requiring an internal application experience.
2 questions test this
- A museum wants a Dataverse-backed website where anyone can browse exhibition schedules without an account. Members must sign in with an external identity, such as a Google account, to see member-only
- Contoso's distributors don't work for Contoso and have no Microsoft Entra accounts in its tenant. They must sign in with their own Google or LinkedIn accounts to view and submit warranty claims that a
- An agent can provide conversation while a flow performs the repeatable process
When users need to express requests conversationally, use an agent as the interaction component; use an app interface when they need direct interaction with screens and data controls. A rule-based workflow remains appropriate for a prescribed sequence of actions. An agent can call an agent flow, so adding conversation does not require replacing the deterministic process with generative decisions.
Trap Replacing a fixed processing sequence with generative decision-making solely because requests arrive through chat.
4 questions test this
- An agent flow in Copilot Studio runs a fixed approval sequence for travel requests. Requests will now arrive through a chat agent, and a colleague proposes replacing the flow with the agent's own gene
- Claims processors must triage and update about 200 claim records each morning by using sortable grids, filters, and editable form fields. A colleague suggests a Copilot Studio agent as their only inte
- Facilities staff want to report building issues by chatting with an assistant in Microsoft Teams, which asks clarifying questions. Each issue must then follow a fixed sequence: create a work order, as
- Every night at 2:00 AM, a fixed sequence must copy approved timesheets into a payroll table and then email a summary to the finance team. No user interacts with the process at any point, and it must p
- Dataflows provide repeatable transformation and loading into Dataverse
When data must be cleaned, transformed, and loaded into Dataverse repeatedly, choose a Power Apps dataflow. Define the preparation steps in Power Query and configure automatic scheduled refresh to rerun them. This loads prepared data into the destination rather than merely previewing an imported file or reading external rows dynamically at runtime.
Trap Choosing a virtual table for a requirement to persist regularly transformed copies in Dataverse, although virtual tables expose external rows at runtime.
3 questions test this
- A maker's dataflow in Power Apps pulls student records from three CSV exports into Dataverse. On every scheduled run, full names must be split into first and last names, rows with a repeated student I
- You're creating a dataflow in Power Apps that prepares vendor data for a model-driven app. The loaded tables must be stored in Dataverse so that the app can use them, not in your organization's Azure
- Every night, Contoso's warehouse system updates a SQL Server database of stock levels. Before apps use the data, units must be converted and blank rows removed, and the prepared rows must be stored in
- The Requirements Agent translates the business problem into user needs
Use the Requirements Agent's output to establish who the solution serves and what each role needs to accomplish. It is the first planning stage; review its proposed roles and requirements before letting later agents design implementation components.
Trap Reaching for the Data Agent to define user needs, although its responsibility is the proposed data model.
5 questions test this
- You're using plans in Power Apps to design a solution for booking meeting rooms. Before any tables or apps are proposed, facilities managers must confirm which user roles the solution serves and what
- A plan in Power Apps for a visitor registration solution lists receptionists and hosts, but it omits security guards, who must sign visitors out at the end of each day. You need the later data model a
- In a new plan for a field service solution, stakeholders must first confirm what dispatchers and technicians need. After that, a data architect must adjust the proposed table relationships on a visual
- You select Generate after describing a business scenario in a new plan in Power Apps. Your manager wants to schedule reviewers for the plan's first output before any implementation design begins, and
- A plan in Power Apps has generated user roles and needs for a PTO solution, and the data model hasn't been generated yet. A stakeholder wants employees to also be able to view PTO blackout dates, and
- The Data Agent proposes tables, columns, and relationships
The Data Agent translates the accepted business needs into a proposed data model with tables, column types, and relationships. Its suggestions can be reviewed and edited in the data workspace before the plan proceeds to technology selection.
Trap Using the Solution Agent as the schema-design specialist, although its role is choosing the technologies that consume the data.
5 questions test this
- The Data Agent in your plan has suggested five tables for a training management solution. A data architect needs to see the tables as a diagram and edit their relationships directly, without describin
- In a new plan in Power Apps for a field inspection solution, you review the generated user roles and needs and select Looks good. A reviewer asks what the plan produces next, so the right person can c
- You are reviewing a plan in Power Apps for a vehicle booking solution. A stakeholder asks for the relationship between bookings and vehicles to be changed, and for a missing column to be added, before
- A data architect is reviewing a plan in Power Apps for a training solution. Before the plan proposes any apps, the architect wants to check the recommended tables, the data types of their columns, and
- In a new plan for a field service solution, stakeholders must first confirm what dispatchers and technicians need. After that, a data architect must adjust the proposed table relationships on a visual
- The Solution Agent recommends technologies for the accepted requirements and data
The Solution Agent evaluates the needs, processes, and data to propose apps, flows, and agents. Use it when deciding the combination of implementation components, then review whether each proposed component addresses the business problem.
Trap Using the Requirements Agent to select the final app and flow combination, although it establishes needs rather than the technology proposal.
5 questions test this
- Your plan's requirements say that managers need a report of spending trends that they can filter and drill into, and no one should have to design app screens for it. You want the plan's technology pro
- Your plan's requirements include a dial control that replaces a numeric column on a model-driven form. You're checking whether the Solution Agent's technology proposal can supply that control or wheth
- A plan in Power Apps proposes a canvas app, a model-driven app, and a Power Automate flow for a supplier onboarding solution. Reviewers decide that external suppliers need a Power Pages website instea
- Your plan in Power Apps already has accepted user requirements and an accepted data model for an expense solution. You now need a recommendation for which combination of apps, flows, and agents should
- A plan for a purchase request solution includes a requirement that each new request is routed automatically to the requester's manager for approval, with no one starting the process by hand. You're re
- Form fill assistance offers suggestions that require explicit acceptance
When users need help entering data while retaining control, evaluate built-in form fill assistance. It suggests values for empty fields from recent usage, smart-pasted text or images, or supplied files; suggestions are not saved unless the user explicitly accepts them.
Trap Choosing form fill assistance for unattended record enrichment, although its suggestions depend on user review and acceptance.
3 questions test this
- A logistics company receives several thousand shipment records from a partner integration into a Dataverse table overnight. Before dispatchers start work, an empty Handling notes column on each record
- A user opens a record in a model-driven app where form fill assistance shows suggested values in several empty fields. The user accepts none of the suggestions and tries to move to another record. You
- Users of a model-driven app receive partner details in plain-text emails. They want to copy an email's text and have AI propose values for the matching empty fields on the main form, reviewing each su
- Form fill assistance can be disabled for individual sensitive columns
The Allow form fill assistance column setting (preview) controls whether a supported column receives AI suggestions. Disable it for sensitive columns while retaining assistance elsewhere; using the feature also requires an enabled AI form fill assistance environment setting.
Trap Using a column security profile solely to suppress AI suggestions, although it governs data access rather than the assistance setting.
3 questions test this
- You're adding a new Applicant table to a Power Apps model-driven app. Users must get automatic AI suggestions for its text and date columns, but a column named Tax ID must never receive suggestions. T
- Your model-driven app uses form fill assistance. A column named Bank Account on the Supplier table holds sensitive data and must never receive AI-generated suggestions. Users must still see and edit t
- Your compliance team decides that no Power Apps model-driven app in an environment may show automatic AI field suggestions that are based on users' recent data entry, on any column, until a review is
- Copilot chat provides conversational data insights where that experience remains supported
Copilot chat for model-driven apps lets users ask natural-language questions about Dataverse data rather than receive form-entry suggestions. This experience depends on Dataverse search, and enabling search alone does not enable every Copilot feature. Evaluate its availability before selecting it: Microsoft documents this as a preview feature in Power Apps, with deprecation beginning January 2026 for environments not enabled for Dynamics 365 apps, and recommends Microsoft Copilot as the replacement there.
Trap Selecting form fill assistance for conversational questions about existing records, although its purpose is proposing field values.
4 questions test this
- Service managers use a model-driven app in an environment that's enabled for Dynamics 365 apps. They want to type questions such as how many high-priority cases were created last week and get answers
- In October 2026, you're designing a new model-driven app for an environment that isn't enabled for Dynamics 365 apps. Users must be able to ask natural-language questions about the app's data, and the
- Users of a model-driven app in an environment that's enabled for Dynamics 365 apps use Copilot chat. When they enter a slash (/) to pick a specific account record for a question, the record picker doe
- Copilot chat is turned on for every model-driven app in an environment that's enabled for Dynamics 365 apps. An app named HR Cases must not show the Copilot pane to its users, while the other apps in
- Copilot selection must account for the business context it can actually access
For questions about organizational information, evaluate the proposed Copilot experience's grounding sources and the user's permissions. Web-grounded chat alone does not establish access to internal business context; that context must be available through a supported organizational-data capability, agent, or explicitly supplied content. Organizational grounding remains scoped by user permissions.
Trap Selecting web-grounded assistance for internal-record questions without providing a supported source of organizational context.
3 questions test this
- Two employees ask an agent the same question about internal project documents, and the agent is grounded in organizational content. One employee receives details from a restricted document, but the ot
- Support staff use Microsoft Copilot Chat, which is grounded in web data only. They need answers that draw on hundreds of internal troubleshooting articles in SharePoint every day, without uploading or
- Employees use Microsoft Copilot Chat, which is grounded in web data only. An employee wants a summary of an internal pricing guideline document that's stored in OneDrive, and the answer must reflect t
- Custom connectors expose services that lack a suitable prebuilt connector
When the solution must call an API that has no suitable prebuilt connector, recommend a custom connector. It wraps API operations as reusable actions or triggers for Power Platform consumers; a connection is still needed to use the API, with authentication when required by the API.
Trap Selecting a Power Apps component framework control for connector actions when no custom user interface is needed.
3 questions test this
- You created a custom connector for an internal ordering API that is published on the internet and requires OAuth 2.0 authentication. A maker adds one of the connector's actions to a cloud flow and wan
- Your integration team built a custom connector in Azure Logic Apps for a partner's REST API by using an OpenAPI definition. Makers now need the same API operations in Power Automate cloud flows and ca
- A logistics partner's REST API can notify subscribers whenever a shipment's status changes. You need a cloud flow to start automatically when that notification occurs, without polling on a schedule. N
- Power Apps component framework extends the application's visual controls
Recommend a Power Apps component framework code component when standard controls cannot provide the required data interaction or visualization. Components can replace a numeric field with a dial or present a dataset as a calendar, and can be reused in supported canvas and model-driven experiences.
Trap Choosing a Dataverse plug-in to render a custom interactive control, although plug-ins execute server-side data-event logic.
3 questions test this
- A model-driven app shows a Pressure column on its main form as a plain numeric value. Field technicians need to view and change the value by using an interactive dial on the form, and no standard cont
- Your team needs one custom slider control that makers can reuse on screens in several canvas apps and on main forms in model-driven apps. No standard control provides the required interaction, and the
- A model-driven form has a subgrid of service locations. Dispatchers want the subgrid's records shown on an interactive map in the same form context. A colleague proposes a Dataverse plug-in that draws
- Dataverse plug-ins extend data operations when declarative options are insufficient
Recommend a Dataverse plug-in when a requirement needs custom handling of a Dataverse data event and available declarative options do not meet it. A plug-in can augment or cancel the data operation, but requires developer implementation and maintenance.
Trap Choosing a custom connector to intercept and cancel Dataverse operations, although a connector exposes callable API operations rather than an event-pipeline handler.
3 questions test this
- Users delete Contract rows from model-driven apps, canvas apps, and integrations that call the Dataverse Web API. A delete must be stopped with an error message whenever the contract still has unpaid
- When a user saves a Contract row, Dataverse must evaluate pricing rules that are stored in several related tables and stop the save with an error message if the rules fail. Business rules and other de
- Order rows are created by a model-driven app, a canvas app, a cloud flow, and integrations that call the Dataverse Web API. A discount must be calculated and written to each row during the same save f
- Synchronous extensions delay the data operation while asynchronous extensions run afterward
A synchronous Dataverse plug-in makes the data operation wait for its work, so recommend it only when the operation must depend on the result. Asynchronous execution queues the extension after the operation finishes and is appropriate when the work can occur later.
Trap Selecting an asynchronous plug-in to prevent the original save, although that operation has already finished before the queued work executes.
3 questions test this
- A developer registered an asynchronous plug-in that validates new Order rows and is meant to stop invalid orders from being saved. Rows are created from apps and Web API integrations. Testers report t
- A Dataverse plug-in checks a customer's credit limit when an order row is created. If the check fails, the order must not be saved, and the user must see the error immediately in the app that submitte
- After an order row is saved, a Dataverse plug-in sends the order to an ERP system, which can take several seconds. Users must not wait for the ERP call to finish, and saving the order must not depend
- Private API integration can require an on-premises data gateway
For an API visible only within a private network, evaluate an on-premises data gateway alongside the custom connector. The connector describes the operations, while the gateway supplies the connectivity path to the private service.
Trap Treating a custom connector definition as a network tunnel, although describing an API does not provide private-network connectivity.
3 questions test this
- Contoso's inventory API runs on a server in the corporate datacenter and isn't reachable from the internet. Makers need to call it from several cloud flows through a custom connector that's already de
- A vendor's API is published on the internet over HTTPS and uses API key authentication. You're creating a custom connector so that cloud flows can call it. A colleague insists that you also install an
- A hospital's bed-tracking service exposes a REST API on a server inside the hospital network, with no public endpoint. An architect's diagram shows cloud flows calling the service through a custom con
- Azure Functions can host custom APIs exposed through a connector
When a solution needs custom server-side processing outside Dataverse, Azure Functions is an option for hosting the API. A custom connector can expose that API to Power Apps, Power Automate, or Copilot Studio, separating service implementation from low-code consumption.
Trap Treating the custom connector as the API's execution host, although it wraps a service implemented elsewhere.
3 questions test this
- Developers deployed an HTTP-triggered Azure function that calculates shipping rates. Makers in an environment without a Dataverse database must call it from canvas apps and cloud flows as one reusable
- Developers built an HTTP-triggered Azure function that scores loan applications with custom C# logic. Makers call it from canvas apps, cloud flows, and Copilot Studio agents through a custom connector
- Your team must run custom C# processing that calls several external services and isn't tied to any Dataverse data event. Makers must be able to call the processing from Power Apps, Power Automate, and
- Client scripting extends model-driven form interactions beyond available low-code capabilities
When a model-driven form interaction cannot be achieved with supported low-code form capabilities, recommend JavaScript client scripting through the supported client APIs. Scripts can respond to form events such as loading or column changes to control the client experience. This is a client-behavior extension, rather than a request for a replacement visual control or server-side handling of a Dataverse data operation.
Trap Choosing a Dataverse plug-in to react directly to a form-load interaction, although plug-ins handle server-side data events.
2 questions test this
- On a model-driven app's main form, a column named Resolution must become required whenever the Status column is set to Closed. Makers on the team who don't know JavaScript must be able to maintain and
- On a model-driven app's main form, when a user saves a Case row, client logic must call the client API to check related values and show a form notification in the browser before the user leaves the fo
- Production environments are intended for permanent operational workloads
Use a production environment for business workloads on which the organization depends. Keep development and testing separate so experiments and validation do not modify the operational application and data.
Trap Selecting the default environment as the standard production location, although it is intended for exploration and lightweight experimentation.
2 questions test this
- A critical expense app has run for a year in your tenant's default environment. Auditors note that the environment has no backup guarantees and that every licensed user is a maker there. You need a su
- Contoso is ready to release a model-driven app that the finance department will use every day to process supplier invoices. The app and its Dataverse data must reside in an environment that the organi
- Sandbox environments provide copy and reset capabilities for nonproduction work
Choose a sandbox when development or testing needs an isolated environment that can be copied or reset. Its purpose is nonproduction validation rather than permanent business operation.
Trap Choosing a production environment for disposable reset-based testing, although sandbox is the type designed for those operations.
3 questions test this
- Your team needs a nonproduction environment for testing changes to a production app before release. Before each test cycle the team copies production into it, and after each project the environment mu
- Contoso created an environment named QA as a production environment, but the team uses QA only for testing new releases. The team now needs to be able to reset QA to factory settings between projects
- A sandbox environment named Lab2 hosted a pilot project that has ended. You need Lab2 returned to factory settings for a new project, without any of the pilot's apps, flows, connections, or data, and
- Trial environments expire and suit short-term evaluation
A standard trial environment expires after 30 days and is intended for short-term testing. Choose a permanent environment type when the solution must continue operating beyond the evaluation period.
Trap Using a trial environment for a permanent departmental service, although the environment has an expiration lifecycle.
2 questions test this
- A maker created a standard trial environment 25 days ago to evaluate Dataverse features and built two test apps there. Nobody has converted or changed the environment since then, and the maker plans t
- Three weeks ago, a regional office created a standard trial environment and built a visitor sign-in app in it. The app is now essential, so it must keep running permanently in this environment, and th
Each tenant automatically receives one default environment, and licensed users receive Environment Maker access there. Its exploration-oriented purpose and lack of backup guarantees make it unsuitable for production workloads; it cannot be deleted.
Trap Choosing the default environment to isolate a restricted department's makers, although its maker population is tenant-wide.
4 questions test this
- The finance team builds and runs several apps in the tenant's default environment. A Power Platform administrator tries to assign the Finance makers security group to the default environment, so that
- A user who was just assigned a Power Apps license can immediately create apps and flows in the tenant's default environment, although no administrator granted the user any role there. The security tea
- Your manager proposes hosting a new business-critical app in the tenant's default environment, because it already exists and can't be deleted. You must explain why a different environment is preferabl
- Your organization moved every business-critical app out of the tenant's default environment into dedicated production environments. A Power Platform administrator now proposes deleting the default env
- Developer environments are for individual development rather than shared production
Developer environments are intended for the owner's development work, and security groups cannot be assigned to them. Recommend a production or sandbox environment when the requirement is a centrally controlled operational or shared testing environment.
Trap Selecting a developer environment for security-group-controlled production access, although that environment type does not support assigning security groups.
4 questions test this
- A maker finished an app in the maker's own developer environment, and 40 sales users must now start using it every day. The users' access must be managed centrally, and the app must run where business
- A team of five testers needs a shared environment for validating releases before production. Access must be controlled by assigning the team's Microsoft Entra security group, and the environment must
- A maker wants a personal environment for learning Power Apps and building prototypes with Dataverse tables over the next year. No one else will use it, nothing will be shared or promoted, and it must
- A team of five makers plans to build and test a shared solution in a developer environment. Corporate policy requires that access to every shared environment be controlled by assigning a Microsoft Ent
- An environment contains at most one Dataverse database
A Power Platform environment can have zero or one Dataverse database. When a solution needs independently isolated Dataverse databases for development and production, place them in separate environments rather than attempting to add a second database to one environment.
Trap Adding a second Dataverse database inside the existing environment for production isolation, although the environment supports only one.
3 questions test this
- A solution must have four independently isolated Dataverse databases: one each for development, testing, user acceptance testing, and production. An administrator wants to use as few Power Platform en
- Contoso has an environment named Env1 whose Dataverse database supports a production app. Developers need their own isolated Dataverse database for building the next release, and their work must not a
- An environment named Env2 was created months ago without a Dataverse database, and its makers already built connections and cloud flows there. A maker must now build a model-driven app with new Datave
- An environment's location determines the geographic placement of its resources
When a solution requires a particular geographic placement, select an environment in the appropriate location because the environment and the resources created in it are bound to that geography. Apps created there are routed to datacenters in that macro region. For production and sandbox environments, the location is selected at creation time.
3 questions test this
- Contoso's tenant home location is the United States. A new HR solution must keep its apps, flows, and Dataverse data in Europe to meet a data residency requirement. You're now creating the production
- A production environment named EnvUS is located in the United States geography. A maker in Germany creates a new canvas app, two cloud flows, and their connections in EnvUS, and the compliance team as
- A department wants to build its apps in the tenant's default environment, which is located in the tenant home location in North America. Regulations require the department's apps and data to be hosted
- Develop unmanaged solutions and distribute managed build artifacts
Use an unmanaged solution as the editable source in development, and export it as managed for downstream test and production environments. Keep the unmanaged source in source control; an installed managed solution cannot itself be exported as the development source.
Trap Distributing an unmanaged solution as the third-party product artifact, although it becomes editable customizations rather than a separately serviceable managed package.
3 questions test this
- Your company is an ISV that sells a Dataverse solution to many customers. Customers must receive a package that can be serviced independently of their own customizations, and they must not edit its co
- The only copy of a business solution is a managed solution that's installed in production. The original development environment was deleted. A developer wants to export that installed solution so that
- Your team develops a solution in an unmanaged solution in a development environment and deploys managed builds to test and production. You need to choose what to check in to source control as the sour
- Deleting a solution has different effects for managed and unmanaged packages
Deleting an unmanaged solution removes its container but leaves its customizations in the default solution. Uninstalling a managed solution removes its included customizations and can delete data in its custom tables and custom columns, so assess those effects before removal.
Trap Using managed-solution uninstall as a harmless container cleanup, although it removes included assets and their stored data.
3 questions test this
- A test environment contains a managed solution named Field Audit that includes a custom table and a model-driven app. Other teams' managed solutions in the same environment must stay installed. You ne
- A managed solution named Field Service Add-on is installed in production. It contains a custom Inspection table with thousands of rows and a custom column on the Account table. A maker plans to uninst
- Your development environment contains an unmanaged solution named Pilot. Pilot holds a custom table, a canvas app, and a cloud flow that other makers still use in their own work. You need to remove Pi
- Choose the custom publisher prefix before creating schema components
The solution publisher's prefix identifies new metadata components and reduces naming collisions. Create or select the appropriate custom publisher before creating tables and columns, because changing the publisher prefix later does not rename existing schema items.
Trap Changing the publisher prefix after creating a column to rename its schema, although existing metadata names are immutable.
2 questions test this
- Developers created several columns with the prefix cr8a3_ in an unmanaged solution. A lead then changes the solution publisher's prefix to fab and expects the existing columns to show the new prefix i
- Contoso is starting a new Dataverse project. All new tables and columns must use the prefix contoso, and they must not use the randomly assigned prefix of the default publisher. No tables have been cr
- Managed component ownership cannot be moved between publishers
A component's creating solution publisher owns that component. Ownership can move between solutions of the same publisher, but not across publishers after introduction in a managed solution, so choose publisher boundaries before distributing the product.
Trap Moving an existing managed component to a newly named publisher to transfer ownership, although ownership transfer is limited to solutions within the same publisher.
3 questions test this
- Fabrikam's managed solution includes a table that was created under the publisher fabrikam. After a rebrand, Fabrikam creates a new publisher named northwind and wants the table's ownership transferre
- Contoso plans several modular managed solutions that will customize one another's components. Contoso wants to keep the option of moving a component from one of its solutions to another later as the l
- Contoso's publisher, named contoso, owns two managed solutions named Core and Sales. A table that was created in Core should be shipped and owned by Sales in future releases, and the table must keep i
- Solution dependencies determine installation and removal order
Install a required base solution before installing a dependent solution. Removal reverses that order: dependent solutions or customizations must be removed before the base can be uninstalled. Use dependency information to identify what requires a component before deleting it.
Trap Inspecting managed properties to find every dependent component, although those properties control customizability rather than dependency relationships.
3 questions test this
- A vendor ships two managed solutions: Base, which defines core tables, and Analytics, which customizes components in Base. A test environment has neither installed, and an administrator plans to impor
- You plan to delete a custom column named Region from an unmanaged solution in development. Before you delete it, you need to identify every view, form, and flow that uses the column so that you can re
- A test environment has two managed solutions: Base and Extensions, which depends on components in Base. You must remove both solutions from the environment, and the administrator starts by trying to u
- Managed properties determine which distributed components remain customizable
Before extending a managed component, inspect its managed properties. If customization is permitted, add it to an unmanaged solution and customize there; the change creates an unmanaged dependency on the installed managed solution.
Trap Editing the component directly inside the managed solution, although permitted customizations must be made through an unmanaged solution.
3 questions test this
- Your unmanaged solution adds custom columns to a table that belongs to a vendor's managed solution named VendorCore. Months later, an administrator tries to uninstall VendorCore from the environment a
- The managed properties of a vendor's managed table allow new columns to be added. You need to add a Region column to that table in your development environment so that the change can be deployed with
- A vendor's managed solution includes a Service Plan table. Your team wants to add a column to that table for internal tracking in your own solution, but you aren't sure whether the vendor allows that
- Test a managed export in an environment separate from its unmanaged source
A managed solution cannot be imported into the environment that contains its originating unmanaged solution. Use a separate test environment to validate the managed installation and dependency behavior before production deployment.
Trap Importing the managed export back into the source environment to test installation, although the originating unmanaged solution prevents that import.
3 questions test this
- A maker exported an unmanaged solution named Sales as managed from the development environment. To test the managed installation quickly, the maker tries to import the managed file back into that same
- Contoso builds an unmanaged solution named Inventory in a development environment. Before each release reaches production, the team must validate the managed build's installation and dependency behavi
- Diego exports an unmanaged solution named Billing as managed from an environment named DevEnv. He imports Billing_managed.zip back into DevEnv to check the managed installation, and the import fails.
- A preferred unmanaged solution captures supported work outside explicit solution context
Set a custom unmanaged solution as the preferred solution when supported components created outside an explicit solution context should enter your deployment package automatically. The preference is not universal: components created in classic solution explorer do not enter it, and other authoring surfaces have documented limitations. Verify package membership rather than treating the preference as a guarantee for every component.
Trap Relying on the preferred solution to capture classic solution explorer creations, although that surface does not honor the preference.
3 questions test this
- Your preferred solution is an unmanaged solution named Sol1. During a sprint, you create a dataflow that loads product data, a new form on an existing table, a new view, and a new column, all outside
- You set an unmanaged solution named Sol1 as your preferred solution. A colleague then creates a new table by using the classic solution explorer and expects the table to appear in Sol1 automatically,
- Makers in a development environment often create apps and tables outside of any solution, and those components end up in the Common Data Services Default Solution. You want supported components to lan
- The system Default Solution is not an exportable deployment package
The system solution named Default Solution cannot be exported for import into another environment. Put the components to distribute in a custom solution instead of relying on their visibility in the system-wide Default Solution.
3 questions test this
- A maker adds a canvas app to an unmanaged solution named Sales and starts exporting Sales for a test environment. The app uses a custom table that the maker created outside any solution, so the table
- A maker built two apps and a table without using a custom solution. The components are visible in the system solution named Default Solution, and the maker wants to export them from there so that they
- A development environment contains three solutions: the system solution named Default Solution, which shows every component; an unmanaged solution named Sales, which contains an app and its tables; an
- Segment existing tables to ship only the assets that changed
When a table already exists in the target environment, use table segmentation to include the changed table assets and required dependencies rather than all unrelated components. Use Edit objects to select the needed columns, forms, or views. This reduces unnecessary solution layers and dependencies.
Trap Selecting Include all objects for a single-column change on an existing target table, introducing unrelated assets and layers.
3 questions test this
- You added a new column named Top Ten to the Account table in development. Production already contains the Account table and all of its other components. You need the solution update to include only th
- Your team adds the Account table to each release solution by selecting Include all objects, although each release changes only one or two Account columns. Production also has a vendor's managed soluti
- The Contact table already exists in production. In development, you changed only the table's auditing and change tracking settings, and none of its columns, forms, or views changed. You need a segment
- A table absent from the target requires Include all objects
When a table does not yet exist in the target environment, select Include all objects when adding it to the solution. Segmenting that new table can omit parts of its definition and produce missing-dependency errors during import.
Trap Applying existing-table segmentation to a first-time table deployment, leaving the target without required components.
3 questions test this
- A maker created a custom table named Asset in development and added it to a solution by selecting Include table metadata, following the team's segmentation guidance for release updates. Asset has neve
- Your next release adds a new column to the Contact table, which already exists in production, and introduces a new custom table named Equipment, which has never been imported into production. The rele
- You created a custom table named Inspection in development. The table has never been imported into the test environment. You're adding Inspection to a solution that you'll export and import into test
- Removing a component from a solution preserves it in the environment
Use Remove from this solution when an object should leave an unmanaged package but remain available in the environment. Delete from this environment is the destructive alternative: it removes the object and can remove associated data, such as rows stored in a deleted custom table.
Trap Choosing Delete from this environment to exclude a component from one release package, removing the underlying object instead of only its membership.
2 questions test this
- An unmanaged solution named Rel2 contains a custom table that the next release shouldn't ship. Other solutions in the development environment still use the table, and the table and all of its rows mus
- A maker selects a custom table named Survey in an unmanaged solution and chooses Delete from this environment, intending only to keep it out of the next export of the solution. The table held thousand
- Use a solution upgrade when obsolete components must be removed
A managed solution update adds or modifies components but does not delete omitted components. An upgrade removes components no longer included and can roll patches into a new base, so use an upgrade when the release retires an asset.
Trap Importing an update to remove an omitted column, although updates leave components that are absent from the new package.
3 questions test this
- Version 2.0 of a managed solution adds new forms and no longer includes a Legacy Code column from version 1.0. Production users must keep the Legacy Code column and its data for now, and no second cop
- A managed solution in production has a base version and three patches that were imported over several months. You're importing a new major version, and you want the base solution and all of its patche
- Version 2.0 of a managed solution no longer includes an obsolete Legacy Code column that version 1.0 added to production. When you import version 2.0 into production, the column must be removed, and t
- A solution patch contains changes to a parent and cannot delete components
A patch packages additions or modifications for a parent managed solution and is layered above that parent. It cannot remove components; Microsoft currently recommends avoiding patch-based servicing in favor of a simpler solution lifecycle where possible.
Trap Selecting a patch to uninstall one obsolete component, although patches only add or modify parent-solution assets.
3 questions test this
- You import a patch for a managed solution named Field, and the patch modifies one form. You then open See solution layers for that form to explain to a reviewer how the patch relates to the parent sol
- The next release of a managed solution named Field must retire an obsolete view in production. Field is currently serviced with patches, and a developer proposes shipping the retirement as one more sm
- Your team plans its release process for a managed solution and wants to keep team development and source control simple. A developer suggests using clone a patch and clone solution in development for
Imported unmanaged solutions and ad-hoc customizations share a single unmanaged layer rather than separate independently removable layers. Inspect that active layer when a managed deployment appears not to change runtime behavior, because unmanaged customizations can remain above managed definitions.
Trap Deleting one unmanaged solution container to roll back its layer, although unmanaged solutions do not have separate runtime layers.
3 questions test this
- In a test environment, a form's behavior comes from an unmanaged solution named Hotfix that was imported over a managed solution. You need the form to use the managed definition again, and you accept
- You imported two unmanaged solutions, SolA and SolB, into a test environment, and both customized the same form. You now want to roll back only SolA's changes to the form, so you delete the SolA solut
- You import version 3.0 of a managed solution that changes the label of an Account column. In production, users still see the old label. An administrator had earlier customized the same column directly
- Forms, model-driven apps, and site maps merge across solution layers
Model-driven apps, forms, and site maps support merge behavior when layered customizations are combined. Other component types generally use top-layer-wins behavior, so do not expect a canvas app or cloud flow to merge like a form.
Trap Expecting two cloud-flow definitions to merge their actions, although cloud flows use top-layer-wins behavior.
3 questions test this
- You import a managed solution that customizes the main form of a table that already exists in the environment. After the import, the form shows an autogenerated tab named Conflicts Tab that contains s
- Two managed solutions from the same vendor are installed in a production environment. Base adds a Sales area to a model-driven app's site map, and Ext, which is installed later, adds a Service area to
- You're importing a new version of a managed solution that includes a table's main form. You select the Overwrite Customizations option because you expect the imported form to replace the existing cust
- A staged upgrade can affect runtime before Apply upgrade consolidates the layers
A staged upgrade appears as a pending upgrade layer above the base and patches. For top-layer-wins components, that pending layer can already determine runtime properties; Apply upgrade subsequently consolidates the layers into the new base.
Trap Treating a staged upgrade as entirely inert until Apply upgrade, although its top layer can already determine component behavior.
3 questions test this
- You imported a new version of a managed solution by using Stage for Upgrade and completed a data migration. The environment now shows the base solution and a second solution with the suffix _Upgrade.
- Version 2.0 of a managed solution replaces a Region choice column with a Region lookup column. You need both the old and new versions installed at the same time in production so that you can migrate t
- The Comments column on the Account table has a Max length of 100 in a managed solution's base layer. You import version 2.0 by using Stage for Upgrade, and the pending upgrade sets Max length to 150.
- Solution checker analyzes static quality rather than guaranteeing target import success
Run solution checker on an exportable unmanaged solution to identify problematic patterns against best-practice rules. Its static analysis does not know the destination environment's configuration or installed dependencies. A clean report therefore complements, rather than replaces, target import validation.
Trap Substituting solution checker's clean report for target dependency validation, although static analysis does not inspect target configuration.
3 questions test this
- Solution checker reported no issues for an unmanaged solution named Sol1. When you import the managed export of Sol1 into production, the import fails because of a missing component that another solut
- A partner gave you a managed solution that contains JavaScript web resources. Before installing it, you want to run solution checker in your environment to find problematic patterns in its components.
- Before each release, your team wants a quick report that lists problematic patterns in its solution's JavaScript web resources, Power Automate flows, and Power Fx expressions, with links to documentat
- Object checker diagnoses live metadata and layering problems
When a deployed model-driven app or site map has an ALM-related problem in test or production, use object checker (preview) to analyze its live database metadata and layering. It examines the object regardless of which solutions contain it, unlike solution checker's offline analysis of a single exported solution file.
Trap Using only an exported package's solution checker results to diagnose the deployed object's live layering state.
3 questions test this
- Your team wants to use object checker (preview) on several components in a production solution: a model-driven app's site map, a cloud flow, a canvas app, and a custom table. Object checker is enabled
- After a release, users in production report that recent changes to a model-driven app's site map don't appear. You suspect that an active layer is hiding the customizations, and you want real-time dia
- In production, a model-driven app named Field Ops is installed only through a managed solution. Users report that recent changes to the app don't appear, and you suspect a layering problem. A colleagu
- Solution history records operation outcomes and failure diagnostics
Use See history in the Solutions area to inspect import, export, and uninstall operations and their results. For a failed operation, open its details and examine the Error code and Exception message; the Activity Id helps correlate the failure with support investigations. A solution's presence in the environment does not establish that its latest operation succeeded.
3 questions test this
- A solution upgrade failed in production. You opened the operation in the solution history and reviewed the error code and the exception message, but you still need Microsoft Customer Support to invest
- An import of a managed solution into a test environment failed overnight during a scheduled deployment. You need to view the error code and the exception message from that operation in Power Apps so t
- An attempt to uninstall a managed solution named Vendor failed in a test environment because of a dependency. You open the failed operation from See history and want the part of its details that can i
- Environment variables separate deployable logic from environment-specific parameters
Use environment variables for configuration such as a SharePoint site or list that differs between development and production. Transport the definition in the solution and supply the destination value during deployment, allowing multiple consuming components to reuse one parameter.
Trap Hard-coding the production site in each component before export, although that requires changing the application for each environment.
3 questions test this
- A production solution contains a canvas app and four cloud flows that all read an environment variable that stores a SharePoint site URL. The site is being retired, and every component must switch to
- You are adding a SharePoint list as a data source to a solution-aware canvas app. The list's site and name will differ in each environment, and you want Power Apps to resolve the site and list from a
- You are building a solution that contains a canvas app and two cloud flows. All three components read and write the same SharePoint list, but the SharePoint site and list differ between the developmen
- An environment variable's current value takes precedence over its default value
A defined current value is used even when a default value exists. The default is the fallback when no current value exists, so changing only the default will not replace an explicit destination value.
Trap Editing the default to override an existing production current value, although current-value precedence keeps the explicit value in use.
3 questions test this
- An environment variable named ApiUrl has a default value in its definition. In the test environment, nobody has set a current value for ApiUrl during import or afterward. A cloud flow in the test envi
- A solution in development includes an environment variable named ApiBaseUrl. Its definition has a default value that points to the test API, and a maker also set a current value that points to the dev
- You're importing an updated solution into production. The solution includes an environment variable definition with a default value, but you removed the variable's current value from the solution befo
- Remove source values from the solution when destinations need their own values
Before export, use Remove from this solution on the environment variable's current value when it should not travel to the next environment. The development value remains in the source environment, while deployment can supply a different destination value.
Trap Deleting the variable definition to avoid exporting the source value, although consuming components need the definition to resolve the parameter.
3 questions test this
- Your development solution contains an environment variable whose current value points to a development SharePoint site. When you deploy to test, the test team must provide its own value during import,
- You export a solution after removing the current values of its environment variables from the solution. Two of the variables have no default value. A colleague imports the solution into a test environ
- A managed solution that you imported into production included an environment variable's current value by mistake. Your team needs the value record itself to be deleted from production, and the variabl
- Secret environment variables use Azure Key Vault configuration
Use a Secret environment variable for a secret that components must reference through Azure Key Vault. Configure the required vault access rather than treating an ordinary Text variable as a dedicated secret store.
Trap Using a Text environment variable as the secret-management mechanism, although it does not provide the Secret type's Key Vault integration.
3 questions test this
- A Secret environment variable references an Azure Key Vault secret, and cloud flows in the solution already read it successfully. Now a Copilot Studio agent must use the same secret, and the vault use
- A cloud flow in a solution calls a partner API by using an API key. Security policy states that the key must be stored in Azure Key Vault, referenced by the solution rather than embedded in it, and ch
- You configured Azure Key Vault for Power Platform and registered the Microsoft.PowerPlatform resource provider. When a maker saves a new Secret environment variable, the error "User isn't authorized t
- Connection references bind solution components to destination connections
A connection reference is a solution component that points to a connector connection, while the connection contains authentication information. Bind references to usable target connections during import; use environment variables separately for parameters such as SharePoint sites and lists.
Trap Using a data-source environment variable to carry authentication, although it stores parameters rather than the connection's credentials.
3 questions test this
- A managed solution contains four cloud flows that use connection references for SharePoint and Office 365 Outlook. A data source environment variable stores the SharePoint site for each environment. Y
- A solution contains several cloud flows that use the Office 365 Outlook and SharePoint connectors. When the solution is imported into test and production, each flow must automatically use connections
- A canvas app and a cloud flow in a solution connect to SQL Server by using basic SQL authentication. The server and database names differ between the test and production environments, and the componen
- Adding an existing flow to a solution does not immediately replace its direct connections
A flow created outside a solution initially retains direct connections after it is added to a solution. Use the flow checker's Use connection references migration action, or export and import the unmanaged solution, to replace those connections with solution-aware references.
Trap Assuming Add existing automatically converts all flow connections, although connection-reference migration is a separate step.
3 questions test this
- A maker built a cloud flow outside any solution months ago and today used Add existing to add it to an unmanaged solution. When the maker opens the flow's details page in the solution, the flow checke
- A maker created a cloud flow named Flow1 outside of any solution and then used Add existing to add it to a solution. You need Flow1 to use connection references instead of direct connections. You don'
- You added ten existing cloud flows, which were all created outside solutions, to an unmanaged solution. You're about to move the solution to a new development environment by exporting it as unmanaged
- Activating a deployed flow requires access to every referenced connection
The user initially turning on a flow must own or have permission to use all its connections. A ConnectionAuthorizationFailed error therefore calls for checking connection permissions or activation by the connection owner, not merely changing the solution publisher.
Trap Assigning solution ownership to fix connection authorization, although ownership of solution metadata does not grant use of each underlying connection.
3 questions test this
- A service principal will turn on solution flows in production. The flows use connections that a developer owns, and the developer won't be available to activate them. You need the service principal to
- An integration engineer who owns every connection in a solution flow turned the flow on after import. Later, a co-owner of the flow who doesn't own those connections needs to turn the flow off for mai
- You imported a managed solution into production. A release manager tries to turn on a cloud flow in the solution and receives a ConnectionAuthorizationFailed error. The flow's connections were created
- Import custom connectors before the references and flows that depend on them
Custom connectors need to be imported in a separate solution before their connection references or dependent flows. Plan this dependency sequence rather than expecting one combined import to establish the connector and all its consumers reliably.
Trap Packaging the custom connector and its connection references into a single first import, although the connector must already be available for the dependent import.
3 questions test this
- Fabrikam's production environment has the following configuration: A solution named FreightConnector, which holds only the Freight API custom connector, was imported two weeks ago. Production cloud fl
- In production, an administrator created a custom connector named Shipping API directly on the Custom connectors page, outside any solution, with the same definition as the development connector. You m
- You must deploy a solution that contains a custom connector, two connection references that use the connector, and three cloud flows that call it. The target environment doesn't contain the custom con
- Pipelines promote the same exported artifact through sequential stages
A pipeline exports the solution when deployment is requested and promotes that same artifact through the later stages. It does not re-export development changes for each stage, ensuring that the artifact reaching production is the one that passed earlier validation.
Trap Editing development after QA and expecting the new changes in the same production promotion, although the pipeline retains the original export.
3 questions test this
- A pipeline has Test and Production stages. A maker has an urgent fix in development and wants to select the Production stage first, so that the fix reaches users immediately and is tested later. The p
- A maker deployed version 1.0.0.4 of a solution to the Test stage of a pipeline. After testing finished, the maker changed a form in development without incrementing the solution version and then deplo
- Version 1.0.0.6 of a solution passed the QA stage of a pipeline and is waiting for the Production stage. A maker then fixes a typo on a form in development, and the team wants the fix in production. T
- Pipelines deploy solutions and configuration rather than Dataverse business records
Pipelines deploy solution components and target configuration such as environment variables and connection references. They do not carry the business data stored in Dataverse tables, so plan a separate data-migration mechanism when records must move too.
Trap Relying on pipeline deployment to copy customer rows with their table schema, although business records are not included in the solution artifact.
3 questions test this
- A solution deployed with a pipeline contains a Product Category table, a model-driven app with its site map, two connection references, an environment variable, and 400 category rows that the app need
- A solution contains a custom Product Category table. Development has 400 category rows that production also needs. A maker plans to deploy the solution with a pipeline and assumes that the rows will b
- A maker's solution includes a new global choice with 12 options and three new views of the Order table. Before the first pipeline deployment to production, the maker worries that these items will have
- Production pipeline targets must satisfy Managed Environments requirements
A production destination used by Power Platform pipelines must be enabled as a Managed Environment. The pipeline host is recommended to be production but does not itself have to be managed; distinguish the host's orchestration role from the destination requirement.
Trap Enabling Managed Environments only on the host to satisfy production-target requirements, although the destination has its own requirement.
2 questions test this
- You're setting up Power Platform pipelines. The setup has a pipelines host, a sandbox environment named Dev for development, a QA target, and a production target. You must enable Managed Environments
- In October 2026, an admin receives a notice on the admin deployment page that a pipeline deploys to an unmanaged target environment named Test. The automatic managed environment setting isn't turned o
- Native Power Platform pipelines do not deploy across tenants
When deployment must cross Microsoft Entra tenants, use an ALM approach such as Azure DevOps or GitHub rather than native Power Platform pipelines. Cross-region support within a tenant does not imply cross-tenant deployment support.
Trap Enabling Cross-Geo Solution Deployments to support another tenant, although that setting addresses geography rather than tenant boundaries.
4 questions test this
- Your team uses native Power Platform pipelines for most releases and is reviewing four planned deployments. You must identify which deployment needs a different ALM tool, such as Azure DevOps or GitHu
- Contoso's pipelines host and development environment are in its own Microsoft Entra tenant. The production environment for a new customer project belongs to the customer's separate Entra tenant, in an
- Contoso develops a solution in its own Microsoft Entra tenant and must deploy it to a production environment that belongs to a subsidiary's separate Microsoft Entra tenant. The team wants an automated
- Your makers deploy to test and production in your own Microsoft Entra tenant by using native Power Platform pipelines, and they want to keep that experience. A new requirement adds an automated deploy
- Publish customizations before requesting pipeline deployment
Pipelines do not automatically publish unmanaged customizations before exporting. Publish the components that require publication in development before requesting deployment so that the exported artifact includes the intended published changes.
Trap Using the pipeline request as the publication step, although the pipeline does not publish those unmanaged customizations.
3 questions test this
- A maker changed several columns on a main form in an unmanaged solution and saved the form but didn't publish it. The maker then deployed the solution to test with a pipeline. In the test environment,
- A team lead documents the release process for makers who use Power Platform pipelines. The lead must state which part of the process publishes the unmanaged customizations, such as edited forms and vi
- In development, a maker edits Form A and publishes it, and then edits View B and saves it without publishing. The maker then deploys the solution to the Test stage with a pipeline. Which of these chan
- Pipeline prevalidation checks dependencies and target configuration before deployment
Pipelines prevalidate the solution against the target and collect connection and environment-variable configuration before deployment. Resolve missing dependencies and invalid configuration at that stage instead of planning to repair every environment manually after import.
3 questions test this
- A maker selects a pipeline stage, chooses Deploy now, and selects Next. The solution depends on a component that doesn't exist in the target environment. The maker wants to know when this problem will
- A maker selects Deploy here for the Test stage of a pipeline and then selects Next. Validation reports that the solution depends on a component that doesn't exist in the Test environment, and the make
- A solution that you deploy with a pipeline contains two connection references and three environment variables. The team wants the deployed flows connected to the correct target data sources without an
Build Dataverse data models
Read full chapterUnlock with Premium — includes all practice exams and the complete study guide.
Create intelligent applications
Create model-driven apps
Read full chapterCheat sheet
Sharp facts the exam loves — scan these before test day.
- Quick create forms streamline creation without leaving the current task
When users need to create a row from a lookup or subgrid, use a quick create form for streamlined data entry. Quick create forms also support creation from the app navigation bar when the table supports that entry point.
Trap Using a quick view form for new-row entry, although it displays related data read-only.
2 questions test this
- You have a model-driven app named App1. While working on an opportunity, users select + New in the Primary Contact lookup to add a contact. They must enter a few contact columns and return to the oppo
- You created and published a quick create form for a custom table named Inspection in a model-driven app named App1. Enable quick create forms is turned on for the table, and Inspection is included in
- Quick create requires table enablement and app inclusion
A table must have Enable quick create forms enabled and be added to the app for its quick create experience to be available. Creating the form definition alone does not complete the configuration.
2 questions test this
- You created a quick create form for a custom table named Asset in a model-driven app named App1. When users select + New in an Asset lookup, the quick create form never appears. You discover that Enab
- A custom table named Asset has Enable quick create forms turned on and a published quick create form. Users of a model-driven app named App1 still can't use the Asset quick create form, and you find t
- Quick create forms have a fixed layout and restricted controls
Quick create forms always have one section with three columns; additional sections or columns cannot be added. They cannot contain subgrids, quick view forms, web resources, iframes, notes, or Bing Maps, so a richer related-data experience requires another form surface.
Trap Using quick create for a multi-section editor with a child-record subgrid, which exceeds its layout and control support.
2 questions test this
- You are editing the quick create form for the Project table in a model-driven app named App1. A manager wants the form to include a subgrid of the project's existing tasks so that users can review the
- A maker wants to redesign the quick create form for the Contact table in a model-driven app named App1 so that it has two sections and four columns, matching the main form. You need to explain the lay
- Quick create form order selects one shared form
Although a table can have multiple quick create forms, form order determines the one used by everyone. Users cannot switch between quick create forms, and these forms cannot be assigned to security roles.
Trap Using role-specific quick create forms for separate departments, although quick create has no role assignment or form switching.
2 questions test this
- You have a model-driven app named App1. The Contact table has a quick create form named Contact Quick A. You create a second quick create form named Contact Quick B, move it to the top of the Quick Cr
- The Lead table in a model-driven app named App1 has two quick create forms named Lead Quick A and Lead Quick B, and form order places Lead Quick A first. User1 prefers Lead Quick B and asks how to swi
- Excluding a quick create form from an app does not reliably suppress it
The Unified Interface runtime can still open a table's existing quick create form from lookups and subgrids even when that form is not included in the app. Microsoft documents deleting the quick create form when its appearance must be prevented, so assess the impact on other apps before removing the shared form asset.
Trap Using the app's form asset selection alone to suppress lookup quick creation, which does not govern this runtime behavior.
2 questions test this
- In a model-driven app named App1, you removed the Contact quick create form from App1's form selection and published the app. Users still see the quick create form when they select + New in Contact lo
- You plan to delete the quick create form for the Contact table so that it stops appearing from lookups in a model-driven app named App1, even though you already excluded it from App1. The Contact tabl
- Quick view forms display a lookup-related row without allowing edits
When users need to read information about a related row while staying on another row's form, add a quick view control bound to the relevant lookup. Its data is read-only, and the control is not visible when the lookup has no value.
Trap Using a card form to show lookup-related details inside another form, although card forms are intended for compact view rows.
2 questions test this
- In a model-driven app named App1, users working on an opportunity must see the phone number and email address of the opportunity's primary contact without navigating to the contact. The information mu
- The Case main form in a model-driven app named App1 includes a quick view control that shows details of the related customer through the Customer lookup. On some new cases, the quick view control does
- Quick view forms have a deliberately limited embedded layout
Quick view forms provide one single-column tab with additional single-column sections, columns, subgrids, and spacers. They do not support form scripts or custom controls; use a form component control when the related-record experience needs richer controls.
Trap Using a scripted quick view form to supply a custom interactive related-record control, which its supported control surface cannot provide.
2 questions test this
- On the Account main form in a model-driven app named App1, users need a related-contact experience that uses a custom Power Apps component framework control to interact with the primary contact's data
- You are editing a quick view form for the Contact table that will be shown through a quick view control on the Account main form in a model-driven app named App1. You want to add more structure to the
When users need the related record's full form, tabs, timeline, or related records without navigating away, open its main form as a dialog. A lookup can be configured to open this modal experience, which can appear at the left, center, or right of the page.
Trap Using a quick view control for editing a related record's timeline and full form, although quick view is read-only.
2 questions test this
- You want users of a model-driven app named App1 to open the full contact main form as a modal overlay when they select the Primary Contact lookup on the Account form, so they stay in the context of th
- From the Account main form in a model-driven app named App1, users must open the primary contact, update its phone number, add a note to the contact's timeline, and create an appointment from the cont
When users should edit a related row within the current form rather than open its complete navigation experience, use a form component control. It embeds the related form's controls and promotes unsaved changes to the hosting main form.
Trap Using a reference panel for inline related-record editing, although reference panels provide read-only related views.
- Card forms provide compact row information in views
Card forms present table rows in a compact format suited to mobile devices. Custom card forms are attached through the legacy Read Only Grid control's Card Form property rather than simply added as standalone app forms; the newer Power Apps grid does not render custom card forms.
Trap Using the Power Apps grid's automatic list reflow as a way to render a custom card form, although that grid does not consume custom card layouts.
2 questions test this
- You created a custom card form for the Account table in a model-driven app named App1, and phone users must see it in the My Active Accounts view. The table currently uses the Power Apps grid control,
- You created a custom card form named Account Mobile Card for the Account table in a model-driven app named App1. In the classic view designer for the My Active Accounts view, you added the Read Only G
- An embedded canvas app brings a custom contextual experience into a model-driven form
When a model-driven form needs a custom visual experience combining its record context with data from additional sources, use an embedded canvas app. The canvas experience appears alongside Dataverse fields on the host form and can receive contextual data from that form.
Trap Using a quick view form for a custom interactive multisource experience, although quick view provides a read-only related-record presentation.
2 questions test this
- You are adding a custom canvas experience to the Contact main form in a model-driven app named App1 by using the form designer. The canvas app must appear on the form next to the Dataverse columns and
- On the Account main form in a model-driven app named App1, users need a custom visual area that combines the current account with sales data from SQL Server and documents from SharePoint, right next t
- ModelDrivenFormIntegration.Item exposes the hosting form's row
In a canvas app created through Customize on the classic form designer's Canvas app control, ModelDrivenFormIntegration.Item is the read-only property for accessing the host form's row. Reference a column through Item to make the embedded experience depend on that row.
2 questions test this
- You created a canvas app by selecting Customize on the Canvas app control of the Account main form in the classic form designer. A label in the canvas app must display the Account Number column, which
- You need a canvas app on the Account main form of a model-driven app named App1 to read the account that is open on the host form by using ModelDrivenFormIntegration.Item. You haven't created the canv
- The integration control's DataSource must remain the unmodified host table
ModelDrivenFormIntegration.DataSource must reference the table of the model-driven form containing the app. Leave this value unfiltered and unmodified so the integration control retains its connection to the correct parent table.
Trap Replacing the integration DataSource with a related child table to drive an embedded gallery, which changes the required host-table binding.
- The host row may not be available when an embedded canvas app starts
ModelDrivenFormIntegration.Item is not guaranteed to contain data at app startup. Gate logic that needs the host row on a readiness check such as !IsBlank(ModelDrivenFormIntegration.Item), rather than relying on startup timing to supply the record.
2 questions test this
- Logic in an embedded canvas app on the Account main form of a model-driven app named App1 needs the host account as soon as the app starts. ModelDrivenFormIntegration.Item isn't guaranteed to be popul
- An embedded canvas app on the Account main form of a model-driven app named App1 reads ModelDrivenFormIntegration.Item.accountnumber in its App.OnStart formula. Sometimes the value is blank when the a
- OnDataRefresh refreshes embedded-app state after the host form saves
ModelDrivenFormIntegration.OnDataRefresh runs its formula when the hosting model-driven form saves data. Use it to refresh the embedded app's data source or update its variables from the host row; Microsoft recommends using this event for refresh work rather than saving embedded-app changes.
2 questions test this
- When users save the host Account main form in a model-driven app named App1, the embedded canvas app must refresh its Accounts data source and set a variable to the current Account Number. You need to
- A maker plans to use ModelDrivenFormIntegration.OnDataRefresh in an embedded canvas app on the Contact main form of a model-driven app named App1 to save changes that users make inside the canvas app
- The integration control's SaveForm action saves the host form
Use ModelDrivenFormIntegration.SaveForm when an embedded canvas interaction needs to save data on the hosting model-driven form. Its target is the host form, not an Edit form inside the canvas app.
Trap Calling SubmitForm on a canvas Edit form to save unsaved host-form fields, which submits the canvas form's own data instead.
- The integration control's RefreshForm action refreshes the host form
ModelDrivenFormIntegration.RefreshForm refreshes data on the hosting model-driven form. Use it when the model-driven surface needs refreshed data, rather than treating a refresh of the embedded app's data source as the same operation.
2 questions test this
- You call ModelDrivenFormIntegration.RefreshForm from an embedded canvas app on the Order main form of a model-driven app named App1. The action requires a parameter named showPrompt with the value tru
- An embedded canvas app on the Account main form of a model-driven app named App1 updates the account's credit limit by using Patch. Afterward, the host Account form still shows the old credit limit un
- Classic embedded canvas binding needs a column guaranteed to contain a value
When adding a Canvas app control to a column in the classic form designer, use a required column guaranteed to contain a value, such as Account Name. If the bound column is empty, the embedded canvas app will not refresh in response to data changes on the host model-driven form.
- The embedded canvas control resolves App name before falling back to App ID
The Canvas app control first looks for the app using its unique name in App name. If no matching app is found, it uses App ID instead. Check these configured identifiers when diagnosing a missing-app reference.
Trap Using the app's display label as App name, which expects the solution-visible unique name.
2 questions test this
- A maker entered Customer Insights, the display name of a canvas app, in the App name field of the Canvas app control on the Account main form, and the App ID value is outdated. The form shows Sorry, w
- The Canvas app control on the Contact main form of a model-driven app named App1 has values in both the App name and App ID fields. You need to explain to a colleague how the control finds the canvas
- An embedded canvas app must exist in the current environment
The canvas app referenced by a model-driven form's Canvas app control must be in the current environment. When troubleshooting an app that cannot be found, verify its presence in the host environment before changing the form's reference.
2 questions test this
- You imported a solution with the Account main form of a model-driven app named App1 into an environment named Test. In Test, the form's Canvas app control shows Sorry, we didn't find that app, althoug
- You are planning environment strategy for a model-driven app named App1 whose Account main form embeds a canvas app by using the Canvas app control. You need to tell the team where the canvas app must
When an embedded canvas interaction should navigate the model-driven host to a particular record's main form, use ModelDrivenFormIntegration.NavigateToMainForm. Supply the table name, main form name, and record ID to identify the destination.
Trap Using canvas Navigate with a screen destination, which changes the canvas screen rather than selecting the host's record and main form.
2 questions test this
- You are writing a formula in an embedded canvas app on the Case main form of a model-driven app named App1 that calls ModelDrivenFormIntegration.NavigateToMainForm to open a related account. You need
- A canvas app embedded on the Account main form of a model-driven app named App1 calls ModelDrivenFormIntegration.NavigateToMainForm when users select a contact in a gallery, so that the host app opens
When an embedded canvas interaction should open a model-driven record list, use ModelDrivenFormIntegration.NavigateToView. Supply the table name and view name to navigate the host to that view.
Trap Using NavigateToMainForm for a record-list destination, which requires an individual record and main form instead of a view.
- OpenQuickCreateForm launches the table's default quick create form
When an embedded canvas interaction should start the host's quick create experience, use ModelDrivenFormIntegration.OpenQuickCreateForm with the table name. The action opens that table's default quick create form.
Trap Using NewForm on a canvas Edit form, which changes the canvas form's mode rather than opening the model-driven quick create form.
2 questions test this
- An embedded canvas app on the Contact main form of a model-driven app named App1 calls ModelDrivenFormIntegration.OpenQuickCreateForm with the entityName parameter set to incident. You need to tell a
- A button in a canvas app that was created from the Canvas app control on the Account main form of a model-driven app named App1 must open the host app's default quick create form for contacts. Users m
- The app designer selects which existing views belong to an app
To tailor a model-driven app's view choices, select its table view page in the app designer and use the Views tab to add or remove views. All views are available by default; selecting specific views narrows the app experience without redesigning the table's public views. Save and publish the app changes.
Trap Changing a public view's filter to remove other view choices, which changes its records rather than the app's component list.
3 questions test this
- You have a model-driven app named App1 that includes the Account table, which has eight public views. App1 users must be able to select only Active Accounts and My Active Accounts, while other apps ke
- You create a model-driven app named App1 and add the Opportunity table by using Add page > Dataverse table. You don't change anything on the Views tab for Opportunity before you save and publish App1.
- You have a model-driven app named App1 that includes the Account table. A public view named Key Accounts appears under Not in this app when you open the Views tab for the Account view page in the app
A personal view is available to its creator unless it is shared with others. Use a personal view for a user's reusable grid configuration instead of changing the administrator-managed system view for everyone.
Trap Editing the shared system view for one user's preferred grid, which changes the common definition rather than creating a private configuration.
2 questions test this
- You have a model-driven app named App1 with modern advanced find turned on. User1 owns a personal view named Budget Watch. User1 shares Budget Watch with a team named Finance and with no one else. Her
- You have a model-driven app named App1. User1 creates a personal view named My Hot Leads by selecting Create view and saving her filters. User1 hasn't shared My Hot Leads with anyone. Her manager asks
- An asterisk identifies view edits that will be lost without saving
An asterisk beside the view name indicates unsaved grid-view changes. Switching views or leaving the page restores the original definition, so save a personal view when the edited configuration must be reused.
3 questions test this
- You have a model-driven app named App1. User1 removes two columns from the Active Accounts view by using Edit columns and selects Apply, and an asterisk appears beside the view name. User1 then leaves
- You have a model-driven app named App1. User1 opens the Active Cases view and drags a column separator to widen the Title column. An asterisk then appears beside the view name. User1 asks you what the
- You have a model-driven app named App1. User1 adds two filter conditions to the My Open Orders view and selects Apply, and an asterisk appears beside the view name. User1 then switches to another view
- Users without Write permission must save an edited view as a new view
When a user changes a system view or a personal view they cannot write, Save as new view preserves their changes as a separate view. Overwriting the existing view requires Write permission, and a distinct name preserves the original definition.
Trap Using Save changes to current view on a shared view with read-only access, which requires Write permission.
2 questions test this
- You have a model-driven app named App1. User1 owns a personal view named My Deals and has Write permission to it. She edits its filters, selects Save as new view, and enters the name My Deals again, e
- You have a model-driven app named App1 with modern advanced find turned on. User2 shared a personal view named Team Pipeline with User1 and granted only Read permission. User1 edits the view's filters
- A user can override the administrator's default view personally
Set current view as my default changes the initial view for that user without changing the administrator's table default. Reset default view returns the user to the administrator-selected default.
Trap Changing the table's default public view to satisfy one user's preference, which alters the shared default.
2 questions test this
- You have a model-driven app named App1. The administrator set My Active Accounts as the default view for the Account table. User1 wants Active Accounts to open by default when she opens Accounts, but
- You have a model-driven app named App1. Last month, User1 selected Active Accounts and chose Set current view as my default, replacing the My Active Accounts default that the administrator set. User1
- Hiding a view affects only the user's selector
With modern advanced find, hiding a view removes it from that user's table view selectors across model-driven apps and devices. Deleting or deactivating a shared personal view affects everyone who uses it. A current default view cannot be hidden until another default is selected.
Trap Deleting a shared personal view to declutter one person's selector, which removes the view for all its users.
2 questions test this
- You have a model-driven app named App1 with modern advanced find turned on. A personal view named Q3 Renewals is shared with User3 and ten colleagues who still use it. User3 no longer needs it and wan
- You have a model-driven app named App1 with modern advanced find turned on. User4 owns a personal view named My Key Accounts and set it as her default view for the Account table. User4 now tries to hi
- Sharing and assigning personal views are different operations
Sharing a personal view grants other users access and requires Share permission. Assigning transfers its ownership to another user or team and is available for views the user owns; it is not necessary merely to let colleagues use the view.
Trap Assigning ownership to distribute a personal view to colleagues, which transfers the owner rather than simply sharing access.
2 questions test this
- You have a model-driven app named App1 with modern advanced find turned on. User6 owns a personal view named Vendor Audit and is moving to another department. A team named Procurement must own Vendor
- You have a model-driven app named App1 with modern advanced find turned on. User5 owns a personal view named Overdue Invoices. Two colleagues must be able to use Overdue Invoices in App1, and User5 mu
- The Power Apps grid is read-only until editing is enabled
The Power Apps grid control supports both read-only and inline-editing experiences. Its Enable editing property defaults to No, so set it to Yes when users should edit records directly in the grid.
2 questions test this
- You are standardizing the grids in a model-driven app named App1. The Account views must stay read-only, while the Opportunity views must allow inline editing. You want a single grid control that supp
- You have a model-driven app named App1. You added the Power Apps grid control to the Contacts subgrid on the Account main form by using the form designer, and you didn't change any of its properties.
- Table-level grid configuration applies across that table's views
Configure the Power Apps grid at table level when all views of the table should use that control. Configure an individual form subgrid when the requirement is limited to the related-record list on that form.
Trap Changing a single form subgrid to update every table view, which changes only that subgrid instance.
2 questions test this
- You have a model-driven app named App1 that uses the Case table. Every view of the Case table must display records by using the Power Apps grid control with inline editing. You need to choose where to
- You have a model-driven app named App1. A colleague added the Power Apps grid control to the Contacts subgrid on the Account main form, set Enable editing to Yes, and expected every Contact view in Ap
- Grid grouping requires infinite scrolling rather than pagination
The grid's Enable pagination setting defaults to No, which provides infinite scrolling. Setting it to Yes provides paging buttons, but column grouping is not supported when pagination is enabled.
Trap Enabling pagination while promising grouped grid rows, which combines incompatible grid capabilities.
2 questions test this
- You manage the Power Apps grid control for the Lead table in a model-driven app named App1. A sales manager asks for paging buttons at the bottom of the Lead views and for the ability to group leads b
- In a model-driven app named App1, the Power Apps grid control for the Opportunity table has Enable grouping set to Yes and Enable pagination set to Yes. Users see paging buttons, but the Group by opti
- Grid grouping is temporary and uses one nonlookup column
When Enable grouping is turned on, users can group rows by one supported column at a time. Lookup columns are not supported, choosing a different grouping replaces the existing grouping, and the grouping is not saved in the view definition.
2 questions test this
- In a model-driven app named App1, the Power Apps grid control for the Account table has Enable grouping set to Yes. A user can group accounts by Industry, but the Group by option doesn't appear in the
- In a model-driven app named App1, grouping is enabled on the Power Apps grid control for the Account table. A user selects Group by on the Region column, and then selects Group by on the Industry colu
- Grid aggregation exposes numeric summaries without creating a chart
Enable aggregation allows users to display sum, minimum, maximum, or average values for numeric columns. The default is No; when enabled alongside grouping, summaries also appear for each group. These runtime aggregations are not saved to the view.
Trap Using Enable grouping alone to expose numeric totals, which requires the separate aggregation setting.
2 questions test this
- In a model-driven app named App1, you set Enable grouping to Yes on the Power Apps grid control for the Opportunity table. Sales managers must see the sum of Est. Revenue for each group directly in th
- In a model-driven app named App1, aggregation and grouping are enabled on the Power Apps grid control for the Invoice table. A user groups invoices by Status and shows the sum of Amount for each group
- Nested grids require both child data and the parent relationship
To expand a grid row into related records, configure Child items with the child table and view, and configure Child items parent ID with the linking relationship column. Child editing inherits the parent grid's editability unless Disable editing in child items grid suppresses it.
2 questions test this
- You are configuring a nested grid in the Power Apps grid control for the Account table in a model-driven app named App1. You set the Child items property to the Contact table and the Active Contacts v
- In a model-driven app named App1, the Power Apps grid control for the Account table has Enable editing set to Yes and a nested grid configured for related contacts. Users must keep editing accounts in
- Reflow behavior controls the grid's small-screen presentation
The grid's Reflow behavior can force Grid only, force List only, or use Reflow to switch according to available width. Reflow is the default, so use it when the same view must adapt between desktop and narrow screens.
Trap Using Enable pagination to obtain a mobile list layout, which changes navigation through rows rather than responsive presentation.
2 questions test this
- In a model-driven app named App1, a colleague set Reflow behavior to Grid only on the Power Apps grid control for the Case table. Agents now see a table on their phones as well as on wide desktop moni
- Field technicians use a model-driven app named App1 on both phones and wide desktop monitors. The Power Apps grid control for the Work Order table must always display records as a list on every device
Navigation types allowed defaults to All. Primary only retains hyperlinks for the primary column while suppressing other lookup links; None suppresses all grid hyperlinks. Use this setting to control navigation opportunities without changing the underlying view columns.
2 questions test this
- In a model-driven app named App1, a kiosk view of the Product table uses the Power Apps grid control. The grid must not render any hyperlinks, including the primary column, but every column in the vie
- In a model-driven app named App1, users of the Case grid must still be able to open a case by selecting its primary column, but the other lookup columns in the grid, such as Customer and Owner, must n
- Main-form security roles determine which layouts users can select
When groups need different forms for the same table, assign Specific security roles in each main form's Form settings. Form order ranks available forms but does not grant form access; Quick Create, Quick View, and Card forms cannot receive role assignments.
Trap Changing form order to restrict a department's form choices, which changes preference rather than eligibility.
2 questions test this
- You are planning role-based forms for the Opportunity table in a model-driven app named App1. Opportunity has a main form, a quick create form, a quick view form, and a card form. You need to identify
- You have a model-driven app named App1. A colleague moved the Case Manager main form to the bottom of the Case form order so that service reps would stop using it. Service reps can still select Case M
- A fallback main form serves users without an explicitly assigned form
For role-based main-form configurations, designate a fallback form so users without a matching form assignment still have a usable interface. A minimally populated contingency form or a generic common form can serve this purpose. Fallback configuration does not apply to quick create, quick view, or card forms.
Trap Using a quick view form as the fallback editor, although fallback is a main-form setting.
2 questions test this
- You use role-based main forms for the Contract table in a model-driven app named App1 to restrict the information people can view or edit. Users whose roles aren't associated with any Contract form mu
- You have a model-driven app named App1. The Account table has three main forms, each assigned to specific security roles. A new employee whose security roles aren't assigned to any Account form must s
- A user's form selection persists after the initial form-order choice
Form order chooses the initial default among available forms. When a user selects another eligible form through the form selector, that selection remains their default until they select a different form, so changing order is not equivalent to resetting every user's preference.
2 questions test this
- In a model-driven app named App1, the Account Sales main form is assigned to the Sales role and ranked first in the Account form order, and the generic Account Common form is the fallback form for eve
- You have a model-driven app named App1. You move a new main form named Case Triage to the top of the Case form order and select Save and publish, expecting every user to start on Case Triage. Several
A main form can be made inactive to prevent its use while retaining the form definition. Forms must also be enabled and included in the app to appear in its form selector, so inspect both form state and app inclusion when a form is missing.
Trap Moving an obsolete form to the bottom of form order, which leaves it available to eligible users.
2 questions test this
- You have a model-driven app named App1. A main form named Lead Qualify is active, and its security roles include every App1 user. However, Lead Qualify doesn't appear in the form selector when users o
- You have a model-driven app named App1. The Account table has an obsolete main form named Account Legacy. Users must no longer be able to use Account Legacy, but the form definition must be kept for r
- Role-based public-view filtering requires an environment feature setting
Role-based system-view filtering requires EnableRoleBasedSystemViews to be true and System Administrator membership for its configuration. Configure the applicable view through View settings and Save and Publish; all system views are available to everyone by default.
2 questions test this
- You are a system administrator for a Dataverse environment that hosts a model-driven app named App1. You plan to make the nondefault public view All Leads visible in the view selector only to users wh
- You need to configure role-based access for public views of the Account table in a Dataverse environment that hosts a model-driven app named App1. The EnableRoleBasedSystemViews property is already se
- Only nondefault public views can receive view security-role assignments
Use Specific security roles on a nondefault public view to tailor its availability in the table list view selector. Default public views cannot be assigned security roles, and special-purpose view types are not interchangeable with these configurable public views.
Trap Assigning view roles to the default public view, which is excluded from this access configuration.
2 questions test this
- You plan to filter the Contact table's view selector in a model-driven app named App1 by security role. You open the Views area for the Contact table in a solution and review the available view types.
- You manage view access for the Account table in a model-driven app named App1. My Active Accounts is the table's default public view. You must make My Active Accounts available in the view selector on
- Role-based view filtering is a selector experience rather than a data-security boundary
Role-based view settings filter the table list view selector, but users can still access views through Manage and share views. System and associated views also remain visible in subgrid and associated-grid selectors. Record visibility continues to follow the user's data privileges, independently of which view is selected.
Trap Using view role assignments to make the underlying records confidential, although the feature filters a selector rather than authorizing record access.
2 questions test this
- You have a model-driven app named App1. The records in the Executive Accounts public view must be confidential, so only users who have the Executive role can read them. A colleague suggests assigning
- You manage view access in a model-driven app named App1. You assign the nondefault public view High Value Leads to the Sales Manager role and select Save and Publish. A user without the Sales Manager
- Restoring a view to Everyone can require a new sign-in
Assigning view security roles takes effect after Save and Publish, and enabling EnableRoleBasedSystemViews takes effect immediately. Changing a view from Specific security roles to Everyone can take up to 24 hours, or become effective when the user signs out and back in.
2 questions test this
- You manage view access in a model-driven app named App1. This morning, you changed the View settings of the All Cases public view from Specific security roles to Everyone and selected Save and Publish
- You are planning role-based view access for a model-driven app named App1. You need to identify which change is effective immediately on its own, without a Save and Publish step and without waiting fo
- Adding a Dataverse table page composes its form and view experience
In the model-driven app designer, Add page > Dataverse table brings selected tables into the app's page structure. Use the Pages pane and the selected table's properties to manage its forms, views, and charts rather than treating the table definition alone as a complete app.
3 questions test this
- You are building a model-driven app named App1 in the app designer. App1 is in an unmanaged solution named Solution1. Users of App1 must work with the forms and views of two existing Dataverse tables
- You are composing a model-driven app named App1 in the app designer. You added the Account and Contact tables by using Add page > Dataverse table. You now need to find the part of the Pages pane that
- You have a model-driven app named App1 that includes the Account table, which you added by using Add page > Dataverse table. In the App1 designer, you select the Account view page in the Pages pane. Y
The app designer's Navigation section organizes pages with areas, groups, and subareas. Enable Areas permits additional areas and cannot be disabled while multiple areas remain; Enable collapsible groups separately controls whether groups can expand and collapse.
Trap Using form tabs to reorganize the app's navigation areas, which changes one record form rather than the app navigation.
2 questions test this
- You have a model-driven app named App1. The App1 navigation contains three groups named Customers, Orders, and Reports, and each group contains several subareas. Users want to expand and collapse the
- You have a model-driven app named App1 whose navigation has two areas named Sales and Service. You open the Navigation settings in the app designer and try to turn off Enable Areas, but the setting ca
- Saving an app does not make its changes available to other users
Save preserves model-driven app edits, while Publish makes the changes available to users. The designer preview reflects edits immediately, and Play opens the app in run mode, so a successful preview is not evidence that the changes have been published.
Trap Using Play as a substitute for Publish, although running the app does not publish edits.
3 questions test this
- You are editing a model-driven app named App1 that the finance team uses. You remove two views from the Invoice table and want to see how App1 will appear to users with the change. The finance team mu
- You have a model-driven app named App1. You change the App1 navigation and select Save. To confirm the change, you select Play, and App1 opens in a new browser tab that shows the new navigation. You t
- You are partway through redesigning the navigation of a model-driven app named App1, which is used daily by the service team. You must keep your incomplete navigation changes so that you can continue
- App form selection controls which form assets the app includes
Select a table form in the app designer to see forms under In this app and Not in this app. Add or remove forms there and publish the app to tailor the form set; by default, all forms are selected. This app composition choice complements, rather than replaces, form-role eligibility.
3 questions test this
- You have a model-driven app named App1. In the app designer, you select the Lead form, move two unused Lead forms from In this app to Not in this app, and select Save. Two days later, users report tha
- You have a model-driven app named App1 that includes the Account table. A maker created a new main form named Account Partner for the Account table. In the App1 designer, the Account Partner form appe
- You have a model-driven app named App1 that includes the Contact table. The Contact table has four main forms, and all of them currently appear under In this app. App1 users must be able to use only t
- Model-driven apps can be shared with roles, users, or teams
Use the app's Share pane to grant access to members of selected security roles or to selected users and teams. This is the model-driven app sharing surface; possession of the app URL alone is not the sharing configuration.
Trap Distributing the Web link without granting app access, which supplies an address rather than an authorization.
3 questions test this
- You have a model-driven app named App1. You copy the Web link for App1 from the Details page and post it on a SharePoint site for the support team. Support team members open the link but can't run App
- You have a model-driven app named App1. The Salesperson security role is assigned to 200 users, but only the 15 members of a Dataverse team named Inside Sales may run App1. The team already has the re
- You have a model-driven app named App1. A contractor named User7 has the Salesperson security role, which 300 other users also have. Only User7 must be able to run App1 at this time, and none of the o
- Sharing an app does not automatically authorize its custom-table data
Users need appropriate table privileges in addition to access to a shared model-driven app. If the app opens but custom-table records are unavailable, verify the assigned roles include privileges for those custom tables rather than repeating the app-share operation.
Trap Resending the app invitation to fix missing custom-table data, which does not add table privileges.
3 questions test this
- You are an app maker who doesn't have rights to edit security roles. You built a model-driven app named App1 that uses a custom table named Site Visit, and you plan to share App1 with members of the B
- You have a model-driven app named App1 that uses a custom Dataverse table named Inspection. You shared App1 with a security role named Inspector. Inspector role members can open App1, but they can't w
- You plan to share a model-driven app named App1 with the members of the predefined Basic User security role. App1 uses the Account table, the Contact table, and a custom table named Equipment. Users m
The model-driven app sharer must have administrative privileges for the environment or be a Power Platform administrator. Their security role must have equal or greater privileges than the role they assign to the app and users, so ordinary app use does not imply authority to share it with elevated roles.
4 questions test this
- User2 has the System Customizer security role in a Dataverse environment. User2 tries to share a model-driven app named App1 and assign the System Administrator security role to the app's users. You n
- A maker named User1 built a model-driven app named App1 and wants to share it with the sales team by assigning the Sales Manager security role. User1 isn't a Power Platform administrator. You need to
- Your company wants a small group of makers to share model-driven apps with other users in a Dataverse environment. You need to recommend the Dataverse security roles that app sharers usually have so t
- A maker who needs to share model-driven apps requires the Dataverse System Customizer security role in the environment named Production, which hosts a model-driven app named App1. You need to identify
- A Microsoft 365 account alone does not make someone an environment user
A recipient of a model-driven app must exist as a user in the app's environment and meet the applicable licensing requirements. Check these prerequisites when a correctly shared app still cannot be opened; directory presence alone is insufficient.
3 questions test this
- You shared a model-driven app named App1 with a security role, and you assigned that role to User3, who has a Microsoft 365 account in your organization. User3 still can't open App1, and you find that
- User4 exists as a user in the environment that hosts a model-driven app named App1, has the required security role, and App1 is shared with that role. App1 contains premium components, and User4 can't
- A custom model-driven app named App1 is hosted in the Contoso tenant. A partner user whose home tenant is Fabrikam is an environment user with the correct role and must use App1. You need to identify
- Model-driven app sharing does not automatically email the app link
After sharing a model-driven app, copy the Web link from its Details and distribute it through an appropriate channel. A Mobile QR code is also available; the sharing operation itself does not currently send an email containing the link.
3 questions test this
- You shared a model-driven app named App1 with the Field Service security role from the Share pane. The field technicians report that they didn't receive any email about App1, and they don't know how t
- You shared a model-driven app named App1 with the Warehouse security role and assigned that role to 40 users. Some of the users work at desktop computers, and others use only phones. Your manager asks
- Your team shares both canvas apps and model-driven apps with users. A new team member assumes that both sharing processes notify users by email with a link to the app. You need to correct the assumpti
- An embedded canvas app requires explicit sharing in addition to host access
Share an embedded canvas app explicitly with its intended users or a security group, and ensure they can access the data sources it uses. Access to the hosting model-driven form does not complete this authorization workflow; the Canvas App table privilege alone also does not share the app.
4 questions test this
- You added an embedded canvas app to the Account main form of a model-driven app named App1. Users who can open the Account form report that the embedded canvas area doesn't load for them, although it
- You shared an embedded canvas app on the Case main form of a model-driven app named App1 with a security group. Group members open the form, and the canvas app reports permission problems with Dataver
- You are sharing an embedded canvas app that appears on the Contact main form of a model-driven app named App1. The canvas app must be available to about 2,000 users across several departments, and you
- An embedded canvas app on the Account main form of a model-driven app named App1 is shared with a security group, and members have read privilege for the Canvas App table. The canvas app shows a Share
- Command customization targets a specific table and command bar location
Choose the command bar location that matches the user experience: Main grid for the full-page record list, Main form for the form's top commands, Subgrid view for that table's rows embedded on another table's form, or Associated view for related data opened from the parent form. To customize contact subgrid commands on an account form, edit the contact table's Subgrid view command bar.
Trap Editing the account Main form command bar to change contact subgrid buttons, which targets a different command location and table.
3 questions test this
- The Account main form in a model-driven app named App1 includes a subgrid that lists the account's related contacts. You need to add a new command to the command bar that appears on that contacts subg
- On an account record in a model-driven app named App1, users select the Related tab and then select Contacts to view the contacts related to the account. You need to add a command to the command bar t
- Users of a model-driven app named App1 must see a new Escalate command as one of the quick actions for the Case table when they play the app. You open the Case table's command bar in the command desig
- Modern commanding separates appearance, action, and visibility
A modern command's display settings define its appearance and placement, its action defines what selecting it does, and its visibility defines when it appears. Use Power Fx for action and visibility logic in the command designer when implementing low-code command behavior.
Trap Reaching for hand-edited classic ribbon XML for a low-code Power Fx command, although classic commands do not support Power Fx actions or visibility.
2 questions test this
- You are configuring a new modern command named Approve on the Order main form of a model-driven app named App1 by using the command designer. You need to define what happens when a user selects the Ap
- You are creating a modern command named Send Survey for the Contact main grid in a model-driven app named App1. The command must appear only when the selected contact has an email address, and it must
- Command designer creates commands scoped to the selected app
Modern commands created using the command designer are visible only within the selected model-driven app. Adding the same table to another app does not automatically give that app these commands, so treat their availability as app-specific when composing the experience.
3 questions test this
- A modern command that you created with the command designer appears on the Account main form in a model-driven app named App1. Users of a model-driven app named App2, which also includes Account, must
- A modern command on the Account main form must appear in every model-driven app that contains the Account table, including apps that are created in the future. Commands that you create in the command
- App1, App2, and App3 are model-driven apps that all include the Account table. You need a new Escalate command on the Account main form that appears only in App1, so that it doesn't transfer to App2 o
- Power Fx command access also requires sharing the command component library
Users of Power Fx commands need the command component library shared with them in addition to an appropriate security role. Include that library in the access configuration when making a model-driven app's Power Fx commands available to its intended audience.
2 questions test this
- A model-driven app named App1 includes modern commands that run JavaScript actions and don't use Power Fx, and other modern commands that use Power Fx. You need to describe which security model govern
- A model-driven app named App1 has commands that run JavaScript actions and a modern command named Escalate that uses Power Fx. You share App1 with a new Field Agents security role that has the require
- Self.Selected supplies the record selection for Power Fx commands
Use Self.Selected.Item for a command's single-record context and Self.Selected.AllItems for the selected record set. For selection-count visibility, CountRows(Self.Selected.AllItems) > 1 tests whether multiple records are selected. Item is blank when the command's SelectionMax is not 1, so multi-record logic must use the selected table rather than a single record.
2 questions test this
- You are writing the action formula for a modern command on the Account main form of a model-driven app named App1. The formula Patch(Accounts, X, {'Account Name': "Changed Account name"}) must update
- A modern command on the Opportunity main grid of a model-driven app named App1 allows users to select many rows at once. The command's formula reads Self.Selected.Item.Name, but the value is always bl
- Self.Selected.State lets a command's visibility depend on form mode
Use Self.Selected.State in a modern command's visibility formula when the command should appear only in a particular form mode. For example, Self.Selected.State = FormMode.New identifies the create-form state.
Trap Testing the number of selected records to identify a new form, which measures selection rather than the form's mode.
2 questions test this
- You are configuring a modern command on the Lead main form of a model-driven app named App1. The command must appear only when Self.Selected.State = FormMode.New is true. In the command designer, you
- A modern command named Copy Address on the Account main form of a model-driven app named App1 must be visible only while users are creating a new account. A maker proposes checking whether no records
- Custom pages provide canvas experiences beyond a model-driven form
When a model-driven app needs a low-code canvas experience as a full page, dialog, or app side pane, use a custom page. Author its flexible layout and expressions in Power Apps Studio to create the required experience within the model-driven app.
Trap Using an embedded canvas app for an app-level side pane, even though embedded canvas apps can only be placed on model-driven forms.
3 questions test this
- Your team plans to add several canvas-based experiences to a model-driven app named App1 by using custom pages instead of embedded canvas apps. A designer asks where a custom page can appear within Ap
- You created a custom page for a model-driven app named App1 from the modern app designer. You now need to build the page's flexible layout, add controls, and write expressions that define the page's d
- A model-driven app named App1 needs a low-code canvas experience that opens in the app side pane on the right side of the app, where users can review tasks while they work on any page. A maker suggest
- Custom pages use the containing model-driven app's end-user sharing
Custom pages rely on model-driven app sharing, so individual pages do not need separate sharing with app users. Configure end-user access through the containing model-driven app rather than treating each custom page as a separately shared canvas app.
2 questions test this
- A model-driven app named App1 includes a custom page named Inspection Wizard. App users already reach the page through App1's sharing. A second maker on your team must now be able to edit Inspection W
- A model-driven app named App1 includes a custom page named Site Survey and is shared with the Inspector security role. Inspectors must run Site Survey, and a second maker, who can't currently open Sit
- Generative pages turn requirements into a model-driven app page
Use Add page > Generative page and Describe a page to describe the required experience, behavior, and data. The agent generates React code for the interface and logic; generative pages are supported in model-driven apps rather than canvas apps.
Trap Choosing a canvas-app screen as the host for a generative page, although this page type belongs to model-driven apps.
2 questions test this
- Your team wants an interactive Kanban page that is built by describing it in natural language and letting the app agent generate the React code. A colleague proposes hosting the page in an existing ca
- You are editing a model-driven app named App1 in the app designer, in an environment located in the United States. You need to create a new page by describing its functional requirements and data in n
- An attached image guides page design rather than supplying a runtime asset
Attach a sketch or screenshot when you want the agent to imitate a layout or visual style. To display a particular image in the finished page, provide an accessible image through Dataverse, a public URL, or a web resource instead of relying on the design attachment.
Trap Treating an attached wireframe image as an automatically hosted runtime image, which confuses design guidance with page data.
2 questions test this
- You are creating a generative page for a model-driven app named App1. Before you select Generate page, you select Add data > Attach image and upload a photo of a rough napkin sketch that shows three p
- You created a generative page in a model-driven app named App1 and attached a wireframe that includes your company logo to the prompt. The generated page imitates the wireframe layout but doesn't disp
- Generative pages can be refined conversationally or through code edits
After generation, refine the page by chatting with the agent or editing the Code tab. Saving a manual code edit creates a new iteration, while Compare becomes available from the second iteration in the current session to inspect changes.
2 questions test this
- You generated a page in a model-driven app named App1. You select Edit on the Code tab and manually change the layout code of the page. You must keep the manual changes as a new iteration of the page,
- Yesterday, you generated and refined a generative page in a model-driven app named App1. Today, you open the page in the designer and complete one new iteration by chatting with the app agent. The Com
- The maker must validate generated page behavior and accessibility
Generated code is a best-effort result, not a guarantee of compliance or correctness. Review and test it before publishing; the Accessibility assistant scans after generation and can pass violations to the agent through Auto fix, but the maker remains responsible for validating the result.
Trap Treating a successful generation preview as a compliance approval, although generation does not validate organizational requirements.
2 questions test this
- You generated a page for a model-driven app named App1 by using the app agent. After you selected Auto fix, the Accessibility assistant reports no remaining violations. Before publishing, a compliance
- You are iterating on a generative page in a model-driven app named App1. After the latest iteration, the Accessibility assistant at the bottom of the screen reports several accessibility violations in
- Existing generative pages are filtered to published pages by default
The Add page > Generative page dialog can reuse existing generative pages in the environment. Its default Published filter can hide an unpublished page; switch to All when locating one. Save preserves work, while Save and Publish publishes the app's pending changes, including generative pages.
2 questions test this
- A colleague created a generative page named Order Board in your environment but hasn't published it yet. You want to add Order Board to a model-driven app named App1. You select Add page > Generative
- A published generative page named Order Board is used in App1, a model-driven app in your environment. App2, another model-driven app in the same environment, must use the same Order Board page withou
- Generative pages can receive record and custom input context
Generative pages accept recordId, entityName, and data inputs when configured to receive them. Describe the expected inputs and how the page should use them in the prompt so the agent generates initialization logic for the contextual experience.
2 questions test this
- You are creating a generative page in a model-driven app named App1. When the page is opened, the calling page must pass a custom filter object, and the page must use the object to filter the records
- You are creating a generative page named Account Insights in a model-driven app named App1. When another page navigates to Account Insights, it must load and display the details of the account that wa
- An embedded generative page receives the current form record ID automatically
To embed a record-aware page in a form, first publish a generative page that accepts recordId, then add the Generative page component from the form designer's Display group. The host form passes its current record ID automatically; additional static inputs can be configured separately.
Trap Hard-coding the current record's ID as a static page input, which binds the experience to one record instead of using the host's runtime context.
2 questions test this
- You published a generative page named Account Health that accepts the recordId input parameter, and you are embedding it in the Account main form of a model-driven app named App1. A colleague suggests
- You published a generative page named Case Timeline that accepts the recordId input parameter. You need to add Case Timeline to a tab of the Case main form in a model-driven app named App1 so that it
- Browser-based generative-page authoring has regional and language constraints
The documented in-browser authoring experience requires an environment in the United States, Great Britain, Australia, or Singapore and supports US English prompting. AI code generation tools provide a separate worldwide public-cloud authoring route, so distinguish the browser experience from that alternative when checking availability.
2 questions test this
- Your Power Platform environment is located in the Great Britain region, and makers in your organization will create generative pages for a model-driven app named App1 by using the in-browser experienc
- Your organization's Power Platform environment is located in Canada. A maker reports that generative pages aren't available when she edits a model-driven app named App1 at make.powerapps.com. The make
- Connector-backed generative pages require a prepared connection reference
Power Platform connector support in generative pages is a preview feature. Prepare an authenticated connection and its connection reference, then select the reference through Add data > Connectors and describe how the page should use it. Selecting a connector name alone does not supply the authenticated connection.
2 questions test this
- You are creating a generative page in a model-driven app named App1 that must display tasks from a Power Platform connector, which is a preview capability. Before you can select the connector data in
- You prepared an authenticated connection and a connection reference for a Power Platform connector. You are now describing a generative page in a model-driven app named App1 that must show data from t
- A custom API lets a generative page invoke a named server operation
With preview custom API support, add an existing Dataverse custom API when a page needs to invoke a named operation at a specific time. Describe its trigger, input values, and response handling in the prompt. Ordinary plug-ins triggered by the page's row operations already run without being added as custom APIs.
Trap Adding every row-update plug-in as a page custom API, although those plug-ins already execute for their registered data operations.
2 questions test this
- A generative page in a model-driven app named App1 updates Order rows. A Dataverse plug-in registered on the Order update operation recalculates totals whenever an order changes. A colleague wants to
- A generative page in a model-driven app named App1 needs an Approve button. When a user selects it, the page must call a named server-side operation that is implemented by a Dataverse plug-in, pass th
- Page localization requires explicit language and formatting instructions
For a multilingual generative page, request translated user-visible text, appropriate right-to-left layout, and dates, numbers, and currency formatted from the user's Dataverse preferences. The page's sitemap entry is not localized automatically and must be handled separately in the app designer.
Trap Translating only the sitemap label to localize the generated interface, which leaves the page's labels and formatting unchanged.
2 questions test this
- You need a generative page in a model-driven app named App1 to support English and Arabic users. A colleague translated the page's sitemap entry in the app designer and expects the page itself to be l
- You are writing the prompt for a multilingual generative page in a model-driven app named App1. Users in several countries will use the page, and dates, numbers, and currency must appear in each user'
- Generative-page editing does not support simultaneous collaboration
Only one maker should work on a generative page at a time because collaborative editing is not supported. Coordinate page edits to avoid unintended conflicts rather than relying on the designer to merge simultaneous work.
2 questions test this
- Two makers on your team must both make changes to the same generative page in a model-driven app named App1 this week. They plan to open the page in the designer at the same time and expect the design
- Two makers edited the same generative page in a model-driven app named App1 at the same time from different browsers. Afterward, some changes made by one of the makers are missing, and the page behave
- Browser-authored generative pages can link up to six Dataverse tables
In the browser generative-page designer, use Add data > Add table to select the Dataverse tables the page should use. A single page can link up to six tables, so keep its data requirements within that supported selection.
- A browser generative-page prompt is limited to 50,000 characters
The browser generative-page authoring experience accepts a prompt of at most 50,000 characters. Keep the page requirements within this character limit when preparing the description.
- System charts are organization-owned rather than individually shared
System charts are available to app users who can read the relevant data. They cannot be assigned or shared with particular users, so do not use system-chart ownership as an audience-selection mechanism.
Trap Sharing a system chart as though it were a personal view, although system charts are organization-owned assets.
2 questions test this
- You created and published a system chart named Pipeline by Stage for the Opportunity table in a model-driven app named App1. A sales director wants only User1 and User2 to receive the chart, so she as
- You published a new system chart named Cases by Priority for the Case table, and the chart is included in a model-driven app named App1. A support manager asks which App1 users can use the chart, beca
- Chart series measure values while categories group them
Choose a series column and aggregation for the quantity to measure, and a category column for the grouping. Sum measures a total, Count measures record quantity, and Average measures the mean; choose the aggregation to match the business question rather than merely the chart shape.
Trap Using Count of revenue to show total revenue, which counts entries rather than summing their amounts.
2 questions test this
- A sales manager wants a system chart in a model-driven app named App1 that shows the average deal size for each salesperson. The Opportunity table has an Est. Revenue currency column and an Owner colu
- You are creating a system chart for the Opportunity table in a model-driven app named App1. The chart must show the total estimated revenue for each industry. A colleague configures Count of Est. Reve
- Nonnumeric chart series support counts rather than arithmetic aggregates
For a nonnumeric series column, the chart designer supports Count: All and Count: Non-empty. Numeric columns also support Average, Max, Min, and Sum; choose Count: Non-empty when missing values must be excluded from the count.
2 questions test this
- A system chart for the Contact table in a model-driven app named App1 must show, for each city, how many contacts have an email address. Contacts whose Email column is empty must not be counted. You s
- You are creating a system chart for the Case table in a model-driven app named App1. You select Status Reason, which is a choice column, in the Column dropdown list of the chart designer, and then you
- Chart averages exclude nulls but include zero values
Minimum, maximum, and average chart calculations exclude NULL values but include zero. Distinguish a missing value from an actual zero when interpreting these aggregates, because the two do not have the same effect on the result.
2 questions test this
- A group in a system chart contains three opportunity records. Their Discount values are 100, 0, and an empty value. The chart uses Average of Discount as the series aggregation. A manager asks what va
- A system chart in a model-driven app named App1 shows the average of the Discount column for each region. Some records have no value in Discount, and other records have a Discount value of 0. A manage
- Top and Bottom chart rules rank aggregated results
Configure Top or Bottom and a count to show only the highest or lowest results according to the selected aggregation. A Bottom rule on Sum of revenue selects the lowest total-revenue groups rather than the individual records with the smallest raw amounts.
Trap Interpreting Bottom on aggregated revenue as a filter on the smallest individual transaction, which ranks a different level of data.
2 questions test this
- A system chart in a model-driven app named App1 shows Sum of Est. Revenue by Account, with Set minimum and maximum values configured as Top and a Count of 3. A sales director wants the chart to rank a
- A system chart for the Opportunity table in a model-driven app named App1 uses Owner as the category and a Count: All aggregation. In the chart designer, you select Set minimum and maximum values, sel
- Stacked charts and comparison charts have different configuration constraints
Stacked and 100% Stacked options are available for bar, column, and area charts. A comparison chart can use up to two category items with one series item, so choose the supported layout according to whether the requirement is stacked measures or multiple grouping categories.
Trap Selecting a pie chart for stacked series, although stacking is supported on bar, column, and area charts.
2 questions test this
- A system chart in a model-driven app named App1 must show revenue for each quarter, with each quarter's bar split into stacked segments for each product line. A colleague suggests using a pie chart wi
- You are building a comparison chart for the Lead table in a model-driven app named App1 by using Add a category in the chart designer. A manager wants to group leads by several columns at once. You ne
- A newly published chart may still need to be added to the app
When an app uses selected charts rather than All charts, a new system chart must be selected in the app designer before users can choose it. Add it through the table view's Charts tab, then save and publish the app.
Trap Recreating a published chart that is missing from one app, when that app's selected chart list excludes it.
2 questions test this
- You published a new system chart for the Opportunity table. Users of a model-driven app named App1 don't see the chart in the chart list, although users of another app can select it. App1 was configur
- App1 is configured with specific charts for the Opportunity table, and App2 is configured to display All charts for the Opportunity table. You publish a new system chart for Opportunity. You need to d
- A chart's preview view does not permanently determine its record set
Selecting a view to preview a model-driven chart does not permanently associate that view with the chart. The chart can display data from another selected view at runtime, so interpret its values in the context of the view currently supplying the records.
2 questions test this
- Yesterday, you previewed a draft system chart for the Case table by using the My Active Cases view in the chart designer. Today, you open the same chart again in the chart designer for a model-driven
- While creating a system chart for the Opportunity table, you previewed it with the My Open Opportunities view. In a model-driven app named App1, users later display the chart with the All Opportunitie
- An oversized chart input requires fewer qualifying records
Model-driven charts support views returning up to 50,000 records. If the chart reports that the maximum record limit is exceeded, reduce the qualifying record set so the view falls within the supported volume.
Trap Changing a column chart to a pie chart to resolve the record-limit error, which leaves the oversized input view unchanged.
2 questions test this
- A column chart for the Activity table in a model-driven app named App1 displays the message The maximum record limit is exceeded. Reduce the number of records. The view that supplies the chart returns
- You are designing views for system charts in a model-driven app named App1. A reporting lead asks how many records a view can return and still be displayed by a chart before the chart shows the maximu
- Users can choose a personal dashboard instead of the system default
An app user can create a user dashboard initially visible only to them, while administrators or customizers create system dashboards for app use. A user can make their own dashboard the default, overriding the system dashboard for their experience.
Trap Replacing the system dashboard to accommodate a single user's default, which changes the shared dashboard rather than the personal selection.
2 questions test this
- In a model-driven app named App1, the system dashboard named Sales Overview opens by default for every user. User1 created a user dashboard named My Pipeline and wants it to open by default for her. A
- User2 creates a user dashboard named Team Escalations in a model-driven app named App1, in an app area where she has privileges. She hasn't shared Team Escalations or asked an administrator to customi
- Standard dashboards combine up to six components
A standard model-driven dashboard can include up to six components, such as charts and lists. When adding a chart component, select its Record Type, View, and Chart so both the visualization and the record subset are defined.
2 questions test this
- You are adding a chart to a tile of a standard system dashboard for a model-driven app named App1. The chart must show open opportunities grouped by sales stage. You select the chart icon on the tile,
- You are creating a standard system dashboard named Operations Summary for a model-driven app named App1 by using the 3-column overview layout. The operations manager wants as many charts and lists as
- Interactive dashboards support acting directly on workload records
Use an interactive dashboard when users need to review real-time work streams and act on records without navigating through the app. A standard dashboard primarily combines components such as charts and lists, whereas interactive dashboards provide this workload-oriented experience.
Trap Choosing a standard dashboard solely to satisfy interactive work-stream processing, which is the purpose of an interactive dashboard.
2 questions test this
- Service managers use a standard system dashboard in a model-driven app named App1 that shows case charts and a list of active cases. To work on a case, reps currently open it from the list. You propos
- Service reps who use a model-driven app named App1 need a one-stop workplace where they see their workload in real time across several streams and act on cases directly, without paging through the app
- Multi-stream dashboards can combine separate table-specific streams
Each interactive dashboard stream is based on one table, but a general multi-stream dashboard can contain streams from different tables. A table-specific dashboard instead bases its streams on that table; a single-stream dashboard presents one stream based on a view or queue.
Trap Combining records from unrelated tables inside one stream, although each stream has a single table basis.
2 questions test this
- A home page interactive dashboard in a model-driven app named App1 must show active cases and open tasks at the same time. A colleague proposes building one stream that contains both the Case rows and
- You create an interactive dashboard from the Dashboards area of the Case table in a model-driven app named App1. The Filter Table is preset to Case. A supervisor asks whether one of the dashboard's st
- Interactive dashboard filters have explicit table and time-column scope
Interactive charts act as visual filters. The Filter Table defines the global-filter attributes and related stream or tile scope, while Filter By selects the date column used by the timeframe filter and Time Frame sets its default interval.
Trap Changing Time Frame to switch the date column being filtered, which requires changing Filter By instead.
2 questions test this
- You are configuring a multi-stream interactive dashboard for a model-driven app named App1. The global filter must work on all charts and also on the streams and tiles that are based on the Case table
- An interactive dashboard in a model-driven app named App1 has Filter Table set to Case, Filter By set to Created On, and Time Frame set to This Month. Users must filter cases by the Resolved On column
- Queue-backed dashboard streams require queue-enabled tables
A dashboard stream can use a view or a queue only when the underlying table supports the chosen source. If a table is not queue enabled, the Queue option is unavailable and the stream must use a view.
2 questions test this
- You are adding a stream to an interactive dashboard for a custom table named Inspection in a model-driven app named App1. When the stream dialog opens, only the View option is visible, and the Queue o
- The Case table in your environment is queue enabled. You are adding a stream to a multi-stream interactive dashboard for Case in a model-driven app named App1, and the stream dialog asks you to choose
- Interactive dashboard audiences can be restricted by security role
Use Enable security roles on an interactive dashboard and Display only to these selected security roles to target its audience. Publish the dashboard after changing this configuration so the intended role-based experience is available.
2 questions test this
- You selected Enable security roles for an interactive dashboard in a model-driven app named App1, chose Display only to these selected security roles, selected the Service Manager role, and selected O
- An interactive dashboard named Escalation Center in a model-driven app named App1 must be available only to users who have the Service Manager security role. Other users of App1 must not see Escalatio
- Individual Power BI tiles can be added to personal dashboards
To mix a Power BI tile with other dashboard components, add the tile to a personal model-driven dashboard. The organization must allow Power BI visualizations, and the user needs a Power BI account and access to the source dashboard; third-party cookies are required for the documented browser authentication flow.
Trap Using a standard system dashboard tile slot as the personal Power BI Tile insertion surface, which is not that integration workflow.
2 questions test this
- User1 of a model-driven app named App1 wants a Power BI tile from her Power BI workspace to appear next to two Dataverse charts on one dashboard in App1. Power BI visualizations are enabled for the or
- Power BI visualizations are enabled for your organization, and User2 has a Power BI account with access to a Power BI dashboard. When User2 selects Power BI Tile on her personal dashboard in a model-d
- A shared dashboard does not automatically share its Power BI content
Sharing a personal dashboard containing Power BI visualizations requires sharing in both Dataverse and Power BI. Recipients need appropriate access in both services, so a visible dashboard shell does not prove they can read the embedded visualizations.
Trap Sharing only the Dataverse dashboard to grant access to embedded Power BI content, which remains protected by Power BI authorization.
2 questions test this
- Before User4 shares a personal dashboard that contains Power BI visualizations from a model-driven app named App1 with a security group, her manager asks what the recipients need so that both the dash
- User3 shared her personal dashboard, which contains Power BI tiles, with two colleagues by selecting SHARE DASHBOARD in a model-driven app named App1. The colleagues can open the dashboard and see its
- A Power BI embedded system dashboard can reference a report or dashboard
Use New > Dashboard > Power BI embedded to create a system dashboard referencing a Power BI report or dashboard and its workspace. Add it to the model-driven app through Add page > Dashboard and the Power BI dashboards picker. Users still need the applicable Power BI authorization and license.
Trap Choosing a personal Power BI tile when the requirement is an app-wide system dashboard referencing a whole report.
2 questions test this
- All users of a model-driven app named App1 must be able to open the complete Sales Performance Power BI report from a dashboard in the app navigation. Each user has a Power BI license and access to th
- You created a Power BI embedded system dashboard named Regional Sales in a solution. You now need to add Regional Sales to a model-driven app named App1 so that users can select it from the app's left
- System-dashboard Power BI embedding ignores the personal-visualization setting
Power BI content embedded in a system dashboard or form is not controlled by the environment's Power BI visualization embedding setting. That setting governs end users adding Power BI visualizations to personal experiences, so disabling it does not disable system-dashboard embedding.
Create canvas apps
Read full chapterUnlock with Premium — includes all practice exams and the complete study guide.
Build business application logic and automation
Create cloud flows
Read full chapterUnlock with Premium — includes all practice exams and the complete study guide.
Create prompts and models in AI Hub
Read full chapterUnlock with Premium — includes all practice exams and the complete study guide.
Implement business and process logic
Read full chapterUnlock with Premium — includes all practice exams and the complete study guide.