Temporary Storage Table

Are there any way to temporarily store values on appsheet or on user’s own phone, so when user adds or updates some table, that user can extract from that “temporary table” without having to *sync and read from the workbook?

I tried creating a table that lets user input production data, and retrieves the last entered data for a certain field, but everytime i need to sync with the table and that takes a long time. All I wanted is to retrieved the last inputted value by the user.

1 Like

Hi @siusaikwan! Unfortunately, I don’t think that is possible. I’ll be interested to see, however, if someone else can prove me wrong. :slight_smile:

@Kirk_Masden is correct, there is no device-local table your app can modify. There are user settings, wich are device-local, that the app can read from but cannot modify.


@Kirk_Masden, @Steve, have either of you used Private Tables before?

I’ve never really experimented with them, so this is just a guess. But I think a private table + Delayed Sync + Offline Storage Might achieve this functionality.

1 Like

Private tables use cloud-based storage, just like normal tables. The difference is that each user gets their own “private” copy of the table’s data store.

As I understand it. I might be wrong. @WillowMobileSystems shattered my world-view earlier, so I’m not sure of anything now…


To help boost your confidence…I agree with your assessment! :innocent:

And to elaborate, "The copy is stored in the user's cloud storage account". This is why the user must be able to login.

If anyone is thinking to use Private Tables, be sure to read the very last paragraph in the article carefully!


Thanks for the confidence booster!

Because the storage underneath private tables can’t be controlled by the app creator, the design of the private table can never change: you can’t add or delete columns!

The one worthwhile and safe use I can see for private tables is as a key-value store, because who couldn’t find a use for a key-value store? :slight_smile:


Thanks all! I assume the loading time for the Private Table should be load faster since it exists from the user’s own cloud storage and should consists of lesser data?

As for the Usersettings, I believe it won’t work in my case because the App cannot edit it? Let’s say, when a Form is saved, one of the field gets saved to the usersettings at the same time (i.e. As if an user is editing their own Usersettings and also editing a new form at the same time). Please correct me if I’m wrong.

May this Sample App be a solution for you?


Please have a look at those virtual columns:


@Fabian This worked perfectly! Interesting how I can store data into the virtual columns that was generated by the user, so data can be retrieved locally without having to resync to get the most recent data.


A private table is still located in “the cloud”, so really isn’t any faster or slower than any spreadsheet-based data used by your app.

Correct, your app cannot modify user settings directly. The user must interact with user settings to cause them to change,

1 Like