AEP: merge policy for profile snapshot export
This article explains how to identify merge policies attached to profile snapshot export datasets in Adobe Experience Platform (AEP). By following the steps mentioned in the article, you can efficiently manage your datasets and associated merge policies.
Description description
Environment
- Adobe Experience Platform
- There is not a specific impacted AEP version. This article concentrates on the API parameter.
Issue/Symptoms
When attempting to identify the merge policy attached to a profile snapshot export dataset, two issues can arise:
- The command used only returns 20 datasets while more exist in the environment.
- The description for system-generated datasets does not save input changes even though it appears successful in the UI.
Resolution resolution
To resolve these issues, follow these steps.
-
Retrieve all datasets using pagination:
-
Use pagination options with your API call to retrieve all datasets.
-
Example API Call:
GET https://platform.adobe.io/data/foundation/catalog/dataSets?start=0&limit=100
-
This ensures you get all available datasets within your environment. This command is executed through the Developer API (specifically the Catalog API) using an API client like POSTMAN. Note: The maximum number of objects that can be returned is 100.
-
-
Identify merge policy:
- Once you have retrieved the list of datasets using the Catalog Service API, filter them using keywords such as profile-snapshot-export to locate the correct dataset.
- Under Tags/unifiedProfile you see mergePolicyID:
[
xxx]
Editing descriptions on system-generated datasets
- Note that descriptions for system-generated datasets cannot be modified through the UI or API despite appearing editable.
By following these steps, you can identify and manage merge policies attached to profile snapshot export datasets within AEP.