In Business 360 Console you can purge code values of code lists along with the crosswalks, relationships, and hierarchies.
When you purge data, you permanently delete data from Reference 360 without deleting data models and other configuration details of your organization. You can only purge assets that weren't created in Business 360 Console.
You can purge data in the development, QA, and production environments. When you purge reference data, a purge job is automatically created and triggered.
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 are complete.
•You must be a Reference 360 Administrator with necessary privileges.
To purge code values of code lists, configure the Administrator and MDM Configuration service privileges for the Reference 360 Administrator user role with only Reference 360 access.
1In Administrator, click User Roles.
2Click Reference 360 Administrator.
3In the Services field, select Administrator.
4On the Assets tab, enable the Read privilege for the Organization asset type.
5In the Services field, select MDM Configuration.
6On 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.
Small volume data purge
When you purge up to 1,000 code values or deleted source records, the purge job runs immediately without queuing.
Large volume data purge
You can purge up to 1 million code values at a time. To purge larger volumes, run the purge job multiple times.
You can purge up to 10 million deleted code values. To ensure proper scheduling and resource allocation for purging volumes exceeding 1 million records, contact Informatica Global Customer Support.
For information about viewing the number of code values and source records in your organization, see Monitor MDM SaaS.
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 specific code list along with their dependencies.
1Click Global Settings > Purge Data.
2Click Start.
3To permanently delete code values in a code list along with their dependencies, in 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 a specific code list along with their dependencies.
- Purge deleted source records. Permanently deletes only the deleted code values of the specified code list along with their dependencies.
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 Monitor Jobs.