Extension points and plugin steps
Where to extend
Section titled “Where to extend”| Need | Preferred approach |
|---|---|
| Add a command to your app | Call a reviewed API from a command you own; handle validation and access failures |
| Change a record experience | Configure documented form rules or controls; keep your form changes in your own solution |
| Reuse a configuration | Use the module’s pack or template facilities when included in your installed version |
| Coordinate business automation | Define who owns each target column and test the combined flows, plugins and rules |
| Read progress | Use documented results and job views; avoid changing engine-owned status records |
Understand the plugin pipeline
Section titled “Understand the plugin pipeline”Dataverse plugins run on messages such as Create, Update and Delete. PreValidation can reject an operation early; PreOperation runs before the core data operation; PostOperation runs after it. Synchronous steps affect the calling operation, while asynchronous work completes later.
Module references describe selected owned steps and their purpose. These are compatibility context, not instructions to register a second copy. A schema entry may omit a stage or mode; this documentation does not invent the installed value. Inspect the installed solution registration when troubleshooting ordering.
Keep ownership clear
Section titled “Keep ownership clear”Do not disable module guard steps to bypass validation. Do not write directly to published versions, allocation counters, job state or audit history. A custom plugin or flow that writes the same field as Switchboard can create competing updates; document the owner of that field before activating either.
Filtering attributes limit when Update steps run. Changing a registration, its images or its execution order can change behavior. Preserve the managed registration and raise a compatibility issue rather than modifying it in place.
Planned adapters are not public SDKs
Section titled “Planned adapters are not public SDKs”Provider and adapter designs may appear in product plans. Unless a module reference publishes a reviewed contract, treat those hooks as planned. This includes implementing custom usage providers or source adapters against internal types.
Form customizations
Section titled “Form customizations”Use the documented Microsoft Client API and installed control configuration. Do not scrape the model-driven app DOM, import private runtime modules or attach to undocumented browser globals. The existence of a private implementation helper is not an extension contract.