# Input init values unexpected behaviour

**URL:** <https://community.weweb.io/t/input-init-values-unexpected-behaviour/7031>\
**Category:** How do I?\
**Tags:** binding\
**Created:** [February 14, 2024, 9:06pm UTC](https://community.weweb.io/t/input-init-values-unexpected-behaviour/7031 "2024-02-14T21:06:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![gduteaud](https://avatars.discourse-cdn.com/v4/letter/g/f19dbf/32.png) [@gduteaud](https://community.weweb.io/u/gduteaud)\
**Post date:** [February 14, 2024, 9:06pm UTC](https://community.weweb.io/t/input-init-values-unexpected-behaviour/7031/1 "2024-02-14T21:06:23Z")

</div>

Hi all,

I built a table with inline editing functionality. I set it up such that the initial values of the input fields that show up when the user enables the “edit” option on a row are set to the item’s current values (from the collection).

HOWEVER, and this is where things get weird: if I leave the initial values in and submit as is, all the input values are treated as empty instead of their initial values.

Any idea what’s happening? Am I doing this wrong?

---

<div class="post-metadata">

**Author:** ![sam1](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/sam1/32/6724_2.png) [@sam1](https://community.weweb.io/u/sam1)\
**Post date:** [February 14, 2024, 9:28pm UTC](https://community.weweb.io/t/input-init-values-unexpected-behaviour/7031/2 "2024-02-14T21:28:51Z")

</div>

Whats your submit workflow

---

<div class="post-metadata">

**Author:** ![gduteaud](https://avatars.discourse-cdn.com/v4/letter/g/f19dbf/32.png) [@gduteaud](https://community.weweb.io/u/gduteaud)\
**Post date:** [February 15, 2024, 5:55pm UTC](https://community.weweb.io/t/input-init-values-unexpected-behaviour/7031/3 "2024-02-15T17:55:20Z")

</div>

It just passes the input field values to the backend to update the item. Its like WeWeb doesn’t recognize input values = init values if they haven’t been modified.