You create a form in a model-driven app that uses data from the Lead table in a Microsoft Dataverse instance. You add a business rule to the Lead table. The business rule displays an error if the…

Question

Options

• ADeactivate the business rule. Change the scope for the rule to Table and then reactivate the rule.
• BReplace the business rule logic with a Microsoft Power Automate cloud flow by using the
• CExtend the webFormClientValidate JavaScript function to replace the business rule logic. Edit the
• DCreate a JavaScript web resource and replace the business rule with a JavaScript function. Add

• A
  72% (36)
• B
  10% (5)
• D
  18% (9)

Explanation

Business rules scoped to 'All Forms' only execute on model-driven app forms - they do not run on Power Apps Portal (Power Pages) web forms. To enforce the same logic on the portal, two approaches work: (A) Changing the scope to 'Table' (entity level) causes the business rule to execute server-side, meaning it applies universally regardless of the interface - including portal submissions - and (C) Extending the webFormClientValidate JavaScript function lets you implement custom client-side validation on the portal web form, effectively replicating the business rule logic. Option B (replacing with a Power Automate flow) could work for some validations but flows are asynchronous and cannot block a form submission with a synchronous error message. Option D (JavaScript web resource) applies to model-driven apps, not Power Pages portal pages.

No community discussion yet for this question.