Symptom
A Datasphere artifact is getting consumed via oData, but every time there is different number of rows pears on SAC
Environment
SAP Datasphere
Reproducing the Issue
Consume Datasphere artifact via oData on SAC
Resolution
This behavior happens on SAC when there is no sort applied in keys while doing odata request. Please ensure that the key is unique and the odata request have all keys sorted.
Check DataSphere guide set orderby as odata parameter: https://help.sap.com/docs/SAP_DATASPHERE/43509d67b8b84e66a30851e832f66911/7a453609c8694b029493e7d87e0de60a.html#use-odata-parameters
Keywords
Sorting, SAC, data inconsistency, oData , KBA , DS-BB-ODATA , To address issues related to Odata consumption API , Problem