1
In flows, why {{$trigger.keys}} for the key on action create, and {{$trigger.keys[0]}} on action update
Source: directus/directus#25274 · opened by @Pachat
Summary I have a flow trigged on create and want to have it also on update. I found out that the key of the collection's item is {{$trigger.keys}} on create and {{$trigger.keys.0}} on update. Why this difference (i understant that there is just one value on create, but a possible array on update? How handle this diffeence? Do i have to create 2 flows, on for create, the other one for update the collection? Basic Example _No response_ Motivation To simplify the creation and maintainance of flows Detailed Design Either • on the directus par, use {{$trigger.keys}} on both case • on the devloper; give him the abilyty to use expressions: None of these worked • {{$trigger.keys[0] || $trigger.keys}} • {{$trigger.keys[0] ? $trigger.keys[0] : $trigger.keys}} • {{$trigger.keys.0 || $trigger.keys}} • {$trigger.keys | first}} • {{$trigger.keys.0}} Requirements List Must Have: • A • B Should Have: •…
No pledges yet. Be the first to back this.
Comments
Similar requests
Import and export option for flows
82 votes · 0 comments
Insufficient documentation about blocking and non-blocking flows
3 votes · 0 comments
Enhancing Directus Flows: Versioning, Archiving, and Improved Manageability
28 votes · 0 comments
Add Simple Link to Triggered/Triggering Flow
2 votes · 0 comments
Add Sorting for Manually Triggered Flows
3 votes · 0 comments
No comments yet.