joecanas1
Forum Replies Created
-
And yes, good to close this topic for now.
Thanks for considering this as a future enhancement. I may try coding a workaround for the scenario I described: use the plugin to manage the bi-directional multi-field address sync, and call the SF API for a custom one-time WP-to-SF only push of the order tracking number to the SF contact record.
Thanks for the speedy response and excellent idea. I was also counting on the separate fieldmap trigger on shop_order (vs. user) updates. With the approach you described, I’d only have the WP user object’s update action available as a trigger.
In practice, the tracking number will be manually added to some (not all) orders some time after the order is created (i.e., once the order ships via USPS and a tracking number is issued). Unless the WP user record tied to the order is also updated, the tracking number might never be pushed to SF.
There’s probably a way to handle just the tracking number update using the plugin’s SF API object outside of standard fieldmap/trigger behavior, but I was of course hoping to avoid a large amount of custom coding.
If you determine that the salesforce_id field must remain unique, perhaps the Fieldmaps creation workflow could be modified to detect and prevent additional mappings to a previously mapped SF object. (At a minimum, remove it from the select list if it was used in an earlier fieldmap.)