Flows: Unable to use `{{$last.body.keys}}` in a read data Operation

[vanling]

Describe the Bug

When trying to pass on multiple keys to an read/update operation the keys are parsed as

"key": [
    "[\"03389a8b-4309-498a-b65b-9d0853d8881b\",\"60cbaa7c-de55-4154-981f-c993df1633be\",\"ba3cabf9-570e-4039-8707-2b80b3d44005\"]"
  ]

I expected to get the following

"key": [
  "03389a8b-4309-498a-b65b-9d0853d8881b",
  "60cbaa7c-de55-4154-981f-c993df1633be",
  "ba3cabf9-570e-4039-8707-2b80b3d44005"
]

and continue in the flow with the selected id/values

To Reproduce

1. Create a manual trigger
2. follow up with a read data
3. Add {{$last.body.keys}} as ID's

Errors Shown

No response

What version of Directus are you using?

9.12.1

What version of Node.js are you using?

v16.15.1

What database are you using?

mysql-server-8.0

What browser are you using?

Edge

How are you deploying Directus?

npm install on ubuntu server

Images

[massimans]

Hi,
you can work around it by using the raw editor and puting {{$last.body.keys}} but it will break the IDs as of directus 9.12.2
ps: i don't think it's api related since the issue appears to be that the field is adding [ ] arround {{$last.body.keys}}

[luciandavidescu]

Is this fixed really or am I missing something? I get the exact same issue in 9.22.4, even with the raw code editor.

[rijkvanzanten]

I believe the raw value is without quotation marks

[luciandavidescu]

They seem mandatory, can't save if I try to take them out

[luciandavidescu]

Weirdly enough, if I add a "run script" block and simply redefine the array as itself, it then works.

*"{{exec.related}}"

[EnzoBitMatrix]

How was this fixed?
I have the EXACT same problem that @luciandavidescu does above...

If I put the variable into a script, it shows without slashes, when I put it in a Create Flow, it adds them, and therefor makes the UUID invalid...

It say's this was fixed, but I can't find the fix.

[bogdan-nita]

Same issue is still present. It would be nice to be able to read items with the keys field of the $trigger on items.create / items.update but the Read Data operation doesn't play well with an array of strings instead of an array of numbers. When converting the array of string to numbers through a script operation I get the double square brackets issue.

[nhadsall]

I don't see any way around this. There should be an option to ignore the json validator when it's wrong.