Can’t map multiple WordPress objects to the same Salesforce object

@joecanas1 you’re right, that weight field is misleading. I need to think more about this and determine what we were doing with this field. It’s possible it should go away, or that it needs some significant work to behave as expected. I’m just not sure at the moment.

However, I think it’s possible you could accomplish your goal with existing developer hooks in the plugin. I am not particularly familiar with WooCommerce or how its API works (although I know it has one), so it may be naive of me, but here’s the kind of thing you could investigate:

add_filter( 'object_sync_for_salesforce_push_params_modify', change_push_params', 10, 6 );
function change_push_params( $params, $mapping, $object, $sf_sync_trigger, $use_soap, $is_new ) {

	/*
	if woocommerce provides a way to get the shipment tracking number via its api, with any data that you have available at this point, you could retrieve it
	* if the operation is an update ($is_new = false), the Salesforce object ID is also there. I don't think it would be ideal, but you could access the plugin's instance of the Salesforce API here as well and query it.
	*
	if ( is_object( $this->salesforce ) ) {
		$salesforce_api = $this->salesforce->salesforce['sfapi'];
	} else {
		$salesforce = $this->salesforce();
		$salesforce_api = $salesforce->salesforce['sfapi'];
	}

	if ( is_object( $salesforce_api ) ) {
		$query = "you can write any SOQL query that works in Salesforce here, and get results back";
		$result = $salesforce_api->query( $query );
	}
	*/
	$shipment_tracking_number = 'something';

    $params = array(
        'email' => '[email protected]',
        'FirstName' => 'test',
        'LastName' => 'name'
        'ShipmentTrackingNumber__c' => $shipment_tracking_number,
    );
    return $params;
}

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.)

@joecanas1 I think there’s a fairly large amount of work that will need to be done to provide the ability to sync multiple objects to the same object like this. I think it is a good feature if it can be done properly, but it’s a good bit of work and may prove complicated.

I think what I’ll do is hide this weight field in the next small release of the plugin, as you are completely right that it is misleading. We can reveal it again when/if the functionality is working as it should.

I’ve added a GitHub issue to track this here: https://github.com/MinnPost/object-sync-for-salesforce/issues/135

I’ll leave it up to you whether it is good to close this topic for now, but I don’t think we’ll have an immediate solution.

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.

And yes, good to close this topic for now.