We are newly implementing with UiPath and are automating Salesforce activities. When we update a field using the Salesforce Update and integration services connection, large numbers are losing precision due to the DataType of System.Single. Has anyone found a work around that utilizes the Salesforce API or is UI automation via a browser the more reliable solution?
When you’re working with Salesforce and UiPath, and you encounter issues with data types, such as precision loss with System.Single, there are a few approaches you can take to handle this situation:
- Use Decimal Data Type*: If possible, change the data type from
System.SingletoSystem.Decimalwithin your automation workflow. TheDecimaltype has a greater precision and is more suitable for financial calculations. - Salesforce Activity Pack*: Make sure you are using the latest version of the UiPath Salesforce Activity Pack, which might have specific activities or properties to handle precision correctly.
- Salesforce API*: If the standard activities do not meet your precision requirements, consider using the Salesforce API directly. You can call the API using the
HTTP Requestactivity in UiPath to perform the update operation, ensuring that you format the number as aDecimalin the JSON payload. - Custom Code Activity*: You can use an
Invoke Codeactivity in UiPath to write custom .NET code that updates the Salesforce field using the API, which allows you to control the data type and format explicitly. - UI Automation*: If all else fails, automating the Salesforce web interface using UiPath’s browser activities is a last resort. This is less reliable than API integration due to potential changes in the UI and slower performance but can be a temporary workaround.
1 Like
I am not sure which activity you are using but for me I prefer to use the Update Record (or Insert record if its a new record). This way all your organization fields are available with their actual datatype
We are using the Update Record activity.
Thank you for all the suggestions.
I’m adding the fields from the activity itself and not from the properties pane. It’s easier there as you would just need to pick the fields from your org.

