> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-c-retire-some-features/data-governance.md).

# Retire legacy Data Governance

Retire the legacy Data Quality feature after upgrading to YouDesign Command v26.1, without losing attestation dates.

Retires the legacy Data Quality implementation. The new [Data Governance](https://docs.ins-pi.com/command/features/data-governance.md) replaces it. Follow [Upgrade from v26.0 to v26.1](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261.md) first.

{% hint style="danger" %}
**Migrate first.** The cleanup set drops the legacy data quality tables. The migration carries over the attestation dates, which nothing in Command can rediscover: without them every data owner has to re-validate from the start.
{% endhint %}

## Steps

### 1. Back up the legacy tables

The cleanup set drops these tables with every record in them. Export them to XML before you migrate, so the records can be put back if anything goes wrong.

| Table                           | Name                                         |
| ------------------------------- | -------------------------------------------- |
| **Data Quality**                | `x_inpgh_upmx_data_quality`                  |
| **Scoped Fields**               | `x_inpgh_upmx_data_definition`               |
| **Data Definition Scope**       | `x_inpgh_upmx_data_definition_scope`         |
| **Command m2m Data Definition** | `x_inpgh_upmx_m2m_data_definit_data_definit` |

For each one:

1. Open `https://<instance>.service-now.com/<name>_list.do`, with the name from the table above.
2. Right-click any column heading and choose **Export > XML**.
3. Save the file somewhere outside the instance.

If a list holds more records than your instance exports at once, filter it into parts, for example by **Created**, and export each part.

To put the records back, back out the cleanup set so the tables return, then on each table's list right-click a column heading, choose **Import XML** and select its file.

### 2. Migrate the data

1. In Command, click **Open menu** (☰), expand **Migration** and choose **Data Governance**.
2. Click **Migrate** on **Charters and rules** and wait for 100%.
3. Click **Carry verifications** on **Verifications** and wait for 100%.
4. Optional: to see the Command data quality view on forms before the cleanup, click **Switch to Command** on **Forms show Command**. **Revert to legacy** switches forms back.

Both buttons then read **Re-check**. The person who made each verification is not carried, but its date is, so an expired verification arrives overdue. Reminder settings are not carried either: set them up again in Data Governance settings.

**Forms show Command** sets the global setting `dq.form_visualization.use_command` (`true` shows the Command view, `false` the legacy one). The setting only works until the cleanup: once the legacy data quality tables are gone, forms always show the Command view.

### 3. Commit the update set

**First, check Logic Preservation.** In **Retrieved Update Sets**, look for **YCM V26.1 Legacy Logic Preservation** with the state **Committed**.

If it is already committed, for example because you retired another feature first, do not commit it again. Committing it again turns the shared Lifecycles and Measures calculation jobs back on, even ones you deleted by hand. If it is not there, or not yet committed, commit it now:

{% file src="/files/r5th8lgCHZ3rAU8Ldbom" %}

The cleanup set deletes the legacy `x_inpgh_upmx.dq_admin` role. Before you commit it, give everyone who holds that role **Command Editor** (`x_inpgh_upmx.editor`) and a persona that opens **Data Governance** on its **Admin Settings** tab. See [Personas](https://docs.ins-pi.com/command/the-portal/personas.md#admin-settings) and [Roles the cleanup removes](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261.md#roles-the-cleanup-removes).

Then commit **YCM V26.1 Legacy Data Governance Cleanup**. Skip this set if you are using **Full Cleanup**.

{% file src="/files/03UVMZx55BarSSXcocKT" %}

The set keeps the **UPMX Data Quality** form widget: the `UPMXDataQuality` UI macro, its UI formatter and the **Data Quality** form sections that place it. From the cleanup on, that widget shows the Command data quality view.

The preview reports one error, on `analytics_category_m2m_3552b41071a93ed9ffc4943a3e2baecf`. Skip that entry and commit the rest: the record belongs to the global scope, which this set cannot change. One harmless category link stays behind.

### 4. Delete 12 scheduled jobs

The set switches these jobs off but cannot delete them. In **System Definition > Scheduled Jobs**, delete each one:

<details>

<summary><strong>The 12 Data Quality jobs</strong></summary>

* `PERIODIC: YCM DQ Create Data Quality from Recently Created Scoped Fields`
* `PERIODIC: YCM DQ Update Data Quality for Recently Created/Updated CIs`
* `PERIODIC: YCM DQ Update Data Quality When Scope Changes`
* `ON DEMAND: YCM DQ Add Missing Data in Data Definition Scope Table`
* `ON DEMAND: YCM DQ Create Data Quality from All Scoped Fields`
* `ON DEMAND: YCM DQ Fill Table Reference Field in Data Quality`
* `ON DEMAND: YCM DQ Remove Complete Data Quality Configuration`
* `ON DEMAND: YCM DQ Set Average Data Quality`
* `ON DEMAND: YCM DQ Set Verification History on Data Quality from Data Verification Table`
* `IGNORE: YCM DQ Create Data Quality for CIs Created in Last 15 Minutes`
* `YCM DQ Notify Currentness and Completeness Info to Steward/Steward Group`
* `YCM DQ Set Data Currentness on Data Quality Table`

</details>

### 5. Delete one global setting

Delete `dq.fields.allowed.verification` from the YouDesign Command global settings (`x_inpgh_upmx_global_settings`).

### 6. Remove the Data Governance tab from Admin Settings

The **Admin Settings** page of the **YouDesign Command (UPMX)** experience still has a **Data Governance** tab for the legacy feature. The update set leaves the page alone, so it works whichever features you keep.

1. In the filter navigator, open **UI Builder**.
2. Open the **Experiences** tab.
3. Search for **YouDesign Command (UPMX)** and open it.
4. Expand **Admin Settings** and click **Default**.
5. In the content tree, select the **Data Governance** tab.
6. In the right panel, click **Tabs**, then **Go to Tabs**.
7. Click the settings icon on the **Data Governance** tab, then click **Delete**.
8. Click **Save**.

## Check it worked

* The **Data Quality** module is gone from the **YouDesign Command (UPMX)** menu.
* The **Admin Settings** page of the **YouDesign Command (UPMX)** experience has no **Data Governance** tab.
* No `YCM DQ` job is left in **Scheduled Jobs**.
* Forms with a **Data Quality** section show the Command data quality view.
* Relationship counts and business value still recalculate when you change a record.

## Related

* [Upgrade from v26.0 to v26.1](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261.md)
* [Data Governance](https://docs.ins-pi.com/command/features/data-governance.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-c-retire-some-features/data-governance.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
