How Do You Prevent Users from Using a Dataverse BPF?
A company uses Microsoft Dataverse to manage prospects. The company has a business process flow named BPFA that is associated with the Prospect entity to streamline the prospect management process. You add a field named Category to the Prospect entity. You create additional business process flows. You apply the business process flows to Prospect records based on the selected category. Users can switch to any other newly configured business process flows but must not use BPFA. You need to configure the solution. What are two possible ways to achieve this goal? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.
Community Insight
This question tests how to make one Dataverse BPF unavailable without blocking the other flows; the trap is assuming that moving BPFA to the bottom of the display order prevents users from switching to it.
In Microsoft Dataverse, a business process flow (BPF) can be retired for users either by deactivating it or by removing all security privileges on the BPF entity. This page establishes why display order and business rules cannot enforce a hard block on BPFA while leaving newer Prospect flows selectable.
The most common wrong answer is A: changing BPFA's display order only changes its position/default in the flow switcher, not whether users can select it.
Community Discussion (5 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Deactivating BPFA is a hard control: it removes the flow from the active BPF list so users cannot select or continue using it, while the newly configured Prospect flows remain available. Removing all security privileges for BPFA is also a hard control because access to a specific business process flow is gated by privileges on that BPF; without those privileges, users cannot read or use it. Both options meet the requirement that users may switch to any newly configured flow but must not use BPFA. The key is that each option removes availability rather than merely changing presentation.Why the Other Options Are Wrong
Changing the display order of BPFA only changes where it appears in the flow switcher and which BPF is evaluated or shown first; users can still switch to BPFA if it remains active and they retain privileges. Using a business rule does not solve this because Dataverse business rules act on field values, visibility, and validation, not on the list of available business process flows. Those two options are distractors that sound administrative but do not enforce a hard deny on BPFA. This is why A and B fail the 'must not use BPFA' requirement.Community Comment Notes
sujalthakur5 and Prometix both endorsed A with C, reasoning that moving BPFA to the bottom makes newer BPFs take precedence, but that only changes ordering/default and does not stop a user from switching to BPFA. aed747e drew the sharper distinction: deactivation disables BPFA and privilege removal revokes access, while display order and business rules do not control availability. sanjaybhandekar suggested B with C, but business rules cannot remove a BPF from the switcher. EsViolet's assertion that "BPF access is not controlled simply by removing privileges from the BPF itself" is the key misconception here; BPF visibility is tied to privileges on the BPF, so removing them is a valid hard block.Official Reference
Exam Strategy
Treat 'must not use' as a hard deny, not a preference. Eliminate options that only reorder or de-emphasize BPFA, then select controls that remove availability: deactivation or privilege removal.
Frequently Asked Questions
Why does changing BPFA's display order not prevent users from selecting it?
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.
Can a business rule hide BPFA based on the Category field?
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.