Connector Improvement: Salesforce Connector - Data Integrity Issues
CompletedHi --
I am reaching out regarding a critical issue we've encountered, as detailed in ticket (#182001). There is a significant discrepancy between the data extracted via the Salesforce connector and that obtained through the Salesforce API.
To illustrate, when extracting data using the following command:
curl https://<my_domain>.my.salesforce.com/services/data/v59.0/sobjects/blng__Usage__c/XXXXXXXX?fields=id,blng__UnitPrice__c,BLG_Unit_Price__c,BLG_Usage_Total__c,CreatedDate
The API returns the following:
{
"attributes": {
"type": "blng__Usage__c",
"url": "/services/data/v59.0/sobjects/blng__Usage__c/XXXXXXXX"
},
"Id": "XXXXXXXX",
"blng__UnitPrice__c": 1.5e-06,
"BLG_Unit_Price__c": 1.5e-06,
"BLG_Usage_Total__c": 334.6259205,
"CreatedDate": "2023-12-24T02:05:13.000+0000"
}
This data clearly demonstrates that the API calculates values such as blng__UnitPrice__c and BLG_Usage_Total__c with a precision of 10 decimals.
However, when analyzing data retrieved through the Fivetran Salesforce connector, there is a noticeable discrepancy. For example:
XXXXXXXX XXXXXXXXXXX 2023-12-23 XXXXX 0.000002 223083947 446.167894
This variance is concerning and could potentially lead to significant data integrity issues.
Given these observations, could you please investigate the issue and provide guidance on how the Salesforce connector can be updated or configured to align with the results provided by the Salesforce API and UI?
Thanks!-
Official comment
Hi all,
An update here: we have implemented this request to sync the raw currency values as returned by the Salesforce API instead of the rounded values based on UI configuration. We will be rolling this feature out to all customers slowly. If you would like to receive this feature sooner, please reach out to our support team.
Please see our release notes for more information: https://fivetran.com/docs/connectors/applications/salesforce/changelog#april2024
Best,
Sadie
-
Hi Thierry,
Thanks for submitting this request. We have found that most customers want the data they sync to match what they see in the Salesforce UI, which is why we currently rely on the precision and scale as it's set in the UI.
However, I completely agree that it would be valuable to return values at a higher precision in cases like what you've described. I've added this to our backlog and we will look into how we can support this.
In order to decide on a solution, it would be helpful to understand your use cases a little more. You've described a case where you require values at the precision returned by the API. Do you also have cases where you expect values at the precision set in the UI? If so, can you provide some examples?
Best,
Sadie
Please sign in to leave a comment.
Comments
2 comments