Architecture you can build around
Switchboard is delivered as Dataverse solutions. Administrators configure modules in model-driven apps; server-side operations use Dataverse Custom APIs and plugins. Your extensions should connect at documented boundaries, leaving module-owned records and execution behavior intact.
How a request travels
Section titled “How a request travels”| Layer | Responsibility | Your integration boundary |
|---|---|---|
| Model-driven apps and form controls | Configuration, validation feedback and record experiences | Published form configuration and documented controls |
| Dataverse Custom APIs | Named operations, input validation and permission checks | Reviewed preview contracts in this reference |
| Plugins | Enforce lifecycle rules and perform server-side work | Observe effects; do not replace owned registrations |
| Dataverse data | Configuration, versions, business records and run history | Your business tables, subject to access and module rules |
| Background processing | Work that must continue outside the interactive request | Documented job status and cancellation operations |
A module preview is not a promise that every layer has completed release acceptance. Confirm the installed solution version before integrating.
Core and module independence
Section titled “Core and module independence”Core supplies shared capabilities such as metadata access, record lookup and background dispatch. Modules bring their own configuration and behavior. Do not assume that installing one module installs every other module or grants cross-module permissions.
Identity and permissions
Section titled “Identity and permissions”Calls run through Dataverse authentication. The API’s execute privilege and its record-level checks both matter. Some lifecycle and background work has its own execution context; do not assume it always inherits the interactive user’s access. Test each documented operation under the intended identity.
Do not put credentials in website code. A browser extension inside a model-driven app can use the supported Dataverse client API. Server integrations require your organization’s approved application identity and Dataverse application-user role.
Synchronous work and jobs
Section titled “Synchronous work and jobs”A synchronous operation can return a result immediately and may take part in the Dataverse transaction. Job-based work returns an identifier to monitor. A request timeout is not proof that a write failed: inspect its result or job before retrying. Never call internal worker dispatchers as a substitute for a supported operation.
Customizations that survive upgrades
Section titled “Customizations that survive upgrades”Keep your custom tables, forms and commands in your own solution. Use the documented API operations rather than directly editing version, counter, job or audit records. Do not depend on private web-resource functions, generated bundles or plugin class names.
Review extension and plugin boundaries, then choose a module in the sidebar.