Manage Custom Fields in Ironsight

When to Use Schema Builder

Editing an Activity’s Custom Fields: Add, update, or archive dropdown options and other custom field values.
Creating a New Activity With Custom Fields: Create the Activity first without custom fields, then return to edit it in Schema Builder.

Key Risks & Rules

DO NOT delete fields – This can break dashboards and cause historical job data to disappear from analytics.
If a field is no longer needed:
- Mark it as “Do Not Use” or “Archive” instead of deleting.
- Contact a Ironsight if permanent removal is required.
Avoid unnecessary schema changes during active work hours to minimize disruption.

Step-by-Step: Updating Custom Fields

Log in to Ironsight and ensure your account has the Manage Custom Fields permission.
Go to the Admin Portal.
Navigate to:
- Services (in Admin Portal) → Select the relevant service/activity (e.g., Drill).
- Note: In Dispatch Hub, “Activity” is the term used; in the Admin Portal, it’s called “Service.”
Click “Edit in Schema Builder”.
In Schema Builder:
- Close the preview panel if it opens.
- Locate the field you want to update in the middle column (e.g., Pig Serial Number).
To Add Options:
- Click the field.
- Add items one-by-one with the Add Option button, or
- Use bulk paste from Excel, Word, or any text list (ensure consistent formatting).
To Remove Options:
- Do not delete directly.
- Instead, label as “Do Not Use” or Contact Ironsight to “Archive" or Delete Parmanently.
Save Changes:
- After editing, open the preview to verify the update.
- If correct, click Save to apply the change to all jobs using this schema.

Impact on Active Jobs

New values will appear immediately in forms and dropdowns for new jobs.
For active (uncompleted) jobs:
- Updated options will be available when the job form is reloaded.

Users are required to refresh their browsers to see the changes made.

Best Practices

Always preview before saving changes.
Keep naming consistent for easier reporting.
Maintain a backup list of values before bulk updates.
Coordinate with your team to avoid overlapping edits.

Manage Custom Fields in Ironsight

The Manage Custom Fields permission lets you update lists and options on the custom fields in Ironsight workflows, like adding new information. These changes affect active jobs and reports, it’s only given to trained users who know how to make updates safely without disrupting data or operations.

When to Use Schema Builder

Editing an Activity’s Custom Fields: Add, update, or archive dropdown options and other custom field values.

Creating a New Activity With Custom Fields: Create the Activity first without custom fields, then return to edit it in Schema Builder.

Key Risks & Rules

DO NOT delete fields – This can break dashboards and cause historical job data to disappear from analytics.

If a field is no longer needed:

Mark it as “Do Not Use” or “Archive” instead of deleting.

Contact a Ironsight if permanent removal is required.

Avoid unnecessary schema changes during active work hours to minimize disruption.

Step-by-Step: Updating Custom Fields

Log in to Ironsight and ensure your account has the Manage Custom Fields permission.

Go to the Admin Portal.

Navigate to:

Services (in Admin Portal) → Select the relevant service/activity (e.g., Drill).

Note: In Dispatch Hub, “Activity” is the term used; in the Admin Portal, it’s called “Service.”

Click “Edit in Schema Builder”.

In Schema Builder:

Close the preview panel if it opens.

Locate the field you want to update in the middle column (e.g., Pig Serial Number).

To Add Options:

Click the field.

Add items one-by-one with the Add Option button, or

Use bulk paste from Excel, Word, or any text list (ensure consistent formatting).

To Remove Options:

Do not delete directly.

Instead, label as “Do Not Use” or Contact Ironsight to “Archive" or Delete Parmanently.

Save Changes:

After editing, open the preview to verify the update.

If correct, click Save to apply the change to all jobs using this schema.

Impact on Active Jobs

New values will appear immediately in forms and dropdowns for new jobs.

For active (uncompleted) jobs:

Updated options will be available when the job form is reloaded.

Users are required to refresh their browsers to see the changes made.

Best Practices

Always preview before saving changes.

Keep naming consistent for easier reporting.

Maintain a backup list of values before bulk updates.

Coordinate with your team to avoid overlapping edits.