Rule to update referenced node after customer completes checkout

Question

I've got a rule which fires on "Customer completes checkout".

When it fires I would like to update a field in a node which is related to the one which was "checked out".

The node which is "checked out" has an entity reference field which relates it to another node, of a different content type.

So I have my Rule Event: "Customer completes checkout" And the condition: "Entity has field" which checks for the entity reference field

Under Actions, I have: "Fetch entity by ID" to fetch the referenced node. And I have provided a "Variable name" for the Fetched Entity.

I know this much works because I can print the Title of the referenced node as a status message on the site at this point. I can even print the contents of the field that I want to update using the token [the-fetched-node:field-name]

But when I add an Action: "Set Data value" and look for the field to update, the-fecthed-node:field-name is not available.

I can see things like the-fetched-node:body and the-fetched-node:title, but none of the fields of the node seem to be available to Set Data values on...

How can I get access to set the data in my required field?

I'm using the Rules (7.x-2.9) and Ubercart (7.x-3.9) modules.

Answer 1

This question seemms to be a variation of Populate an entity reference field, which suggests a solution like so:

• Add Condition: “Entity has field”, checking for your reference field
• Add Action: “Fetch entity by id”, supplying your node/user id from another field in the dataset and providing a meaningful name (Note: This solution implies you get the id by a simple field value in your dataset; you might want to add another condition to register the id first)
• Add Action: “Set data value”, which you now can supply your entity object from the step before (hence a name you'll identifiy in the dataset)

Apart from some Rules "Event" you probably need to add to it (related to your "After customer completes checkout"), this should be pretty close to what you're looking for.

Answer 2

Under the hood, Rules 7.x-2.x keeps around something called a RulesState object, which you can think of as a sort of grab bag that keeps data around for conditions and actions of the rule to process later in the chain, if the Rules event you're triggering on does not make the data you want directly available.

@pierre.vriens' approach is not too bad. Somehow, you need to get grab the field you want so the field is available (i.e., stamped into RuleState) for the action you want to use.

I'm guessing the event you're trapping is defined as:

  $events['uc_checkout_complete'] = array(
    'label' => t('Customer completes checkout'),
    'group' => t('Cart'),
    'variables' => array(
      'order' => array(
        'type' => 'uc_order',
        'label' => t('Order'),
      ),
    ),
  );

The definition means you will get a uc_order object, named as "order" as part of your RulesState. This is set up as an entity in uc_order.module.

I haven't used Ubercart, but from reading the code, it looks like the uc_order object has a "products" array, and that the "bid" node you want to access will be in that array. So:

• As the first part of the actions, do a Rules loop that uses the "products" array to pull out one of the products, and assign it to a variable via a data selector.
• At this point, the bid should be accessible, along with its fields. If all you need to do is update the content of another of the node's fields, it should now be possible.

If you can have multiple products in the cart's order but only want to operate on some one them, it gets a little trickier, although I think you can create a Rule Component that you will call for each of the items in the cart. The component can test if the component is of the "bid" type, and process just those. Since components can bundle conditions along with actions, this should give you the flexibility you need.

Answer 3

Create a component

Plugin: Rule

Component Name: kewl

Data Type: Node >> Name: kewl >> Machine name: kewl

Add Condition >> Entity has field >> kewl >> [select the field you want to update]

Add Action >> Set a data value >> kewl:[the field you want to update]

Create Rule

Add Loop >> node:field-[your reference field name]

• Add Action >> Under Components, Rule: Kewl >> list-item