Skip to content

FlexiForm developer reference

Use GetForms/GetResponse, SaveResponse and Transition for the response lifecycle once matched to your installed contract. Access tiers are enforced by the module; direct answer-table writes are not an extension path.

Validates a saved draft by key without publishing or saving answers. Replace project-review with an existing form key. Optional compiled details are omitted.

Transport: unbound Dataverse action; JSON string Request in, JSON string Response out. pfx_ is a prefix token, not a literal deployment name. Read the calling conventions first.

Inner Request — illustrative
{
"form": "project-review"
}

form: saved form key. Alternatively, definition supplies an inline form definition. Findings include diagnostic paths.

Inner Response — illustrative excerpt
{
"ok": true,
"errors": [],
"warnings": []
}

The schema requires Write privilege on pfx_FlexiForm. Prefix tokens in table names resolve with the installed publisher. Record access, module role checks and input validation can further restrict the call. Do not interpret a missing execute privilege as anonymous or unrestricted access.

Handle a Dataverse fault separately from validation findings in the response. Test invalid input and the intended non-administrator role. Do not treat an empty result as a grant of access or a guarantee that no configuration exists.

Selected schema-declared registrations are shown for troubleshooting context. This is not a complete installed registration inventory. Preserve module-owned registrations; do not duplicate or disable them.

Owned registration Message / table Declared stage / mode
FlexiForm: guard response create Create · pfx_flexiresponse PreValidation / Sync
FlexiForm: guard response update Update · pfx_flexiresponse PreValidation / Sync
FlexiForm: guard answer create Create · pfx_flexianswer PreValidation / Sync

The full execution path may also include dynamically maintained registrations. Inspect the installed solution for exact stage, mode, filters and images before investigating interactions with your own plugins.

Confirm the installed operation name and permissions. Test representative data, empty results and denied access. Keep your integration in its own solution, and review contract changes before upgrading.

Administrator guide · Extension boundaries