How to Remove Custom Fields
Learn how to delete a custom field from an octapipe pipeline in a safe and controlled way
Support Team
Last Update 4 months ago
Removing custom fields allows you to clean up attributes that are no longer needed in the pipeline, freeing space and simplifying the workflow. See how to perform this process safely below.
1st Step: Accessing the Pipelines Module
In the upper left side menu, click “Pipelines”.
1st Step: Accessing the Pipelines Module
In the upper left side menu, click “Pipelines”.

2nd Step: Locating the Custom Field
- Open “Module Settings” represented by the Gear Icon.
- Select the “Fields” tab.

3rd Step: Removing a Custom Field
3. Click “Confirm”.
- Click the field you want to delete and then click the "Remove" button represented by the trash icon.
- Confirm in the warning dialog: “Are you sure you want to delete this field?”
3. Click “Confirm”.

Best Practices:
• Pre-removal audit: record the justification, author, and date in the changelog for compliance purposes.
• Data backup and export: save the field values via CSV or API before removing it.
• Dependency analysis: map automations, reports, and dashboards that use the field and adjust them beforehand.
• Validation in a staging environment: simulate the removal to verify impacts before applying it in production.
• Communication and alignment: inform Dev, Ops, and stakeholders about the planned removal and its effects.
• Documentation update: remove references to the field in runbooks, scripts, and wikis.
Conclusion:
You have learned how to remove custom fields in a pipeline safely and in a controlled manner. If you have any questions, contact our support team.
• Pre-removal audit: record the justification, author, and date in the changelog for compliance purposes.
• Data backup and export: save the field values via CSV or API before removing it.
• Dependency analysis: map automations, reports, and dashboards that use the field and adjust them beforehand.
• Validation in a staging environment: simulate the removal to verify impacts before applying it in production.
• Communication and alignment: inform Dev, Ops, and stakeholders about the planned removal and its effects.
• Documentation update: remove references to the field in runbooks, scripts, and wikis.
Conclusion:
You have learned how to remove custom fields in a pipeline safely and in a controlled manner. If you have any questions, contact our support team.
