This should be easy for you! Thank you for helping!
Hello Glide Community!
Since days I’m encountering the same problem to a basic function, with no solution found.
I’m new to Glide, watched all the video content and asked ChatGPT and the support bot for help - no solution.
Problem Description:
I have set up a Glide workflow that should trigger when the “Infusion Assemble” button is pressed in the “Infusion Selection” table. The workflow is intended to delete all previous scent selections made by the current user in the following tables:
Scent Selection 1
Scent Selection 2
Scent Selection 3
Setup:
I have created relations in the “Infusion Selection” table linking the User-ID to the corresponding scent selection tables using the column User ID. The relations are configured to Match multiple rows.
In the Glide workflow, the “Delete Row” action is used to delete all related rows based on these relations.
What is not working:
When the workflow is triggered, the Delete Row action does not delete any rows from the Scent Selection tables.
I have confirmed that the relations are correctly established, as they show the expected related entries.
Even when I remove the conditions and use a direct Delete Row action linked to the relation, the rows are still not being deleted.
Request:
What could be preventing the Delete Row action from working as expected in this setup?
Are there any known issues or specific settings required for relations or Delete Row actions in Glide workflows that could be causing this behavior?
When you open the workflow, you should see “Run History” in the top right corner, and a list of runs. Clicking any of those will show the details for the given run. Please check there and show me what you see.
It kind of makes sense, but I get the feeling that you are making this much more complicated than it needs to be. Perhaps we should take a step back a bit…
If you are deleting rows, then I assume that means that each time a user makes a selection a row will be added?
This seems to me to be completely un-neccessary. What I would do instead is just write the selections as a joined list in a single user specific column, split that and use it to make the relations, and then when you want to clear the selection just clear the user specific column.
Maybe I’m missing something, but does that not seem a simpler approach?
So would each “session” consume one row of “selections” in your flow? Say I have a session in your app and choose as many as I want, do you want to store it in my historical data, or would they all be deleted after a session?
