# Different instances of custom select component treated as one **URL:** \ **Category:** Ask us anything\ **Created:** [June 13, 2025, 3:35pm UTC](https://community.weweb.io/t/different-instances-of-custom-select-component-treated-as-one/18735 "2025-06-13T15:35:02Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![bernardosantos](https://avatars.discourse-cdn.com/v4/letter/b/a87d85/32.png) [@bernardosantos](https://community.weweb.io/u/bernardosantos)\ **Post date:** [June 13, 2025, 3:35pm UTC](https://community.weweb.io/t/different-instances-of-custom-select-component-treated-as-one/18735/1 "2025-06-13T15:35:02Z")
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). ![image](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/e/ece56dca6c263045a2b8ead88e8292b748b1d3cb.jpeg) 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. ![image](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/8/833928e1a70fe3a6408bceeb1d41b62a1cfb47df.jpeg) How can I ensure that each component correctly updates its own corresponding key in `formData`? Any insight would be appreciated. Thanks! ---
**Author:** ![Agustin\_Carozo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/agustin_carozo/32/13231_2.png) [@Agustin\_Carozo](https://community.weweb.io/u/Agustin_Carozo)\ **Post date:** [June 13, 2025, 6:00pm UTC](https://community.weweb.io/t/different-instances-of-custom-select-component-treated-as-one/18735/2 "2025-06-13T18:00:43Z")
Hi Bernardo 👋 I’ll pass this question down to our tech team. ---
**Author:** ![bernardosantos](https://avatars.discourse-cdn.com/v4/letter/b/a87d85/32.png) [@bernardosantos](https://community.weweb.io/u/bernardosantos)\ **Post date:** [June 20, 2025, 12:44pm UTC](https://community.weweb.io/t/different-instances-of-custom-select-component-treated-as-one/18735/3 "2025-06-20T12:44:31Z")
Hi, any news on this topic @Agustin_Carozo? ---
**Author:** ![Agustin\_Carozo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/agustin_carozo/32/13231_2.png) [@Agustin\_Carozo](https://community.weweb.io/u/Agustin_Carozo)\ **Post date:** [June 20, 2025, 2:03pm UTC](https://community.weweb.io/t/different-instances-of-custom-select-component-treated-as-one/18735/4 "2025-06-20T14:03:14Z")
Not yet, I’ll ask again ---
**Author:** ![tomerer2000](https://avatars.discourse-cdn.com/v4/letter/t/9d8465/32.png) [@tomerer2000](https://community.weweb.io/u/tomerer2000)\ **Post date:** [June 21, 2025, 10:48am UTC](https://community.weweb.io/t/different-instances-of-custom-select-component-treated-as-one/18735/5 "2025-06-21T10:48:11Z")
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. ---
**Author:** ![bernardosantos](https://avatars.discourse-cdn.com/v4/letter/b/a87d85/32.png) [@bernardosantos](https://community.weweb.io/u/bernardosantos)\ **Post date:** [June 26, 2025, 8:06am UTC](https://community.weweb.io/t/different-instances-of-custom-select-component-treated-as-one/18735/6 "2025-06-26T08:06:15Z")
@tomerer2000 and were you able to solve the issue after redoing the whole section? ---
**Author:** ![tomerer2000](https://avatars.discourse-cdn.com/v4/letter/t/9d8465/32.png) [@tomerer2000](https://community.weweb.io/u/tomerer2000)\ **Post date:** [June 26, 2025, 1:12pm UTC](https://community.weweb.io/t/different-instances-of-custom-select-component-treated-as-one/18735/7 "2025-06-26T13:12:35Z")
Yeah, it was all right on the second time