In Business 360 Console, you can purge code values of code lists along with their relationships and historical data.
When you purge data, you permanently delete data from Reference 360 without deleting data models and other configuration details of your organization. You can purge code values of custom code lists that aren't picklist values of business entities in business applications, such as Customer 360 SaaS.
You can purge data in the development, QA, and production environments. When you purge data, a purge job is automatically created and triggered.
Note: Before you purge code values of code lists in production environments, analyse the data you want to purge. You can't recover the purged data.
For more information about purging data, see Purging data.
Rules and guidelines for purging code values
Before you purge data, consider the following rules and guidelines to prevent data issues:
•No users have logged in to the business applications.
•No jobs are running.
•All workflow tasks related to the code list that you want to purge are complete.
•You can purge code values of custom code lists that aren't picklist values of business entities in business applications, such as Customer 360 SaaS.
•Review all assets that depend on the code list you are about to purge and assess their impact.
•If you have only the SaaS Edition - Reference 360 license, you must configure purge privileges for the Reference 360 Administrator user role to purge code values.
•If you have the SaaS Edition - Reference 360 license along with any MDM SaaS business application edition license, the Reference 360 Administrator user role can't purge code values but the organization Administrator user role can.
•If you have only the SaaS Edition - Reference 360 license and have configured purge privileges for the Reference 360 Administrator user role, you need to use Business 360 Console to purge reference data assets. Ensure you don't perform any other operations in Business 360 Console.
Configuring privileges to purge code values
If you have only the SaaS Edition - Reference 360 license, you must configure purge privileges for the Reference 360 Administrator user role to access Business 360 Console and purge code values.
1In Administrator, click User Roles.
2Click Reference 360 Administrator.
3In the Services field, select MDM Configuration.
4On the Features tab, enable the Configuration and Authoring, Execute Business 360 Flows, and Manage Job Instances features.
Performance considerations for purging code values
The performance of data purge depends on the data set, data volume, and POD-level limits.
To optimize performance of data purge, consider the aspects of data, such as volume and complexity, and purging limits.
Complexity of the data set
The performance of purge jobs depends on the size and complexity of your data set, such as the number of relationships and historical data.
Concurrency limits at the POD level
MDM SaaS limits the number of concurrent purge jobs that can run on a POD. As a result, your purge job might be queued if multiple jobs run concurrently on a POD.
Purging code values
You can purge code values that belong to a code list along with their relationships and historical data.
1In Business 360 Console, click Global Settings > Purge Data.
2Click Start.
3In the Purge Data dialog box, select Purge records.
4Select a code list.
5Select one of the following options for code values to purge:
- Purge all records. Permanently deletes all the code values, that belong to the selected code list along with their relationships and historical data.
- Purge deleted source records. Permanently deletes only the deleted code values of the selected code list along with their relationships and historical data.
6Click Next.
7Enter your organization ID, and click Submit.
You can monitor the status of the job on the My Jobs page. For more information about monitoring jobs, see Monitoring jobs.