Data 360: Data Model Field Mappings - Dependencies Errors

Steps to Remove DMO Mappings:

1. Initiate Removal:
- Navigate to the data mapping review page.
- Click on the “Remove Mappings” icon.

2. Identify Fundamental Dependencies:
- The system will display dependencies related to:
- Identity Resolution
- Segments
- Data Lake Objects
- Activation
- Data Shares
- Flexi Page
- Calculated Insights
- Flows

3. Check Additional Dependencies:
- Besides the fundamental dependencies, ensure to check for dependencies in:
- Related List Enrichment
- Copy Field Enrichment
- Data Actions
- Reports & Dashboards
-Custom report types

Resolve Generic Errors:
- Errors such as “Could not find dependencies of 0g**” are generic and check for dependencies given below.

Specific Dependency Resolutions:
- Copy Field Enrichment:
- If a DMO field is used in copy field enrichment, deleting the copy field enrichment will also delete the associated data action created automatically.

- Reports:
- Check report types related to Data 360.
- Ensure the DMO field is not used in row summaries, bucket fields, or formula columns.
- Delete any reports using the DMO field before retrying the removal of DMO mappings.

To check which reports are using Data 360 objects that are causing Dependency issues:

1.Login to Workbench
2.Run the below queries and replace ssot__Account__dlm with Data 360 object which shows dependencies error in mapping review page.

To find Reports created by current/Logged In User use below call:
/services/data/v62.0/analytics/report-types/CustomEntity$ssot__Account__dlm/recent-reports?pageSize=100&isCurrentUser=true&offset=0

Report created by Other Users:
/services/data/v62.0/analytics/report-types/CustomEntity$ssot__Account__dlm/recent-reports?pageSize=100&isCurrentUser=false&offset=0

By following these steps, you can systematically address and resolve dependencies cases. If issues persist, consider reaching out to the support team for further assistance.