Inside Activate
Development
Backfill Common Properties Data
4 min
common properties are shared attributes applied to services and assets in activate they are evaluated and populated automatically based on object state and configuration this document explains how common properties are updated and how to backfill them for existing objects when required how common properties are updated for services and assets, common properties are updated when setinfo() is called and one of the following conditions is met the object is being inserted for the first time the object data has changed since the last update if neither condition is met, common properties are not recalculated backfilling common properties in some scenarios, common properties may be missing for existing service or asset instances this typically occurs when common properties were introduced or modified after the objects were originally created to backfill common properties, the object must be treated as changed before calling setinfo() triggering a data change a data change can be triggered by performing a dummy update this is a non functional change that ensures the object meets the data changed condition required for common properties to be recalculated a common approach is to set a transient or placeholder value, such as a newly generated guid, on the object before saving it bulk backfill approach to backfill common properties across multiple objects retrieve the required service or asset instances apply a dummy update to each instance call setinfo() to persist the change and recalculate common properties this process must be applied to all objects that require backfilled values scope and impact considerations when performing bulk backfills limit the scope to only objects that require updates test the approach in a non production environment first be aware of the processing load when updating large numbers of objects the same behaviour applies to both service instances and asset instances