Hi,
I have a manual workflow for deleting rows whenever user clicks on the submit button of a particular form. The Delete row action happens in the loop of the workflow on the basis a relation column(workflow photo attached). If the relation column is non empty then the row is deleted and this logic loops for all rows. This works fine as long as the table referenced is a glide table.
If i replicate the same table data and columns in a big table(which i have to because this table will soon cross 25K in the long run), then suddenly i don’t see any computed columns(the ones highlighted in the green circle in the photo)
relations, query or any other computed columns or that matter from the list on the basis of which i need to run the loop. Also to optimise the workflow, i had applied a filter to the workflow where only non-empty rows of that relation column are to be parsed. This too is not possible with a big table. I can filter on any non computed column but relation columns are not showing up here as well.
IS THIS A RESTRICTION OF BIG TALBES? CAN WE NOT USE RELATION AND QUERY COLUMNS IN BIG TABLES AS BASIS FOR FILTER/DELETING ROWS LOGIC IN WORKFLOWS? @NoCodeAndy@nathanaelb please guide
I need the filter to only select specific rows which i can then delete else all the rows are deleted.
As shown in the screen shot with green highlights it is possible as the table is glide table while the the screenshot shot with red highlights shows that the exact same table (just converted to a big table) doesn’t give options of the relations/query columns to be used as filters.
Ignore the flow of the workflow. Just for comparison i put two pairs of query and delete to show how filters behave in glide vs big table.
I get that there might be some workaround for big tables which i can’t figure out yet but is what i’m observing a legit limitation of big table ? - Filter can’t happen on relations/queries in workflows having source as big table?
