improve support for arbitrary data structures

The difference is that data selection mode lets you choose the value for whatever parameter it is you're setting from the properties of a variable available to the Rule. Direct input mode lets you put in whatever you want as the value (without the constraints of the data type). The reason you don't see the order total token is because it's actually a field on the order variable, and the replacement patterns available to you do not generally include field data.

So, a better question for you would be how can you use a field token in a textarea for the body of an e-mail.

>Well, I know token contrib module in D7 provides tokens for entity fields. I used it with the rules in the past for accessing fields of a node. But looks like it doesn't work in this case.

Actually it's the entity API "entity tokens" module that does that. However, it currently does not cover generating tokens for fields that define a data-structure as property info. Also there is an issue for supporting multiple values in the entity api queue.

Hi, I just struggled with this too.
I've created attached patch as workaround - and it seems to work. However, I've tested only roughly (Yes, in my case as well to send the order-confirmations of commerce ;) ).
And I guess there could be a more elegant solution by use some kind of recursive construct.
Nevertheless I wont hold back the patch :)

Fix for description.

I don't think we should do that specifically for fields, as it is general problem for data-wrappers using structs. So let's solve it for structs in general.

I think best, we define a new token-type "entity-struct-wrapped" or so, which contains a wrapper as data value. That way can pass through the wrapper in token directly, what should make it easy to generate the token value.

I think Rules does it fantastically well. I guess we'd adapt the data selector values from Rules to Entity tokens.

subscribe

The patch in #1058856-22: Entity tokens not created for multi-value fields basically fixes this issue too. It does not properly register tokens for each data property of a structure though, as for that we'd need register a token-type. Currently, the properties of a data structure may differ by data structure (e.g. per field) though. Thus, the basic fix from #1058856 just lists some possible property-keys in the help text.

For a proper fix, we'd need a proper hook for defining compound data structures. Thus we'd have a central place for registering properties of the data structure + properly registered names. That could also be much needed by rules which currently has to complement entity-api data types on its own, as well as by other modules like wsclient.
Based upon this defined compound data structures, we could easily add proper token support for those. Still, for backward compability we should keep the current per-property 'property info' key.

Hi,

Any update on this ?

I'm trying to do what's in this issue: http://drupal.org/node/1262904 (i e concatenate the content of 2 variables in a direct input mode) and, even when updating to entity dev, it doesn't seem to be working...

The issue referenced in #10 is fixed. Is #1547160: Support variable substitution in direct input mode the next step for this?

Marking as a duplicate of #1547160: Support variable substitution in direct input mode.