• Resolved katjavolker

    (@katjavolker)


    Hey.
    I have a field map that connects WP product and the Salesforce object to sync.
    It has 21 fields that, if changed, should trigger the sync.
    There is one field we are not syncing which sets two other fields to true. On change of these fields another field in SF changes status to publish which is connected to the post_status of the WP object and a sync should be triggered. That does not seem to happen.

    Do you have any clue on why that is? Does the order of the fields matter somehow?

    • This topic was modified 2 years, 5 months ago by katjavolker.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter katjavolker

    (@katjavolker)

    Does it matter which order these fields have?

    Plugin Author Jonathan Stegall

    (@jonathanstegall)

    If I’m reading you correctly this part is the problem:

    “On change of these fields another field in SF changes status to publish which is connected to the post_status of the WP object and a sync should be triggered.”

    If you’ve just done a sync that changes the publish field, the plugin isn’t going to do another sync right away. This is how the plugin tries to avoid going into an infinite loop (where hypothetically saving a value in Salesforce would save a value in WordPress which would then save the value in Salesforce and so on).

    Thread Starter katjavolker

    (@katjavolker)

    Hey, Jonathan. Thank you for fast response and feedback.
    As far as I understand these fields are changed simultaneously in SF. I will have to check.

    So what you think is that the 2 fields are changed first, the sync triggers and then the publish field is set? This should still trigger a new sync since this field is mapped, too.

    I can see that it would take some more time for the second sync. The problem is that it never occurs.

    The order of the mapped field does not have anything to do with it, correct?

    Plugin Author Jonathan Stegall

    (@jonathanstegall)

    The order definitely doesn’t matter. The plugin bundles all of the data together each time it syncs.

    What I thought you were saying was that you run one sync that changes the publish field, then you expect that to trigger another sync. And to be clear if that is what you’re saying, it would never happen; the plugin doesn’t work that way.

    But if you’re not saying that, I think you should turn on debug mode and see if you can tell more about what is happening.

    Thread Starter katjavolker

    (@katjavolker)

    OK, thanks. I will have to check with the SF developers working on the project.

    No, I am not expecting to have another sync triggered. It should trigger after all relevant fields are set to their expected value.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Can not figure out why sync won’t trigger’ is closed to new replies.