Loading

History Objects may show fewer records in CRM Analytics

Data pubblicazione: Jul 17, 2023
Descrizione
When creating a dataset based on a history object, users may notice a discrepancy on the number of records in CRM Analytics compared to local data.

History objects represent historical information about an object’s changed field values. If the Integration user has no access to the field of the corresponding history data, the record will not be visible to the Integration User.

Sample Scenario:
The Admin user created a dataset based on the "TestObject__History" whose parent object is "TestObject".
The dataset only contains 120 rows, however, after the admin ran a SOQL query on the history object it returned 132 rows.

To investigate the discrepancy, the admin created a lens grouped by "Changed Field", the result is as follows:
 
Changed Field
 Count of Rows
Name
64
Status
30
Level
20
IsActive
6

6
6


To examine the local data, the Admin user ran the following query in Workbench:

Select Field, Count(Id) From TestObject__History Group By Field
 
 FieldUnknown_Field__1
1Name64
2Status30
3Level20
4Time__c12
5IsActive6


Notice that the result in Workbench has an additional changed field, "Time__c". After reviewing the Field Level Security of the "TestObject", the admin found that the Integration user has no access to the "Time__c" field.

 
Risoluzione
Review the Field Level Security of the Object related to the history object and ensure to make all the fields in the Parent object visible to the Integration User when synching any history object.

1. In Setup | Go to Security | Field Accessibility
2. Select the object in the list
3. Choose your view , select "View by Profiles"
4. Select the "Analytics Cloud Integration User" Profile
5. If a field shows hidden, hover on it and it is shows "Hidden because of field security", click on the 'Hidden' link and in the Access Settings page, select the "Visible" checkbox in the Field-Level Security section
6. Save
Numero articolo Knowledge

000381053

 
Caricamento
Salesforce Help | Article