Over the last few weeks we have done some updates to our Salesforce.com Connector which I will present to you below. These changes are quite specific to some customer situations, so you might not need to upgrade your service.
In some cases you could get a INVALID_SESSION_ID error message from Salesforce.com. This could happen when using Salesforce.com as Destination and when reading the relevant data from the Source system takes a very long time (this can happen when using our Mirror Technology and having several 100.000 records to process). We are talking times in the range of 30 minutes to 1 hour or more. What happens is that the Salesforce.com connection gets a timeout and that the session itself is also expired on Salesforce API side. We now intercept this message and automatically do a new login to Salesforce.com and send the data again. In this way the error is handled by the RapidiOnline Central Service and you wont even see the error message anymore. We also took the opportunity to clean up our existing error handling for Salesforce.com connection issues so this works better and more the same way as the normal operation. You need to be on version 3.2.90u Central RapidiOnline Service.
We now update the dataSent and dataReceived numbers on the Log entry for WebService based direct Connections (connections that are direct from the Central RapidiOnline Service and not through a RapidiConnector). This is the case for Salesforce.com connections. Before we only updated the Package Sent and Received numbers, which for Salesforce btw corresponds to the number of API calls made. This change will allow you to get a general idea about the volume of data sent to and received from the server. You need to be on version 3.2.91a Central RapidiOnline Service.
When reading from Salesforce.com using SourceControl (set to DBSourceControl, this is used to read only the changes from Salesforce.com and not all records), we could get an error message with EXCEEDED_ID_LIMIT from Salesforce.com. The message means that there are too many changes made in Salesforce.com since the last successfull update. The default value for this limitation on Salesforce.com side, is 200.000 records, but this limit can be raised for a specific Salesforce Instance. We now automatically handle this error and default back to do a full sync of all records - the same way as we handle the initial sync when you start to use this feature. The full sync can take a long time, but so would synching more than 200.000 records - anyway this is an exceptional situation to be in. You need to be on version 3.2.91d of the Central RapidiOnline Service.
Please note, that when you are using SourceControl to read from Salesforce.com you should not use the Commit Per setting (set it to 0). If this is set differently and you get an error on the transfer half way through, we cannot guarantee that all changes will be transferred.
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.