AB-410 — Frequently Asked Questions

Automated cloud flows run asynchronously after a record event, so they cannot block or immediately warn a user during form entry; they also duplicate logic per flow.

Yes. Table-level business rules apply to all forms for that table and can be scoped as needed, which reduces duplicated validation across forms.

Canvas apps do not render Dataverse model-driven forms, so the rule has no form context to attach to. Use Entity/Table scope so the rule evaluates against the table data.

It limits the rule to that form; if the form is used only in the intended app, the effect is app-only. Other apps or forms using the Account table are unaffected.

A Word template produces a document from data, usually through Power Automate, and is not a generative AI prompt inside the app. The case requires reusable generative AI with dynamic inputs and minimal custom code.

Yes. Prompts can be invoked from Power Apps, Power Automate, and Copilot Studio, matching Fabrikam's requirement for reusable generative AI solutions.

A canvas app is a user interface; the scenario needs autonomous background analysis, orchestration, and storage, which are handled by AI Builder, cloud flow, and Dataverse.

No. A business rule enforces logic on Dataverse records but cannot retrieve external feedback, call an AI prompt, or orchestrate an escalation workflow.

A prompt column is bound to one table, so it cannot act as a shared instruction asset for forms on several tables. An AI Builder custom prompt is reusable at the environment level.

Yes. The Prompt control can reference a reusable AI Builder custom prompt, allowing the same tone, structure, and required-field instructions to run across forms for multiple tables.

It supports only Approve and Reject, so it cannot represent the Escalate to manager outcome; use Custom Responses - Wait for one response instead.

Yes. With Custom Responses - Wait for one response, the approval completes on the first decision and does not wait for the remaining approvers.

Moderation filters harmful or disallowed content categories; it does not check whether a claim is grounded in your internal support knowledge, so fabricated facts can still pass.

No. It makes answers more consistent and conservative while still responding; only very low values risk terse or repetitive output, so test a moderate low setting.

Do until re-evaluates its condition each iteration, so it can keep running until the status field equals Complete; Apply to each only walks a collection that already exists.

Yes. Apply to each iterates the array retrieved at the start, so it does not pick up records added later and processes each item in that fixed collection once.

The Customer column is a polymorphic lookup to an Account or Contact record and stores no tier value. A Choice column holds the fixed tier options such as Gold, Silver and Bronze.

An alternate key creates a unique index over one or more columns, so external systems can look up records by a stable business value instead of the GUID and duplicates are rejected.

Display order only changes where BPFA appears in the business process flow switcher and which flow is the default; users can still switch to BPFA if it remains active and they have privileges.

No. Dataverse business rules control field behavior and values, not the list of available business process flows, so they cannot enforce the 'must not use BPFA' requirement.

Cloud flows run asynchronously on the server after a Dataverse event, so nothing is pushed to the open form; the user would need to refresh to see any change.

Use JavaScript form event handlers (OnLoad, OnChange, OnSave) with formContext controls, or business rules for simpler visibility and requirement logic.

Identity fields such as the username/UPN are synced from Microsoft Entra ID and read-only in Dataverse, so the field cannot be changed in the app.

Yes. Dataverse links the systemuser record by object ID, so updating the UPN in Entra ID keeps the same user record and its app history.

The mailbox record only stores email server and synchronization settings. Authentication uses the UPN on the Microsoft Entra ID user object, which the mailbox rename never updates.

No. The Dataverse user record linked to the app history stays intact; updating the UPN in Microsoft Entra ID renames the identity without recreating the user.