[Log Action] Unable to access a metafield variable after including it

[Dylan]

This short screencast shows the error better than a wall of text could. But here are the reproduction steps:

1. Create a new Flow based on the Order created trigger
2. Add a new Log action
3. Add a new unstructured metafield variable, but do not create a corresponding alias for it
4. Now you’re unable to access the variable, nor are you able to name it with an alias after the fact

[Dylan]

Slight correction, I see that the alias is automatically generated.

So this time I was more careful and I noted the auto generated alias for this unstructured metafield variable.

Yet, there’s no properties within it.

I suppose the problem is that unstructured metafields cannot be used as variables in log outputs?

[Dylan]

Confirmed, when I create a definition for a metafield, then the value property is able to be selected.

So the problem is that the Log action doesn’t support unstructured metafields at this time.

I can just instruct merchants to add custom definitions, but if unstructured metafields aren’t supported then they shouldn’t be shown as an option in the action.

[Alan_G]

Hey @Dylan - thanks for flagging this and for all the info. I’ll bring this to the team and update you here once we have next steps/can confirm a fix

[Alan_G]

Hey @Dylan - just following up here, as we’ve recently pushed a fix that should resolve this issue. Can you let me know if you’re still seeing metafield variable access issues when replicating the set up above? If so, just ping me here and I can take a look for sure - hope this helps!

[Dennyarcher]

(post deleted by author)