POST /api/database/views/{view_id}/copy-configuration/
Copies the requested configuration categories, the filters or sorts for example, of another view in the same table into this view, replacing this view's existing configuration of those categories. Only categories supported by both view types can be copied. The whole copy can be reverted with a single undo.
Servers
- /
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
view_id |
Integer | Yes |
The view to copy the configuration into. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
ClientSessionId |
String | No |
An optional header that marks the action performed by this request as having occurred in a particular client session. Then using the undo/redo endpoints with the same ClientSessionId header this action can be undone/redone. |
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
ClientUndoRedoActionGroupId |
String | No |
An optional header that marks the action performed by this request as having occurred in a particular action group.Then calling the undo/redo endpoint with the same ClientSessionId header, all the actions belonging to the same action group can be undone/redone together in a single API call. |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
source_view_id |
Integer | Yes |
The id of the view in the same table to copy the configuration from. |
categories[] |
Array | Yes |
The configuration categories that must be copied. Only categories supported by both the source and destination view type are accepted. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.