Overview:
The user activity logs of a failed incremental sync show one or more errors of the type: AND SystemModstamp > Date of Last Sync.
Example:
| Process | Object Name | Description |
| Sync Server Error | Account | Account.Institution_Type__c != null AND SystemModstamp > 2018-12-12T21:55:05.074Z^ ERROR at Row:1:Column:3766 unexpected token: AND |
Root Cause:
This issue is related to the SOQL where clause of one or more VMobile Object Configuration (VMOCs) which are modified during incremental syncs adding the SOQL code AND SystemModstamp > date of last sync. This is added at the end of the existent SOQL code which creates a malformed query.
Example:
The original SOQL where clause of the Account VMOC is:
This SOQL where clause is modified by the incremental sync adding the code AND SystemModstamp > date of last sync creating a malformed query:
Solution:
The original SOQL code can be modified by closing the where clause with parenthesis to avoid that the incremental sync condition added causes a malformed query.
In our example, the following code modification avoids a malformed query during the incremental sync:
Related Documentation:
CRM Help Documentation: Using VMobile Object Configurations
Send us your feedback: We are always looking for feedback to help improve our Knowledge Base! Please let us know if this article is helpful or provide feedback on how we can improve your experience by clicking here.