In this release we have done some work to better support MS Dynamics CRM 4.0
We have implemented Source Control support when reading from MS Dynamics CRM 4.0. To enable this, please select the "modifiedOn" field in "Source Control" on the transfer. As the modifiedOn field has only a precicion of seconds, it cannot garantie that it is unique. This forces us to use a GreaterEqual filter when reading changes since last run. However to avoid actually transferring the same record twice, we do a little optimization check - we check if there is only one record with the same modifiedOn value as was set in the RTI. If this is the case, we simply skip reading that record and continue with the next record. This should work just fine under all normal conditions.
Please note that if you change the time settings on the MS CRM server, then the Integration should be stopped some time in advance and not run for some time after the change to avoid missing some records.
We also made a few error fixes in this release:
* If you transfer the ownerid to CRM, then we now ignore this field, if it is NULL (empty). This prohibits an error from CRM that you cannot set the ownerid to Null.
* In some cases if you got an error from CRM after an insert (and CRM had actually inserted the record), you would end up with two new records in CRM. This has been fixed so that only the first record are sent to CRM. You still risk adding the record several times to CRM if the transfer runs again, but this problem is on the CRM side and we cannot fix that.
* In some cases the RapidiConnector could use a lot of memory when trying to connect to a local CRM server and the "Server URL" was wrong. This has been fixed so that you now get a nice looking error message.
* Adding default values to CRM resultet in an error. This has been fixed.
* Adding default values to Salesforce.com resultet in a error. This has been fixed.
* datetime values are now converted to UTC values when read from MS CRM and also expected to be in UTC when added to MS CRM.
