Roke
Roke8mo ago

How do I extract row information from a rowy trigger

Hey all, I'm new to Buildship and have been struggling all day with something that has to be trivial. I created a Rowy trigger (extension) that fires a buildship workflow (from a firebase change). All that workflow does is receive the trigger (the first node) then attempt to output a field to the console.
All I'm trying to do is extract a field from a row that was added or deleted. So in my firebase there is a record that has a field called 'contextId'. I delete it and the trigger fires and I can see a lot of data embedded in the logs. But what i would expect I could do (based on the documentation) is to export to the console this:
'Context: ' + (x)Row.contextId or maybe 'Context: ' + (x)Before.contextId (where obviously the 'Context' is just so it's clear in the logs). Anyone out there to tell me what I'm doing wrong?
Solution:
Hi @Roke @bobjoneswins, All the information that is gettring triggered by the Rowy Trigger gets stored in a Row variable (you can check more variable from output) you can use it to extract any field/cell value from your rowy table. Example (in the above image) - I have a colum with id welcomeMessage, (x)Row.welcomeMessage will get the row data from welcomeMessage and you can then use it anywhere in your workfow.
No description
Jump to solution
3 Replies
bobjoneswins
bobjoneswins8mo ago
Did you ever receive any help with this issue?
Solution
Gaurav Chadha
Gaurav Chadha8mo ago
Hi @Roke @bobjoneswins, All the information that is gettring triggered by the Rowy Trigger gets stored in a Row variable (you can check more variable from output) you can use it to extract any field/cell value from your rowy table. Example (in the above image) - I have a colum with id welcomeMessage, (x)Row.welcomeMessage will get the row data from welcomeMessage and you can then use it anywhere in your workfow.
No description
bobjoneswins
bobjoneswins8mo ago
Thank you for your reply. I guess ROWY did not have anybody as helpful and skilled as you are to answer his question previously. I wonder if he just gave up and moved to another product.