THE TOOLKIT, IN PRACTICE
Know what
you can build.
Portal exports reveal the sources. Solution metadata adds forms, views, fields and component bindings. Paqvilo makes those relationships easier to work with.
01 / LIVE PREVIEW
Lense
Your local changes.
The online platform.
Override & preview
Discovered JavaScript, CSS, images and fonts; supported page, form and list inline fields; unambiguous literal HTML baseline patches in page copy, templates and snippets.
Inspect & trace
Page/template/snippet/asset chains, rendered controls, exported roles and permissions. With Solution sources: FormXml, views, fields, PCF manifests and resources, observed Web API entity sets, plugin registrations and mapped C# sources.
See what happened
Applied resources, unmatched patches, errors and changes needing deployment. Source audits measure classification; inspect the actual page to verify an overlay.
02 / LOCAL DEVELOPMENT
Mirage
Your exported portal.
A local working model.
Render & serve
Exported assets, supported Liquid and includes, snippets and language variants. Native forms, lists, typed fields, lookups, subgrids, quick views and notes from supported exported metadata.
Inspect & simulate
Source navigation with local runtime context. Supported Web API CRUD, FetchXML, queries, relationships and role/table-permission scopes. Separate local personas, records and explicitly registered project data packs.
Extend supported contracts
Standard PCF page controls, enabled native single-field bindings and explicit Liquid dataset bindings. Exported operations with supported request/response flows, JSON mocks, opted-in local server code or trusted providers. Plugin registrations with supported write-stage mocks or trusted handlers.
Control local scenarios
Tweaks for identity and permission/data scenarios; /_sim/ for local administration. Source edits and project-owned tests stay separate from the online environment.
MAKE THE BOUNDARY EXPLICIT
A useful model.
An honest scope.
Mirage implements selected Power Pages contracts. Unsupported features retain diagnostics. Native list/subgrid PCF hosting falls back to the native grid; React/virtual controls, platform libraries, advanced dataset operators and record navigation remain unsupported. External connectors, custom APIs and unsupported flow actions need project providers or mocks. Compiled Dataverse plugin assemblies require explicitly configured original-assembly mode on Windows; they do not run by default.
Standard, enhanced and code-site/SPA exports have different source coverage. Missing managed metadata and dynamic references can leave bindings unresolved. Validate your deployed result in an authorized environment. Deployment stays with your separate PAC/site process.