Skip to content

Merge Tags

DC Merging a tag into another tag

Merging moves everything that uses a tag to another tag and then deletes the first one. Use it to clean up duplicate tags, such as PII and Personal-Data, so that one tag remains.

Related

Permission Required

Only Admins can merge tags. External tags cannot be merged, and a tag cannot be merged into an external tag.

What Can Stop a Merge

Situation What you see
You are not an Admin, or the Data Catalog module is off Merge is not offered.
The tag is an external tag Merge is not offered, and external tags are not listed as targets.
Work that uses the tag is queued or running, such as a scan or another operation picked by the tag, or a run of a Flow that uses it The review lists that work with the reason Merge is refused while queued or running work references the source tag, and Merge stays off. Try again once it finishes.
You merge into a team tag and some of the tag's uses fall outside that team's datastores The review lists each one with its reason, and Merge stays off. See Merging Into a Team Tag.

Merging Into a Team Tag

A team tag only goes on its team's datastores, so merging into one is refused when anything that uses the tag would land outside them:

  • An asset that carries the tag, archived ones and the assets inside tagged tables included, sits in a datastore the team can't access.
  • A check template carries the tag. Templates belong to no datastore, so they can't take a team tag.
  • An impact metric limit that adds the tag sits on a check outside the team's datastores.
  • A Flow action that adds the tag doesn't filter on the team's datastores.
  • A queued or running promotion that adds the tag promotes into a datastore outside the team's.

Fix or remove those uses first, or merge into a global tag instead.

Before You Merge

The Merge Tag dialog explains what happens when you merge:

What Happens Description
Everything Moves Assets, Flows, and filters that use the tag switch to the tag you merge it into.
The Tag Is Deleted Its history and comments go with it.

Schedules that pick tables by the tag switch too. Assets that already carry both tags keep only the remaining one. The remaining tag keeps its own name, color, category, and weight, and records the merge in its timeline. The switched assets now count with its weight: table and field weights are recalculated and the datastore's quality score is refreshed right away, a table's own score changes from its next scan, and the importance of the affected checks, and the impact of their open anomalies, update on their own.

This action cannot be undone

To move only some assets and keep both tags, use Move a Tag to Another Tag instead.

Steps

Step 1: Open the tag's page by clicking the tag in the Tags list.

Step 2: Click the settings menu at the top of the page, then click Merge . The Merge Tag dialog opens.

Step 3: Under Choose, pick the tag that takes its place in the Tag field. The dialog explains what happens: everything moves to that tag, and the tag you are merging is deleted. Click Next.

Step 4: Under Review, check the assets that switch to the new tag, grouped by type. When the tag is not on any asset, the review says so, and merging only deletes it and records the merge.

Step 5: Click Merge. The dialog confirms that the tag was merged and deleted. Click View tag to open the page of the tag that remains.

Step 1: Open the tag's page by clicking the tag in the Tags list.

Step 2: Press Cmd+KCtrl+K and select Merge.... The Merge Tag dialog opens.

Step 3: Under Choose, pick the tag that takes its place in the Tag field. The dialog explains what happens: everything moves to that tag, and the tag you are merging is deleted. Click Next.

Step 4: Under Review, check the assets that switch to the new tag, grouped by type. When the tag is not on any asset, the review says so, and merging only deletes it and records the merge.

Step 5: Click Merge. The dialog confirms that the tag was merged and deleted. Click View tag to open the page of the tag that remains.