# Missing datasource create and update "row object from" blocks

**URL:** <https://community.thunkable.com/t/missing-datasource-create-and-update-row-object-from-blocks/1917989>\
**Category:** Feature Requests\
**Tags:** localdb, data-source\
**Created:** [June 9, 2022, 1:28pm UTC](https://community.thunkable.com/t/missing-datasource-create-and-update-row-object-from-blocks/1917989 "2022-06-09T13:28:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![paulovaz72](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/paulovaz72/32/119071_2.png) [@paulovaz72](https://community.thunkable.com/u/paulovaz72)\
**Post date:** [June 9, 2022, 1:28pm UTC](https://community.thunkable.com/t/missing-datasource-create-and-update-row-object-from-blocks/1917989/1 "2022-06-09T13:28:48Z")

</div>

Hi Thunkers,

I’m working in a offline database project, and I miss the create and update `row object from` block (similar to the “save” realtime DB Blocks approach)

I can get an entire row of a datasource table as an object using the `get row object`, but I can’t save a row using this approach. The create block at least allows you to save in a single block, but the update… man… You need to put a separate block for each row/column you want to save… So you need a lot of blocks when you have many columns, despite the non-elegant approach.

Somebody knows if there are plants to improve this in the future?

Regards,

Paulo Vaz

---

<div class="post-metadata">

**Author:** ![tatiang](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/tatiang/32/55482_2.png) [@tatiang](https://community.thunkable.com/u/tatiang)\
**Post date:** [June 9, 2022, 1:46pm UTC](https://community.thunkable.com/t/missing-datasource-create-and-update-row-object-from-blocks/1917989/2 "2022-06-09T13:46:35Z")

</div>

I agree. There should be a better way to update row data than having to use a separate Update Row block for every value.

---

<div class="post-metadata">

**Author:** ![muneer](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/muneer/32/75210_2.png) [@muneer](https://community.thunkable.com/u/muneer)\
**Post date:** [June 9, 2022, 4:22pm UTC](https://community.thunkable.com/t/missing-datasource-create-and-update-row-object-from-blocks/1917989/3 "2022-06-09T16:22:47Z")

</div>

Currently, I delete the row and create it again to work around this issue but it does not fit all use cases.

---

<div class="post-metadata">

**Author:** ![paulovaz72](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/paulovaz72/32/119071_2.png) [@paulovaz72](https://community.thunkable.com/u/paulovaz72)\
**Post date:** [June 9, 2022, 5:30pm UTC](https://community.thunkable.com/t/missing-datasource-create-and-update-row-object-from-blocks/1917989/4 "2022-06-09T17:30:08Z")

</div>

Hi @muneer

This, does’nt fit for my case… I’m developing a hibrid offline/cloud app so I need persistence in both sides (local and remote).

Anyway I’ll update [my post with features resquest](https://community.thunkable.com/t/45-ideas-for-thunkable-improvement/1874021) adding this request (45 until now…)

Regards,

Paulo Vaz

---

<div class="post-metadata">

**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\
**Post date:** [November 8, 2024, 1:13pm UTC](https://community.thunkable.com/t/missing-datasource-create-and-update-row-object-from-blocks/1917989/5 "2024-11-08T13:13:11Z")

</div>