Asset data should flow smoothly between on‑prem and Cloud. When it does not, confusion grows. One common problem is asset types that refuse to update in Cloud, even though they look correct on‑prem. This quick tip explains why this happens and how you can fix it in minutes.
What is going on
You may see assets in Cloud stuck with old or incorrect asset types. You check your on‑prem installation and see the right values. Yet Cloud keeps showing something different. This mismatch can disrupt reports and weaken your visibility. The root of the issue often hides in the Cloud asset edit screen. There, the Asset Type field may appear locked. When locked, Cloud ignores any updated asset type received from the on‑prem sync.
A locked field in Cloud acts as a safeguard against unwanted overwrite. It tells the platform to protect that value from incoming changes. This is useful when you want Cloud‑only customization. But when locked by accident, it blocks the sync pipeline. On‑prem sends the correct asset type, but Cloud discards it. The result is a stubborn, outdated asset type that never refreshes.
How can I fix this
You can fix the issue by unlocking the Asset Type field. The process is simple:
- Open your Cloud site and browse to the affected asset.
- Select Edit to open the asset’s editable fields.
- Find the Asset Type field. If it shows a lock icon or the locked toggle is enabled, uncheck it.
- Save your changes.
- Wait for the next scheduled sync from on‑prem.
Once unlocked, Cloud will accept the incoming asset type from your on‑prem installation. After the sync completes, both environments will display the same, accurate asset type. This restores consistent classification and clean reporting across your estate.
This quick fix prevents silent data drift and keeps your environment aligned. Unlock the field, let the sync run, and enjoy a tidy, unified asset view.
