A plain-language guide to how the Asset Database handles deactivated dropdown options

Why this article exists

In the Asset Database, many fields use dropdown lists — things like Unit of Measurement (UOM), Brand, Category, Group, Segment, Asset Allocation, and Asset Ownership. The options inside those dropdowns are managed centrally, not by individual users.

That means an option you’ve already used to tag an asset can later be removed from the master list — for example, when the business retires an old brand, consolidates categories, or cleans up legacy data.

When that happens, a fair question comes up: what happens to all the assets that were already using that option?

This article answers that question across every place in the module where it matters: the asset list, the edit page, the global filter, the activity log, and bulk edits in progress.

The core principle

The system follows one simple rule:

Don’t lose history. Don’t allow new mistakes.

In practice, this means:

• Existing data stays visible. If an asset was tagged with a label that has since been removed, the asset keeps showing that label so you can still recognize and audit the record.
• New selections use the current list. The moment anyone tries to change that field, the removed option disappears — you can only pick from options that are currently active.

Everything below is a consequence of that one rule.

What you’ll see in each part of the module

On the Asset List page

The asset still shows the removed label exactly as it was saved. Nothing about the row changes just because the master list changed.

This is intentional. If a brand called “Acme” is removed from the master list, every asset that used to be tagged “Acme” still says “Acme” on the list. You wouldn’t want those assets to suddenly show a blank field — it would make them impossible to recognize, and the historical record would be lost.

When you open the Edit page

When you open an asset whose data includes a removed option, the field shows the removed value as the current value. You can see clearly what was set, and nothing has been silently overwritten.

The moment you open that field’s dropdown to change it, the removed option is no longer in the list. You can only pick from options that are currently active.

If you don’t touch that field, the removed value stays saved on the record. Editing other fields and saving doesn’t force you to update this one — your edit is scoped to what you actually changed.

When you click Save

Before saving, the system checks every value on the form against the current master list. If any of the values you’re trying to save are no longer valid, the save is blocked and the affected field is highlighted so you can fix it.

This is the system’s safety net: it prevents anyone from saving a record that contains an option that was removed during the editing session.

In the Global Filter

Removed options don’t appear in the Global Filter’s selection list. You can’t build a new filter condition that targets a removed label — the option simply isn’t there to pick.

Existing assets that hold the removed value are still visible on the Asset List. You just can’t isolate them using that label as a filter criterion going forward.

In the Activity Log

When an option is removed from the master list, that change is recorded in the database for audit purposes — but it doesn’t show up as an entry in any individual asset’s Activity Log.

Why? Because the asset itself didn’t change. The master list changed. The asset still holds the same value it was given. Cluttering every asset’s history with an event that wasn’t about that asset would make the log harder to read.

If a config change happens while someone is mid-edit

This is the trickiest scenario. Imagine a user opens an asset’s Edit page, starts making changes, and in parallel an admin removes one of the options from the master list before the user clicks Save.

The system handles this gracefully: it uses a snapshot of the attributes and labels taken when the Edit page was opened. The user can finish their work and save, validated against that snapshot. They won’t be blocked mid-task by a change made elsewhere.

Bulk Edits

The same rule applies to bulk imports. If a CSV file contains a removed option, those rows fail back-end validation and appear in the Failed Data sheet of the result file, with the specific reason listed. Rows that don’t touch the affected field go through normally.

Quick reference table

What this means for you

For business and operations teams: You don’t need to worry about historical records being silently wiped. Anything that was tagged in the past stays tagged — until someone deliberately updates it.

For admins managing the master list: Removing an option is safe in the sense that it won’t corrupt existing data, but it does mean those options can no longer be used as filter criteria or applied to new records. Plan removals around reporting cycles where possible.

For users doing day-to-day edits: If you open an asset and see a value that’s no longer in the dropdown when you click into it, that’s expected. Either leave it as-is or pick a current option to replace it.

End of article. Return to “Understanding the Asset Database” for an overview of the module, or continue to “How to View and Edit an Asset” for the standard edit flow.

Once the upload is successful, the updated mappings are immediately stored and visible in the system, while every change is automatically recorded in the asset mapping log. This includes the actor, timestamp with timezone, the previous state, and the new state after the bulk edit. This feature ensures efficiency, transparency, and a reliable audit trail when managing asset assignments at scale.

The Bulk Edit Asset feature saves your team significant time and effort by allowing you to edit and update multiple assets in a single process, with built-in validation to protect the accuracy of your data. By preparing your template carefully and understanding how the validation process works, you can ensure a smooth and reliable bulk creation experience within Staffinc Suite.

The Bulk Create Asset feature saves your team significant time and effort by allowing you to register multiple assets in a single process, with built-in validation to protect the accuracy of your data. By preparing your template carefully and understanding how the validation process works, you can ensure a smooth and reliable bulk creation experience within Staffinc Suite.

The Asset Activity Log is your organization's built-in audit trail for asset data, ensuring that every update is recorded accurately and can be reviewed at any time. By understanding how to read the activity log, you give yourself and your team the transparency needed to manage assets with confidence, accountability, and full historical context within Staffinc Suite.

With the search and filter tools available in the Asset List, managing a growing inventory of assets becomes far more manageable. Whether you are looking up a specific asset by name or ID, or reviewing which assets are still active versus discontinued, these tools help you stay in control of your asset data and keep your operations running smoothly within Staffinc Suite.

Keeping your asset records accurate and up to date ensures that your organization always has a reliable and transparent view of every asset in the system. By using the edit and status update features thoughtfully, you can maintain a complete operational history without losing important data, giving your team the clarity it needs to manage assets confidently in Staffinc Suite.

Creating an asset with complete and accurate information ensures that it is ready to be used, allocated, and tracked across your organization from day one. By taking the time to fill in each configuration field carefully, you set a strong foundation for reliable asset management and employee performance tracking within Staffinc Suite.

The Asset Database is more than a product catalog — it is a flexible operational tool designed to reflect the full scope of how your organization manages its assets. By understanding its purpose and structure, you will be better equipped to use the Asset Management module in a way that truly supports your business operations within Staffinc Suite.

Deleting a channel that has employees assigned to it is a permanent action that cannot be undone. Before proceeding, make sure you have a plan to reassign affected employees to a new Visitation Policy so their access and mobile activities are not left interrupted. Taking a moment to review the impact beforehand will help you manage the process smoothly and avoid any unintended disruption to your operations.

Once the deletion is complete, the channel will no longer appear in your channel list and will be permanently removed from Staffinc Suite. Since this action cannot be undone, ensure that no active employees or ongoing operations are still dependent on the channel before you proceed.

Having clear visibility into channel-to-employee assignments directly within Staffinc Suite helps you stay in control of your operational structure — ensuring every channel is staffed correctly and that your workforce data remains accurate and easy to verify at any time.

By using the bulk assignment feature, you can connect employees to their respective channels quickly and at scale — eliminating manual effort and ensuring your workforce structure in Staffinc Suite stays accurate and up to date.

With the ability to stack up to 5 filter conditions at once, the advanced filter builder in the Channels module helps you cut through complexity and surface exactly the channels you're looking for — making channel management faster, more precise, and far less time-consuming.

With the search and filter tools in the Channels module, managing a large number of channels becomes much more manageable — helping you stay organized and find the right information without unnecessary effort.