The socket message data can’t be selected in the data picker of an inline flow.
It is available though, if I add it directly via code view:
$event.message
1 Like
@Teodor In general, flows don’t work very well with context when it comes to pickers.
There was another post recently where you had suggested to use code view for an event binding.
This goes for both inline flows, and page flows. For page flows, a specific example would be unable to bind flow-params in pickers.
Not creating separate bug report because I think action pickers in flows need some attention and robust testing in general, and not specific to this bug.
@sid is there a simple way to list all the data an event emits?
You can find the emitted data in inspect tab of your browser actually.
Go to network tab, filter by WS (websocket), and reload the page.
You should see the socket connection there. Click on it, and then click on “Messages” tab.
Here you can see all in/out WS messages. Click on any item to view the full message data.
1 Like