[BUG] Row values not returned for factMap

[nessrine-slimani]

Describe the bug

Based on the following documentation, requesting the report should return factMap with the rows and aggregates

/services/data/<latest API version>/analytics/reports/query

However the response return fact map without values for rows

To Reproduce

Request:

POST https://eu18.salesforce.com/services/data/v49.0/analytics/reports/query

{'reportMetadata': {'detailColumns': ['ACCOUNT.STREET_LINE2', 'ACCOUNT.STREET_LINE3', 'Account.Case__c', 'CASE_ID'], 'sortBy': [{'sortColumn': 'CASE_ID', 'sortOrder': 'Asc'}], 'name': 'Salesforce 3', 'reportFormat': 'TABULAR', 'reportType': {'type': 'CaseList'}, 'scope': 'organization', 'standardDateFilter': {'column': 'Case.Today__c', 'durationValue': 'CUSTOM', 'startDate': '2021-02-09 00:00:00', 'endDate': '2021-02-09 23:59:59'}}}

Reponse:

{'attributes': {'describeUrl': '/services/data/v49.0/analytics/reports/null/describe', 'instancesUrl': '/services/data/v49.0/analytics/reports/null/instances', 'isReportTrendedByAnyone': False, 'reportId': None, 'reportName': None, 'type': 'Report'}, 'allData': False, 'factMap': {'T!T': {'aggregates': [{'label': '751.444', 'value': 751444}]}}, 'groupingsAcross': {'groupings': []}, 'groupingsDown': {'groupings': []}, 'hasDetailRows': False, 'picklistColors': {}, 'reportExtendedMetadata': {'aggregateColumnInfo': {'RowCount': {'dataType': 'int', 'label': 'Record Count'}}, 'availableDashboardSettings': None, 'detailColumnInfo': {'ACCOUNT.STREET_LINE2': {'dataType': 'string', 'filterValues': [], 'filterable': True, 'inactiveFilterValues': [], 'isLookup': False, 'label': 'Billing Address Line 2', 'uniqueCountable': True}, 'ACCOUNT.STREET_LINE3': {'dataType': 'string', 'filterValues': [], 'filterable': True, 'inactiveFilterValues': [], 'isLookup': False, 'label': 'Billing Address Line 3', 'uniqueCountable': True}, 'Account.Case__c': {'dataType': 'string', 'entityColumnName': 'Account.Case__c', 'filterValues': [], 'filterable': True, 'inactiveFilterValues': [], 'isLookup': True, 'label': 'Case', 'uniqueCountable': True}, 'CASE_ID': {'dataType': 'id', 'entityColumnName': 'Case.Id', 'filterValues': [], 'filterable': True, 'inactiveFilterValues': [], 'isLookup': False, 'label': 'Case ID', 'uniqueCountable': True}}, 'groupingColumnInfo': {}}, 'reportMetadata': {'aggregates': ['RowCount'], 'chart': None, 'crossFilters': [], 'currency': None, 'dashboardSetting': None, 'description': None, 'detailColumns': ['ACCOUNT.STREET_LINE2', 'ACCOUNT.STREET_LINE3', 'Account.Case__c', 'CASE_ID'], 'developerName': None, 'division': None, 'folderId': '0050N000007JABmQAO', 'groupingsAcross': [], 'groupingsDown': [], 'hasDetailRows': False, 'hasRecordCount': True, 'historicalSnapshotDates': [], 'id': None, 'name': None, 'presentationOptions': {'hasStackedSummaries': True}, 'reportBooleanFilter': None, 'reportFilters': [], 'reportFormat': 'TABULAR', 'reportType': {'label': 'Cases', 'type': 'CaseList'}, 'scope': 'organization', 'showGrandTotal': True, 'showSubtotals': True, 'sortBy': [{'sortColumn': 'CASE_ID', 'sortOrder': 'Asc'}], 'standardDateFilter': {'column': 'Case.Today__c', 'durationValue': 'CUSTOM', 'endDate': '2021-02-09', 'startDate': '2021-02-09'}, 'standardFilters': [{'name': 'units', 'value': 'h'}], 'supportsRoleHierarchy': False, 'userOrHierarchyFilterId': None}}

Expected behavior Row values returned

Screenshots Not applicable,

Code snippet Provided above

Note: Because the developers need to copy and paste the code snippet, including a code snippet as a media file (e.g. gif) is not sufficient.

Environment

• SDK Version: 1.3.0
• Python version: 3.8

• The bug has the severity

• [x] Critical: The defect affects critical functionality or critical data. It does not have a workaround.
• [ ] Major: The defect affects major functionality or major data. It has a workaround but is not obvious and is difficult.
• [ ] Minor: The defect affects minor functionality or non-critical data. It has an easy workaround.
• [ ] Trivial: The defect does not affect functionality or data. It does not even need a workaround. It does not impact productivity or efficiency. It is merely an inconvenience.

Additional context Add any other context about the problem here.