Troubleshoot Actionable Lists Created from Data 360 Data Model Objects
To resolve issues when you create actionable lists from Data 360 data model objects, try these resolutions.
Required Editions
| Available in: Lightning Experience |
| Available in: Clouds that have Industry Sales Excellence and Data 360 licenses |
Use the table to identify the possible reason for an issue and the resolutions to try.
| Issue | Reason | Possible Resolution |
|---|---|---|
| The DMO doesn't appear in the Select a Data Model Object dropdown list. | The DMO isn't created in Data 360, or isn't mapped to the Data Lake Object (DLO). | In Data 360, go to Data Model Objects and confirm that the DMO exists. Confirm that the DMO is mapped to the correct Data Lake Object. Confirm that the Data Space shown in the wizard matches the Data Space where the DMO is configured. If your org uses a non-default Data Space, select it from the Data Space dropdown list before you search. |
| Users see no results after they apply a filter. | The primary key mapping in the Actionable List Definition is incorrect, the Data Lake Object (DLO) has no records with matching Account IDs, or the data stream didn't run successfully. | From Setup, open the Actionable List Definition and confirm that the primary key field is mapped to the field that contains Salesforce Account IDs. In Data 360, open the source Data Lake Object and preview records. Confirm that the Account ID values in the object match 18-character Salesforce Account IDs in your org. Verify the data stream's Last Run status. If the last run failed, resolve any source connectivity or data format issues and trigger a manual refresh. |
| The Data 360 data model objects option doesn't appear in the Select Data Source window. | The Actionable List with Data 360 data model objects setting in Setup isn't turned on, or no Actionable List Definitions are created yet. | Make sure that you turned on the Actionable List with Data 360 data model objects setting. Confirm that at least one Actionable List Definition exists. Users can't select the Data 360 data model objects option until a definition is available. |
| The member list shows records that the user isn't meant to see. | The user's profile, permission sets, or sharing rules grant broader Account access than intended. | Review the user's profile and permission sets to confirm that their record access is configured correctly. Verify the sharing rules and territory settings that grant broader account access than intended. If records from other users' books are visible, audit the Account owner and sharing configuration. This behavior is a CRM access control issue, not an Actionable List configuration issue. To understand how access to list members is determined, see How Actionable List Sharing Works. |
Did this article solve your issue?
Let us know so we can improve!
