Skip to content

Stamp developer reference

Use Preview to inspect formatting without reserving a number. Counter adjustment, manual fixes and backfill are controlled writes. Do not allocate numbers by editing counter rows or call the internal worker directly.

Reads target columns owned by active Stamp rules. This is a response excerpt; build, administrator and length fields 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
{
"table": "account"
}

table: required logical table name. columns: logical column names managed by active rules.

Inner Response — illustrative excerpt
{
"columns": []
}

The schema requires Read privilege on pfx_StampRule. 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
Stamp: protect rule create Create · pfx_stamprule PreOperation / Sync
Stamp: protect rule update Update · pfx_stamprule PreOperation / Sync
Stamp: protect rule delete Delete · pfx_stamprule PreOperation / 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