PL-400: Microsoft Power Platform DeveloperDemo

By Microsoft · Question Mode

QuestionQ67

Extend the user experience

Users open a form in a model-driven app through a special URL that supplies values for three lookup columns.

The form has three tabs: A (the default), B, and C. JavaScript is currently registered as follows:

  • OnLoad: A lookup column on every tab retrieves data that populates columns on that same tab.
  • OnSave: Data validation uses calculations involving columns on the form. When a value falls outside the allowed range, the record must not be saved.

Creating a new record is taking too long to load and save. Create event registrations that shorten both operations without removing functionality.

Select
OnLoad
OnSave
Explanation

TabStateChange occurs when a tab is expanded or collapsed, so using it for tabs B and C defers their lookup-driven retrieval until those tabs are accessed; tab A remains available at initial form load. OnChange runs when a form column value changes, allowing calculation-based validation to occur before saving. An OnSave handler runs before persistence and can cancel the save, whereas PostSave runs after the save operation and cannot enforce the requirement to prevent an invalid record from being saved. OnOutputChange applies to control output changes, not standard form-column calculation triggers.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!