# Editing Dataset through Table Component in Vision

**URL:** <https://forum.inductiveautomation.com/t/editing-dataset-through-table-component-in-vision/59964>\
**Category:** Ignition\
**Tags:** ignition81, vision\
**Created:** [May 24, 2022, 3:42pm UTC](https://forum.inductiveautomation.com/t/editing-dataset-through-table-component-in-vision/59964 "2022-05-24T15:42:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Urvish\_Mehta](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/urvish_mehta/32/81912_2.png) [@Urvish\_Mehta](https://forum.inductiveautomation.com/u/Urvish_Mehta)\
**Post date:** [May 24, 2022, 3:42pm UTC](https://forum.inductiveautomation.com/t/editing-dataset-through-table-component-in-vision/59964/1 "2022-05-24T15:42:51Z")

</div>

Hello Everyone,  
I need to store recipe names in ignition without SQL, User should be able to change the recipe name, What would be the right approach to do this? I created a dataset tag in vision client with Recipe ID and Recipe name and displayed that in table component. Now I want to edit name column, I am able to edit that but I want to make that change into dataset as well. I need to do this as I want to read same dataset at different windows.  
Let me know your thoughts or even if there is a better way to do it.  
Thanks

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [May 24, 2022, 3:56pm UTC](https://forum.inductiveautomation.com/t/editing-dataset-through-table-component-in-vision/59964/2 "2022-05-24T15:56:11Z")

</div>

The right way to do this is a database.

Even if you get this working, what happens to your dataset if two users are making modifications to recipes at the same time? What happens to your recipes if Ignition goes down for some reason?

Databases give you atomicity and fault tolerance (and a host of other benefits). If you don’t want to pay for one, use MariaDB or Postgres. If you don’t want a ‘full’ RDBMS, use SQLite.

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [May 24, 2022, 9:13pm UTC](https://forum.inductiveautomation.com/t/editing-dataset-through-table-component-in-vision/59964/3 "2022-05-24T21:13:33Z")

</div>

@PGriffith What about for Ignition edge though? You’re a bit stuffed there and if you want the same app (or for the edge one to be incorporaded into a central standard igntion) for both edge and standard, dataset tag is the only option. Luckily I don’t use edge much but this is definitely one of the major reasons we don’t.  
Also, I imagine not having access to recipes if ignition is down wouldn’t be an issue. If ignition is down, the operators have no interface anyway so moot point 😁