[BUG] With multi-select when you get options from an external database

Ask us anything
, , ,
1

Hello! I’m experiencing an issue with a multi-select element that receives its data from Supabase (and possibly other databases). I’ve created a video to help explain the problem, which you can watch here: Loom | Free Screen & Video Recording Software | Loom

Here’s a brief description of the problem:
I’ve designed a custom area to display the filters that the user has selected. You can also remove filters by clicking on them. However, when I delete filters by clicking on them (using a custom workflow), they are added back to the multi-select element multiple times instead of one. This issue only occurs with filters generated from data obtained from Supabase. Deleting filters created from options instead of pulling data from database works as expected.

Do I do something wrong? Thanks

2

Hey,

could you provide your workflow in detail here? Are you sure it’s not just a bug in your nocode logic?

If you still think it is a bug it will probably be faster if you report a bug here support.weweb.io , you can create a ticket and follow the progress of the resolution of your bug.

3

@Broberto

I don’t know, it shouldn’t be. Multi-select works with WeWeb made options, instead of data from CMS.

image
image1940×1046 225 KB

4

@Joyce maybe you have any input for this?

5

Hi @david :wave:

This looks like a bug. Can you report it here if you haven’t already?

In the meantime, here’s a video with a different approach that might help in the meantime.