SystemModStamp Change Made to Our Packages Breaks Them

  • 10Views
  • Last Post 3 weeks ago
0
votes
API User Reporting posted this 3 weeks ago

Simon et al:

The change you made as stated in the following link and described below has broken the changed packages.

It would appear your developers made a change that assumes if the source Salesforce object has a SystemModStamp column then the SystemModStamp column must exist in all target objects for the given source object. This is a fatal assumption and we have packages that have not worked since this change was made.

This was reported yesterday (Monday, April 30, 2018) during our business hours in the Eastern Time Zone in the United States, and we have not heard back from you. It is urgent that you reply and  your team reverts back to the old code / undoes the change.

Darryll Petrancuri

SkyVia Replication - LastModifiedDate vs SystemModStamp - LastModifiedDate Unreliable Mechanism

Hello Darryll,

As we told you before, we planned to implement this option this week. This option is not implemented yet. We will post here when it is implemented.

Taking into account your posts and wishes, we have made changes to the work of your replication packages as a temporary solution. They now use SystemModStamp instead of LastModifiedDate.

 

Best regards,

Simon

0
votes
Simon Bubnov posted this 3 weeks ago

Hello Darryll,

 

We have answered you in another topic of Skyvia support portal: https://support.skyvia.com/thread/skyvia-replication-lastmodifieddate-vs-systemmodstamp-lastmodifieddate-unreliable-mechanism/

 

Best regards,

Simon

Close