> 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-v48-to-v260.md).
# Upgrade from v4.8 to v26.0
{% hint style="info" %}
**Mandatory for all v26.0 upgrades**
YouDesign Command v26.0 introduces a structured, multi-phase alignment of the application's data model with the new **Portfolio Element** architecture. Earlier versions stored a set of custom fields directly on ServiceNow CMDB tables; v26.0 consolidates that logic onto the governed Portfolio Element superclass. Because ServiceNow application upgrades intentionally never remove existing fields, this step is delivered as **Post-Upgrade Update Sets** that you apply after installing v26.0.
Please read this page in full before committing any Update Set.
{% endhint %}
## Why we're doing this
As YouDesign Command (formerly UPMX) evolves, we're committed to keeping our solution fast, modern, and aligned with the latest ServiceNow platform standards — and with what our customers actually need going forward.
Part of that commitment is moving the fields these earlier versions added to the CMDB onto the new Portfolio Element architecture. Completing this step:
* Streamlines your instance by consolidating the business rules and scheduled jobs that maintained these fields
* Keeps `cmdb_ci_business_app`, `cmdb_ci_business_capability`, `cmdb_ci_business_process`, and `cmdb_ci_information_object` aligned with the standard ServiceNow model
* Prepares your instance for the new capabilities introduced in v26.0 — Future State Repository, Scenario Planning, Enterprise Measures, and next-generation Data Governance & Data Quality — and for what's coming next
This is the **first of several alignment phases**. v26.0 covers the batch below; v26.1 and v26.2 will continue the same effort, moving the remaining fields onto the Portfolio Element architecture.
{% hint style="info" %}
This page assumes you've already updated to v26.0. If you haven't yet, see [Updating](/command/get-the-app/updating.md) first.
{% endhint %}
Upgrading to v26.0 on its own does not delete your legacy fields but business rules, and scheduled jobs are updated considering that the legacy fields will be deleted with following cleanup, and no customer data is deleted by the app upgrade itself. Whether anything actually changes is entirely up to you, through the two Update Sets below — that's why we encourage everyone to follow through with the complete cleanup.
## Choose how to handle legacy CMDB fields
Once the application upgrade finishes, decide — together with your team — whether you're ready to complete the cleanup now, or would rather keep the legacy fields active for a while longer. Both paths are fully supported; **you are not required to clean up immediately.**
| | Path A — Complete the Cleanup | Path B — Preserve Legacy Logic |
| ---------------- | ---------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| **Best for** | Customers ready to fully retire the legacy fields | Customers who still rely on the legacy fields and need more time |
| **What it does** | Permanently deletes the 8 legacy fields (and their labels), and deactivates 3 scheduled jobs that depend on them | Explicitly locks in the legacy business rules and scheduled jobs as active, so the fields keep populating |
| **Reversible?** | No — this is a permanent deletion | Yes — you can switch to Path A whenever you're ready |
### Path A: Complete the Cleanup (Recommended)
{% hint style="danger" %}
**This is a permanent deletion.** Do not proceed if any reports, integrations, or custom scripts outside of YouDesign Command still reference the fields listed below. Contact our [support portal](https://www.ins-pi.com/support/) first if you're unsure, and always test in a sub-production instance before applying to production.
{% endhint %}
1. Download the **YCM V26.0 CMDB Custom Fields Cleanup** Update Set XML:
{% file src="/files/3kUALeTbwuCNwOo7O5wQ" %}
1. Go to **Retrieved Update Sets** in ServiceNow.
2. Click **Import Update Set from XML** under the related links.
3. Select the downloaded file and upload it.
4. Click **Preview Update Set**.
5. Accept all warnings and errors, then click **Commit Update Set**.
Committing this Update Set deletes the 8 legacy fields (17 field-on-table instances) and their field labels:
Fields removed by the Cleanup Update Set — 8 fields, 17 field-on-table instances
| Field | Tables |
| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| `x_inpgh_upmx_data_model` | cmdb\_ci\_information\_object |
| `x_inpgh_upmx_relationships` | cmdb\_ci\_business\_app, cmdb\_ci\_business\_capability |
| `x_inpgh_upmx_relationships_to_business_application` | cmdb\_ci\_information\_object, cmdb\_ci\_business\_process, cmdb\_ci\_business\_capability, cmdb\_ci\_business\_app |
| `x_inpgh_upmx_relationships_to_business_capabilities` | cmdb\_ci\_information\_object, cmdb\_ci\_business\_process, cmdb\_ci\_business\_capability, cmdb\_ci\_business\_app |
| `x_inpgh_upmx_relationships_to_processes` | cmdb\_ci\_information\_object, cmdb\_ci\_business\_capability, cmdb\_ci\_business\_app |
| `x_inpgh_upmx_stakeholder_rating` | cmdb\_ci\_business\_app |
| `x_inpgh_upmx_stratification` | cmdb\_ci\_business\_capability |
| `x_inpgh_upmx_users` | cmdb\_ci\_business\_app |
{% hint style="info" %}
Three of the eight fields — `x_inpgh_upmx_data_model`, `x_inpgh_upmx_stratification`, and `x_inpgh_upmx_users` — had no dependent business rules of their own. If your instance has custom ACLs, UI policies/actions, form or list layouts, or dictionary entries referencing any of the 8 fields above, review and remove those separately — they are not included in either Update Set.
{% endhint %}
{% hint style="warning" %}
**One manual step required after commit**
Committing the Update Set automatically **deactivates** 3 scheduled jobs that depend on the deleted fields, but does not delete them. To finish the cleanup, manually delete these three scheduled jobs:
* `YCM CAL Number of Relationships for Information Object`
* `YCM CAL Number of Relationships for BC`
* `YCM CAL Number of Relationships for BA`
{% endhint %}
### Path B: Preserve Legacy Logic (Opt-In)
Choose this path only if you've decided to keep the legacy fields and the logic behind them for now.
{% hint style="info" %}
Upgrading to v26.0 on its own does not delete your legacy fields but business rules, and scheduled jobs are updated. Committing it explicitly locks that logic and preserve the legacy scipts, so it's documented and protected against later alignment phases (v26.1, v26.2) instead of being removed by accident.
{% endhint %}
1. Download the **YCM V26.0 Pre-Cleanup Legacy Logic Preservation** Update Set XML:
{% file src="/files/y2Tpx43vCBAd3ieoYspl" %}
1. Go to **Retrieved Update Sets** in ServiceNow.
2. Click **Import Update Set from XML** under the related links.
3. Select the downloaded file and upload it.
4. Click **Preview Update Set**.
5. Accept all warnings and errors, then click **Commit Update Set**.
Committing this Update Set explicitly locks that logic and preserve the legacy scipts, so the legacy fields keep populating:
Business rules & scheduled jobs locked in by the Preservation Update Set — 14
**Business rules (9)**
* `D: Calculate Child/Parent #Relationships`
* `IU: REL Calculate child #Relationships`
* `IU: REL Calculate parent #Relationships`
* `D: Calculate #Relationships`
* `IU: Calc #Relationships (Child Chg)`
* `IU: Calc #Relationships (Parent Chg)`
* `IUD: Update StakeHolder rating`
* `U: Update StakeHolder rating`
* `U: Update Stakeholder Rating`
**Scheduled jobs (5)**
* `YCM CAL Set #Relationships`
* `YCM CAL Set Stakeholder Rating`
* `YCM CAL Number of Relationships for BA`
* `YCM CAL Number of Relationships for BC`
* `YCM CAL Number of Relationships for Information Object`
There's no deadline to switch. When you're ready to retire the legacy fields, come back to this page and follow **Path A**. Later alignment phases (v26.1, v26.2) will continue in the same spirit, so we recommend revisiting this decision periodically.
## Looking ahead
This alignment continues in **v26.1** and **v26.2**, working toward the same goal: a YouDesign Command data model fully consolidated onto the Portfolio Element architecture. We'll publish an updated version of this page for each phase.
If you face any issues, please contact us through our [support portal](https://www.ins-pi.com/support/).
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ins-pi.com/command/get-the-app/upgrade-v48-to-v260.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.