Different instances of custom select component treated as one

Hi everyone,

I’m working on a form where I’ve built a custom select component, and I’m using two instances of it inside the same form - for example, one for gender and another just for demo purposes custom field (see screenshot attached).

Each select component is configured with a different Field name id which is passed via prop, however when I inspect the form’s data and change their values, both values are being written to the same key (gender in this case) and overwriting each other’s value. The result is the form treating them as one field, even though they are distinct in the UI.

How can I ensure that each component correctly updates its own corresponding key in formData?

Any insight would be appreciated. Thanks!

Hi Bernardo :waving_hand:

I’ll pass this question down to our tech team.

1 Like

Hi, any news on this topic @Agustin_Carozo?

Not yet, I’ll ask again

i also had this issue few days ago, and i had to reproduced the whole section. its probably relate to the last update as i ididnt encountered that before.

@tomerer2000 and were you able to solve the issue after redoing the whole section?

Yeah, it was all right on the second time