Appearance
Enable rules
About 212 wordsLess than 1 minute
apiData Security
2026-09-01
Turns Row access policies on or off, as the Enable switch does in the console. Disabling keeps the policy but removes it from effective access. Enabling re-validates the stored policy first.
| Method and path | POST /plugin/datafor-modeler/api/auth/row/enableBatch |
| Permission | Full control on each policy's connection |
| Content type | application/json |
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| (body) | body | array | Yes | [{"id": "...", "dbconn": "...", "enable": "1"}]. enable is 1 to activate, 0 to deactivate. |
Example
curl -u admin:password -X POST \
"http://localhost:28080/datafor/plugin/datafor-modeler/api/auth/row/enableBatch" \
-H "Content-Type: application/json" \
-d '[ { "id": "8699a11df24c49ddab9451e249ff2c97", "dbconn": "Sales DW", "enable": "0" } ]'{
"success": true,
"code": "200",
"data": [
{ "id": "8699a11df24c49ddab9451e249ff2c97", "dbconn": "Sales DW", "enable": "0", "success": true }
]
}Errors
Per entry in data, with success: false:
code | msg | When |
|---|---|---|
401 | id cannot be empty / dbconn cannot be empty / enable cannot be empty / enable must be 0 or 1 | A field is missing or invalid. |
401 | No administrative privileges:<connection> | The caller lacks Full control on the connection. |
400 | Validation message | Enabling failed because a stored condition, table, or subject is no longer valid. |
Related: Data Security