I’ve got a table that will contain multiple rows with data that has the same data in two fields - the name of the project and the version number. I need Bubble to scan through the table using the constraints I set it for these two things and change multiple entries where the constraints match the data.
In other words, I’m trying to remove the typically used :first dataexpression and just leave it as 'Search for X' but bubble is tell me that I ought to be searching for a single thing, when its the opposite of what I want to do in this case.
@adamhholmes thanks that seems to have worked. I didn’t realise that a list of things could also constitute multiple rows of items in a table. I thought a list was reserved for fields where ‘this item is a list’.
@tylerboodman working on the amendments page (trial management). So this is a workflow that will allow users to go back and edit data about an amendment they saved previously. The workflow goes into each of the tables and modifies the various fields in case the user want’s to revise this data.
On the back of this thread, another ‘list’ related query has come up, this time in backend workflows. I realised that a bunch of my tables should now have deletion instructions to delete lists (because there are multiple instances of them in a table) rather than just one, which is what they were.
This is my current set-up. I’ve got keys to point to what needs to be deleted, but I can’t figure out why Bubble is making the expressions red now that I’ve marked the thing to delete as a list.
Here is the problem, this is an example step following in the same backend workflow. Each of the steps you can see in the background there are having the same issue (as they’re all marked as lists now). Why is Bubble making this red because it’s now a list?
Because, as I said previously, to delete a list of things you need to use a ‘Delete a list of Things’ workflow action.
As shown in your screen shot, you’re currently using a ‘Delete a Thing’ workflow action, so it’s expecting a single thing, not a list… (hence the error)
I marked the checkmark under the key to indicate that field as a list. I can create a new workflow just for the lists (which is actually what I started doing), but if that checkmark doesn’t automatically indicate that the field is a list, why is it present?
I marked the checkmark under the key to indicate that field as a list. I can create a new workflow just for the lists (which is actually what I started doing), but if that checkmark doesn’t automatically indicate that the field is a list, why is it present?
That’s got nothing to do with the workflow actions… that just defines whether the parameter value is a single item or a list…
As I (and others) have pointed out several times, if you want to delete a list of things, you need to use a ‘Delete a list of things’ action.
The ‘Delete a Thing’ action that you’re currently using is only for deleting a single thing.
