Ripple developer reference
Integration boundary
Section titled “Integration boundary”Use this check when coordinating form or automation ownership. It is not authorization to write a column. Recalculation and job operations can change records; worker Process and internal Ruleworks dispatch are not direct consumer entry points.
pfx_RippleGetManagedColumns
Section titled “pfx_RippleGetManagedColumns”Reads columns owned by active non-inherit rules on the target table. This is a response excerpt; build, administrator and other default 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.
Request
Section titled “Request”{ "table": "account"}table: required logical table name. columns: target column logical names; this endpoint is not a complete list of every column touched by inheritance.
Response
Section titled “Response”{ "columns": []}Permissions and failures
Section titled “Permissions and failures”The schema requires Read privilege on pfx_RippleRule. 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.
Plugin steps and customizations
Section titled “Plugin steps and customizations”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 |
|---|---|---|
| Ripple: protect rule create | Create · pfx_ripplerule |
PreOperation / Sync |
| Ripple: protect rule update | Update · pfx_ripplerule |
PreOperation / Sync |
| Ripple: protect rule delete | Delete · pfx_ripplerule |
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.
Before building against this preview
Section titled “Before building against this preview”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.