Agiled Docs

After creating custom attributes, keep them organized so record forms stay easy to use.

Custom attributes can appear on records, imports, forms, reports, and workflows. Review those downstream uses before changing or removing a field.

Edit An Attribute

Open Settings.
Go to Attributes.
Choose the entity type.
Open the attribute actions.
Edit the field details.
Save changes.

Edit labels and help text when the meaning is still the same. If the field now captures a different kind of data, create a new attribute instead so old records do not become misleading.

Before renaming an attribute, search forms, imports, saved views, workflows, and team instructions for the old name so users are not left following stale setup guidance.

Enable Or Disable

Disable an attribute when you no longer want it used on records but do not want to delete it yet.

Disabling is the safer first step when you are cleaning up old fields. It gives your team time to confirm no forms, imports, workflows, or reports still depend on the attribute.

Leave the attribute disabled for a review period when it holds historical data. Deletion should be the final cleanup step, not the first one.

During the review period, watch forms, imports, saved views, workflows, and reports for errors or missing fields. If something still depends on the attribute, update that dependency before deleting.

Reorder Attributes

Use drag-and-drop ordering when available. Put the most commonly used fields near the top.

Order fields by how users complete the record. Put identity and qualification fields first, operational fields next, and rarely used audit or internal fields near the bottom.

Review custom attributes regularly for duplicate fields, unclear labels, unused required fields, and fields that only one old process used. Disable first, observe the impact, then delete only after downstream use is checked.

When two attributes mean the same thing, choose one target field and migrate records in a controlled batch. Do not leave both active unless the team can explain the difference.

Delete An Attribute

Delete custom attributes only after confirming the field is no longer needed. System attributes cannot be deleted.

Before deleting, check:

Existing records that use the field.
Public forms or internal forms that map to the field.
Import templates or CSV mappings that include the field.
Workflow conditions, actions, or filters that reference the field.
Reports, saved views, and exports that rely on the field.

When the data matters historically, export the records or keep the attribute disabled instead of deleting it.

Test After Changes

Open one record for the affected entity and confirm the custom attributes appear in the expected order. Then test one form or import flow if the attribute is used for customer intake or migration work.

If workflows or reports use the attribute, run one safe test or report refresh after the change before telling the team the field is ready.

Tell users when a required field changes. Otherwise they may discover the change only when a form, import, or record save fails.

Attribute Migration Checklist

Before replacing or deleting a field:

export or review existing values
decide the replacement field
update forms, imports, workflows, and saved views
bulk edit or import migrated values where needed
disable the old field before deleting it
spot-check records after cleanup

Manage Custom Attributes