For we changed the way we send Double fields (version 3.2.88p)

By Michael Bock, Founder & CEO - March 07, 2014

For we where sending a null value (or setting the field to null) if the value of an existing record with a Double (Numeric) field was 0. This was leading to errors from SFDC in some situation - for example when updating prices in SFDC.

Now we send the value as 0 when updating a Double field. 

This should make it possible to update e.g. UnitPrice on PriceEntry to 0.

version 3.2.88p (March 2014)

About the author

Michael Bock, Founder & CEO

Picture of
Michael founded Rapidi on technological excellence, fantastic customer service and continuous improvement. A data integration specialist since 1987, he remains focused on creating technology that solves real business problems.