# Upon navigation to a new step (on the same page), input data reset's without trigger

**URL:** <https://community.weweb.io/t/upon-navigation-to-a-new-step-on-the-same-page-input-data-resets-without-trigger/7002>\
**Category:** Ask us anything\
**Tags:** bug\
**Created:** [February 13, 2024, 5:07pm UTC](https://community.weweb.io/t/upon-navigation-to-a-new-step-on-the-same-page-input-data-resets-without-trigger/7002 "2024-02-13T17:07:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![buildnocode](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/buildnocode/32/2964_2.png) [@buildnocode](https://community.weweb.io/u/buildnocode)\
**Post date:** [February 13, 2024, 5:07pm UTC](https://community.weweb.io/t/upon-navigation-to-a-new-step-on-the-same-page-input-data-resets-without-trigger/7002/1 "2024-02-13T17:07:40Z")

</div>

I have a pop-up sidebar that houses a “Tabs element” with 8 steps. I navigate between the tabs inside this element using a button which triggers a workflow to change the tab value. This resets the input values of the previous step.

A walkaround I am using is that I have created an Object variable for each step that is updated when each input (within a step) is changed and then bind the variable data to the input.

 ![Step navigation button workflow](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/7/7f48d84b4b8a3d78cb3778b500c32c43122aa039.png)

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [February 13, 2024, 6:12pm UTC](https://community.weweb.io/t/upon-navigation-to-a-new-step-on-the-same-page-input-data-resets-without-trigger/7002/2 "2024-02-13T18:12:17Z")

</div>

Hi @buildnocode 👋

That sounds like a good approach if you are using a multi-step form with different tabs that are conditionally rendered. Did you have a question you needed help with?

---

<div class="post-metadata">

**Author:** ![buildnocode](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/buildnocode/32/2964_2.png) [@buildnocode](https://community.weweb.io/u/buildnocode)\
**Post date:** [February 13, 2024, 11:38pm UTC](https://community.weweb.io/t/upon-navigation-to-a-new-step-on-the-same-page-input-data-resets-without-trigger/7002/3 "2024-02-13T23:38:58Z")

</div>

Apologies. I should have made the question more clear.

To me, creating a variable to store the object feels like a an additional step. I don’t want the inputs of the previous step to disappear without me creating a reset variables action.

Is this a feature or a bug?

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [February 14, 2024, 12:03am UTC](https://community.weweb.io/t/upon-navigation-to-a-new-step-on-the-same-page-input-data-resets-without-trigger/7002/4 "2024-02-14T00:03:55Z")

</div>

No worries!

Well, if your steps are conditionally rendered, it’s a feature because when you move on to the next step, the elements (and inputs!) from the previous step are no longer rendered. In effect, they no longer exist.

You can [learn more about conditional rendering here](https://docs.weweb.io/css-and-styling/conditional-rendering.html) if you’d like.

That said, you don’t need to create a separate variable for each step. You could have one object variable for example `answers` that you update step after step with a partial update:

 ![CleanShot 2024-02-14 at 01.03.38@2x](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/d/d0ca1c10ff2ae2209411b1be7c560f7d078a4a5c.png)

In the example above, before moving on to step 2 of our form, we update the `answers` variable with the name and then the job title of the user.

Does that make sense?