Prerequisites to delete data enrichment assets created before the April 2025 release
You can't delete, data enrichment assets, such as data enhancement rules, rule associations, and objectives groups, created before the April 2025 release. By default, these assets aren't enabled with the delete permission. You can't delete these assets without enabling the delete permission for them.
Use the Aces API to enable the delete permission for each asset that was created before the April 2025 release.
To enable the permission, perform the following tasks:
1Get the artifact ID of the asset for which you want to enable the permission.
2Generate a session ID.
3Get the organization ID and the access control list ID for the asset.
4Enable the delete permission.
Step 1: Get the artifact ID of an asset
An artifact ID is a unique identifier of an asset. You can get the artifact ID of an asset from Business 360 Console.
1In Business 360 Console, open the asset for which you want to enable the delete permission.
2Copy the artifact ID from the URL of the asset in the browser.
The following image shows a rule association named Enrich Person Data:
Step 2: Generate a session ID
To generate a session ID, use the Login API and submit a POST request.
Step 3: Get the organization ID and the access control list ID
The organization ID is a unique identifier for the organization that contains the asset that you want to delete. The access control list ID uniquely identifies the list of permissions enabled for the asset. To get the organization ID and the access control list ID, use the GetACL API and submit a GET request.
You can use the following sample GetACL request:
GET <base URL>/frs/api/v1/GetACL(artifactId='<The artifact ID from Step 1>') Content-Type: application/json IDS-SESSION-ID: <The session ID from Step 2>
After you submit the GetACL request, you receive a response similar to the following sample response:
The sample response returns 9yrF0GmWoAPhVItLyKiPER as the access control list ID in the id parameter.
The idsInfo > id parameter contains the organization ID as iQMC7WqF4CggJn9PZVozC5.
Note: The value parameter in the response might contain multiple entries. From these entries, find the entry where the idsInfo > type parameter value is ORG and use the value of the id parameter from that entry.
Step 4: Enable the delete permission
To enable the delete permission for an asset, use the Aces API and submit a PUT request with the access control list ID, artifact ID, and organization ID.
When you submit an Aces API request, ensure that the delete parameter in the request body is set to true.
You can use the following sample Aces API request to enable the delete permission of an asset:
PUT <base URL>/frs/api/v1/Aces('<The access control list ID from Step 3>') Content-Type: application/json IDS-SESSION-ID: <The session ID from Step 2> { "id": "<The access control list ID from Step 3>", "artifactId": "<The artifact ID from Step 1>", "idsInfo": { "id": "<The organization ID from Step 3>", "type": "ORG" }, "permission": { "create": null, "read": true, "update": true, "delete": true, "execute": false, "changePermission": true } }
After you submit a successful Aces API request, you can select the asset on the Explore page in Business 360 Console and delete the asset.