Actions108
- Activity Log Actions
- Consent Analysis Actions
- Cookie Scanner Actions
- Web Container Actions
- Get Web Tag
- Create Web Constraint
- Create Web Container
- Create Web Perimeter
- Create Web Tag
- Create Web Trigger
- Delete Web Constraint
- Delete Web Container
- Delete Web Perimeter
- Delete Web Tag
- Delete Web Trigger
- Get Web Constraint
- Get Web Perimeter
- Get Web Trigger
- List Web Constraints
- List Web Containers
- List Web Perimeters
- List Web Tags
- List Web Triggers
- Revert Web Tag
- Update Web Constraint
- Update Web Container
- Update Web Perimeter
- Update Web Tag
- Update Web Trigger
- Data Cleansing Actions
- Destination Actions
- Event Delivery Actions
- Event Enrichment Actions
- Live Report Builder Actions
- Mix Collect Redirect Rule Actions
- Monitoring Actions
- Normalized Datalayer Actions
- Segment Actions
- Source Actions
- Sources Data Quality Actions
- User Actions
- Web Containers Variable Actions
- Create Web Datalayer Variables
- Create Web Datalayer Variables Category
- Create Web Internal Variables
- Delete Web Datalayer Variables
- Delete Web Datalayer Variables Category
- Delete Web Internal Variables
- Get Web Datalayer Variables
- Get Web Internal Variables
- List Web Datalayer Variables
- List Web Internal Variables
- Workspace Actions
Data Cleansing → Update Cleansing Transformations
AI-generatedOverview
This node operation updates an existing data cleansing transformation in the Commanders Act platform. It is useful for users who need to modify cleansing transformation configurations to improve data quality and consistency in their data processing workflows. For example, a user might update a transformation to correct data formatting or apply new cleansing rules to incoming data streams.
Use Case Examples
- Updating a cleansing transformation to change the rules applied to incoming data for better accuracy.
- Modifying an existing transformation to include additional data fields or filters.
Properties
| Name | Meaning |
|---|---|
| Cleansing Transformation ID | The unique identifier of the cleansing transformation to update. |
| Query Parameters | Optional parameters to refine the API request, such as filters, pagination, sorting, and other query options. |
| Request Body | JSON object containing the updated data cleansing transformation details to be sent in the request body. |
Output
JSON
json- The JSON response from the Commanders Act API representing the updated cleansing transformation or status information.
Dependencies
- Commanders Act API with API token credentials
Troubleshooting
- Ensure the 'Cleansing Transformation ID' is provided; otherwise, the node will throw an error indicating the missing ID.
- Verify that the API token credentials are correctly set up and valid to avoid authentication errors.
- Check the JSON format of the 'Request Body' to ensure it is valid and matches the expected schema for updating cleansing transformations.
- If the API returns an error, review the error message for details on what might be wrong with the request parameters or body.