Skip to content

FormFlow developer reference

Extend through authored form rules and supported form setup. GetBundle is runtime delivery, not a promise that private bundle structures are a stable third-party SDK. Keep server-side validation separate.

Validates a saved rule set without activation. Replace the example GUID with a readable saved rule set.

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
{
"ruleSetId": "11111111-1111-1111-1111-111111111111"
}

ruleSetId: saved rule set GUID. Alternatively, ruleSet supplies an inline draft. Findings identify ruleId, actionId and path when relevant.

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

The schema requires Write privilege on pfx_FormRuleSet. 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
FormFlow: rule set created Create · pfx_formruleset Not specified in schema / Sync
FormFlow: rule set changed Update · pfx_formruleset Not specified in schema / Sync
FormFlow: rule set deleted Delete · pfx_formruleset Not specified in schema / 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