# Refresh Data block in DVL

**URL:** <https://community.thunkable.com/t/refresh-data-block-in-dvl/2242963>\
**Category:** Questions about Thunkable X\
**Tags:** dvl\
**Created:** [January 26, 2023, 11:45pm UTC](https://community.thunkable.com/t/refresh-data-block-in-dvl/2242963 "2023-01-26T23:45:14Z")\
**Posts on this page:** 3\
**Page:** 1

<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:** [January 26, 2023, 11:45pm UTC](https://community.thunkable.com/t/refresh-data-block-in-dvl/2242963/1 "2023-01-26T23:45:15Z")

</div>

I’m curious about this block:

![image](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/d/a/da117b33578ec0ca4e2704d69407dc0638d42944.png)

The documentation states: “Refresh the Data Viewer List to sync with the Data Source.”

As I understand it, that block updates the displayed information in a Data Viewer List (DVL) after a change has been made to the data source.

A change could be: (1) Create a row, (2) Update a value, (3) Delete a row

Wouldn’t it make sense to have the refresh function automatically be part of #1, #2, and #3 above? That way, any time a change is made to the data source, the DVL updates to sync with the new state of the data source.

My real question, then, is: are there times when you **do not** want the DVL to update automatically? When you would make a change to the data source and intentionally **not** refresh the DVL display?

The one thing I can think of is speed. I imagine if you were creating/updating/delete a bunch of rows, it’s probably much faster to do so without refreshing after each change and then just refresh the DVL **once** after all changes have been made.

If that’s the only example, I’d think it makes sense to have a property or switch of some sort on the block that toggles refreshing for that individual block.

In Scratch, for example, there is a “Run without screen refresh” checkbox you can select (or not) when a function block is added to the screen:

 ![image](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/a/6/a6fe763c60a44316496f5605ec1aca2cfe155d0a.png)

---

<div class="post-metadata">

**Author:** ![knownkeep](https://avatars.discourse-cdn.com/v4/letter/k/bbce88/32.png) [@knownkeep](https://community.thunkable.com/u/knownkeep)\
**Post date:** [January 27, 2023, 9:04pm UTC](https://community.thunkable.com/t/refresh-data-block-in-dvl/2242963/2 "2023-01-27T21:04:41Z")

</div>

Speed will always be the main reason. There are times you might delete something locally and make a web call or two. I would say there’s lot’s of reason why you wouldn’t want to refresh the viewer until you are done. You just don’t want to waste the I/O until you need to.

It’s also helpful when you leave a DVL and go to another screen to do more work, then come back and call a refresh if you modified the data in another screen.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/0/f/0f59f292712368bce16ff80133ae10de8a6f27e8.png) [@system](https://community.thunkable.com/u/system)\
**Post date:** [April 27, 2023, 9:05pm UTC](https://community.thunkable.com/t/refresh-data-block-in-dvl/2242963/3 "2023-04-27T21:05:04Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.