The Exalate team will be on holiday for the coming days - returning Jan 4
Enjoy & stay safe
We push data from Jira into Salesforce and at the time of case creation in Salesforce - we have Salesforce Apex triggers that update fields in the case. These updates happen very quickly and appear to beat the SF Exalate node as it doesnt see that these fields have updated.
Can we trigger a SF outgoing sync on a timer/pause that we code into the SF Inbound firstSync if statement?
If I understand correct, the Apex triggers are updating some fields upon case creation on SF side and Exalate is then updating these fields once again during the first sync right?
Is Exalate updating those filed with different content coming from Jira side or are this fields coming empty from Jira and then Exalate is updating these fields back to blank?
Also, could I ask you to share the SF incoming sync rules so I can review them and test them on my end?
I would like to reproduce the issue first in order to suggest any changes to the script.
© 2019 Exalate. All rights reserved.