Apply a Tag

Once a Tag is created, it's ready to be associated with a Datastore, Profile, Check, Notification and ultimately an Anomaly.

When a Tag is applied to a data asset, the asset itself is updated immediately, in the same request. The Tag then propagates to that asset's descendants in the background; you may need to refresh a child view to see the tag if you jump to it right after the parent update.
- For example, if a Tag named Critical is applied to a Datastore, the Datastore reflects the tag right away and all the Tables, Fields, and Checks under it pick up the tag as the background cascade reaches them.
Note

Anomalies will inherit the tags if a scan has been run.
Likewise, if the Critical Tag is subsequently removed from one of the Tables in that Datastore, the Table loses the tag in the same request and its Fields and Checks lose the tag as the background propagation completes.
When a new data asset is created, it inherits the Tags from the owning data asset. For example, if a user creates a new Computed Table, it inherits all the Tags that are applied to the Datastore in which it is created.

Anomalies also inherit Tags at the time they are created. They inherit all the Tags of all the associated failed checks.
Thus Anomalies do not inherit subsequent tag changes from those checks. They only inherit tags one time - at creation time.
Tags can be directly applied to or removed from Anomalies at any time after creation.