I want to request from “run code” specific metafield by namespace and key, since it says “returns metafield by namespace and key” (see inputQuery.png). I assume this is also possible technically, since if I use “metafields” instead of “metafield” - I get all metafields surely in the output. But then the output size becomes very big and I alsways get ERROR: 50kb OutputSizeExceeded.
I do a request with the query from inputQuery.png, with metafield field.
What do I expect:
I expect to be able somehow to request a specific metafield by namespace and key.
What is actually happening:
If I use the input query from inputQuery.png - I get no metafields, I get output from output.png. If I try to provide namespace or key as argument - I get error from error.png.
I don’t recommend looping over metafields as that pulls a lot of data. This is a gap in Run code that you cannot add metafield aliases via the input query.
Add a “log ouput” step somewhere in the workflow and then choose that “metafield” via “Add a variable”. It will say “requires arguments”. Once it’s added to the workflow you can use it in Run code via the aliases name
The input query is a way to pass the variables from the workflow into the Run code step’s sandbox. You need to add that metafield’s path to the input query like: