PL-200 — frequently asked questions

It stores files outside Dataverse, preserving Dataverse quota for structured data and avoiding BLOB storage limits.

Yes, Microsoft supports integration between Dataverse and on-premises SharePoint Server for document management.

It displays a warning dialog but allows the user to click 'Save Anyway'. It is a advisory tool, not an enforcement constraint.

Use Alternate Keys. They act as unique constraints and will throw a runtime error if a duplicate value is submitted, blocking the save.

Option B is incorrect because table permissions are indeed the correct mechanism to enforce record-level security in Power Pages.

Yes, table permissions must be associated with web roles to apply the restrictions to the specific users (managers).

Entra ID only handles authentication (verifying identity). It does not handle authorization (permissions), which is needed to restrict users to specific store data.

You must create Security Profiles and assign them to Teams or Users, then configure record-level permissions to limit access to specific business units or records.

In Power Automate, triggerOutputs() is the standard function to retrieve the entire output of a trigger action, allowing access to dynamic content fields like body properties.

The requirement states that if the code is not populated (null), it should default to 'Standard'. The else clause in the if statement handles this default case.

Adding a channel only creates another entry point, and anyone who obtains the bot ID could still use it. Web channel security is the setting that limits the bot to your Power Pages domain.

Manual authentication lets you configure the OAuth connection to Microsoft Entra ID, so only signed-in Entra ID users can chat when sensitive data is involved.

Notes are stored directly in Dataverse. Given the constraint to minimize Dataverse storage costs, using Notes for large scanned PDFs would increase expenses significantly compared to SharePoint.

Yes, SharePoint integrates well with Power Platform. You can add a lookup column in Dataverse that points to a SharePoint library, allowing seamless access to documents from the app interface.

Removing the current value can cause import failures if no default is set. Updating the current value A provides a more controlled state.

No, the current value is environment-specific. You update it in Dev to define the solution's intent, then manage Prod's specific values via deployment or defaults.

Managed solutions are immutable. You cannot edit components or their properties within them. Restrictions must be defined in the Unmanaged solution before export.

No. Only the fields explicitly marked with 'Can be changed' set to false in the Unmanaged solution will be locked upon import.

Power Fx adopts Excel's expression model — '=' followed by functions such as If, Filter, and Sum — so spreadsheet-literate makers can build Power Platform solutions without learning a new syntax.

No. Power Fx is a separate, Excel-derived language that model-driven apps can use; it originated from the canvas app formula language and now spans multiple Power Platform surfaces.

No. Power Fx formulas are declarative and its data operations are generally asynchronous, with functions like Concurrent and Asynchronous controlling behavior.

Virtual tables do not hold their own rows in Dataverse, so they remain organization-owned; user and team ownership applies to standard tables that store data locally.

No. Auditing tracks changes to data stored in Dataverse, while virtual table records live in the external system, so Dataverse auditing does not apply to them.

An alternate key is a platform-level uniqueness constraint over one or more columns, so Dataverse rejects any insert or update that repeats the same combined values, no matter which app writes the row.

No. Flows and duplicate detection rules are conditional or advisory and can be bypassed or disabled, while an alternate key is a hard constraint enforced by Dataverse itself.

Formula columns compute a value for the current row using Power Fx; they cannot query the table to block an insert with the same Name, Company, and Contacted On values.

Define an alternate key or a duplicate detection rule on the table, which Dataverse enforces at the platform level for canvas and model-driven apps.

The list view in an app is where users see records and can create personal views. An organization-wide system view must be authored from the table component in a solution.

No. Views are configuration components; adding a table to a solution and creating a view in its table component uses built-in designer tools without writing code.

Attachments are stored in the Dataverse environment and consume file storage capacity, so they add to usage instead of reducing it.

Use SharePoint integration so documents remain in SharePoint and Dataverse stores only a reference to each document.

A gallery repeats its layout for every row of a data source and its Items property can be sorted with SortByColumns, while a card represents only one field inside a form and cannot render a list.

Use a nested or grouped gallery and control its Visible property with a context variable toggled by a header control, so each subtopic group can be shown or collapsed by the user.

No. Feedback stores the form submission content. Contact stores the person's profile. They are linked but distinct.

Yes, by customizing the form logic or using Power Automate, but the default starter layout uses Feedback.

Classic workflows are legacy, and Power Automate cloud flows are the recommended no-code automation for Dataverse; cloud flows also integrate more easily with the coaches' canvas apps.

Plug-ins are compiled C# code, and the case study states custom code is not allowed. They also cannot be created without a developer deployment.

The Evaluation table explicitly states records cannot be manually created, and a quick create form only supports manual entry by a user.

The admin center is for governance and environment settings, not for building or exporting solutions.

While integration exists, the standard method for creating the initial package is via the maker portal.

Local authentication issues its own username and password, so it cannot validate the managers' corporate identity or enable Microsoft Entra ID-based weekly sign-in.

Use Power Pages web roles and table permissions so each authenticated manager can only read and update rows tied to their store.

The Outlook connector sends client emails only in the separate service request completion flow; qualification verification just updates Dataverse Qualification records.

The authority website is public and Dataverse is cloud-based, so no on-premises data source connection is needed for this flow.

New topics only match utterances you anticipated and authored trigger phrases for; unrecognized questions by definition have no matching topic, so the effort never ends.

No. Escalate fires on explicit escalation intent or when a topic redirects to it, so it never triggers on an unmatched utterance — only the Fallback topic does.