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 → Destroy Cleansing Transformations
AI-generatedOverview
This node operation allows users to destroy (delete) a specific data cleansing transformation in the Commanders Act platform. It is useful for managing and maintaining data cleansing rules by removing outdated or unnecessary transformations. For example, if a cleansing transformation is no longer needed or was created by mistake, this operation can be used to delete it permanently.
Use Case Examples
- Deleting a cleansing transformation by specifying its ID to clean up the data processing pipeline.
- Removing an obsolete transformation to prevent it from affecting data quality.
Properties
| Name | Meaning |
|---|---|
| Cleansing Transformation ID | The unique identifier of the cleansing transformation to be destroyed. This is required to specify which transformation to delete. |
Output
JSON
Status Code- Indicates the HTTP status code or response status of the delete operation, e.g., '204 No Content' for successful deletion.
Dependencies
- Requires Commanders Act API credentials including site ID and API token for authentication.
Troubleshooting
- Error 'Cleansing Transformation ID is required' occurs if the ID is not provided; ensure the ID is specified.
- API errors may occur if credentials are missing or invalid; verify API credentials are correctly configured.
- Network or permission issues may cause API call failures; check network connectivity and user permissions.