June 28, 2021

Deployment Time: 11:45 AM PST

Features & Enhancements

Item Description
Feature A new button that lets you copy individual tables was added to the Editor. Deployed to 100% free users.
Feature A new welcome modal was added to render app preview or app template suggestions when creating a new app. Deployed to 100% of free users.
Enhancement Enhance CSV Import and Export to allow the CSV file's locale to be specified.

Previously, CSV Import required that the input CSV file be in US English format. For example, date values were required to be in MM/DD/YYYY format. Decimal values were required to use period as the decimal separator. Input data values were always delimited by commas.

Also previously, CSV Export always wrote the CSV file in US English format. For example, date values were written in MM/DD/YYYY format. Decimal values were written using period as the decimal separator. Output data values were always delimited by commas.

You can now specify the locale for both CSV Import and Export. For example, if you specify locale "English (United Kingdom)" imported and exported dates are in DD/MM/YYYY format and data values are delimited by commas. If you specify locale "German (Germany)" imported and exported dates are in DD.MM.YYYY format and data values are delimited by semicolons.

The application author specifies the locale on the Behavior > Action page of the "import a CSV file for this view" or "export this view to a CSV file" actions. You can either select the locale from the CSV file locale dropdown or you can supply an expression that yields the locale identifier such as en-GB or de-DE. The locale dropdown allows you to select any of the supported locales listed here https://help.appsheet.com/en/articles/4671936-supported-locales.

The locale expression allows you to compute the locale identified. For example, you might store the locale identifier for each user in a field in that user's UserSettings. Alternatively, you might store the locale identifier in a normal table and retrieve it using a LOOKUP expression.

Existing "import a CSV file for this view" and "export this view to a CSV file" actions are automatically updated to use locale en-US for backward compatibility. You can override these default locale settings using the Editor.

The CSV field delimiter is taken from the Windows CultureInfo.TextInfo.ListSeparator for the specified locale. For example, for "English (United States)" and "English (United Kingdom)" the delimiter is comma. For "German (Germany)" the delimiter is semicolon.

Import and Export are symmetric. If you Export in a locale you can (and should) Import in that locale.

Deployed to all.

Feature Use Locale en-US (English-United States) when the client device is using an unsupported locale

Application users can set their mobile device locale to unorthodox values such as nb-PL (Norwegian-Poland). The client includes this locale in the 'locale' property of the Sync request. The server attempts to retrieve and use this locale when evaluating expressions such as those for virtual columns.

Previously we reported a fatal error when the locale was unsupported. Now we use the locale en-US instead. We believe that this approach is better because it avoids fatal errors.

Bug Fixes


Rollout changes


Preview announcements

The AppSheet Preview program lets app creators try out new app features that are not yet fully supported. Learn how to participate in the AppSheet preview program for app client features.

  • No new preview features were released today.

What's currently available in the Preview program?

Item Description
Feature Google BigQuery data source

For details, see the official announcement on the AppSheet Community.

Feature Table view

Table View now supports freezing the first column while scrolling horizontally. For details, see Freezing the first Column of a Table View - in Preview Program.

Feature Chart Editor

App Creators can now make use of our new chart editor and the new and improved charts it can create. Learn more.

Feature Filters in AppSheet applications
  • App users can now filter items from a collection of records based on column values. The feature is available both on mobile devices and desktop computers. Learn more.
  • In the Search box, you can now filter by label.
  • Strings in the filtering interface, such as Done, Clear, Contains, and so on, can now be localized under UX > Localize.
  • In filtering, Yes/No attributes now support custom Yes/No display values.
  • App users can now search by columns of type EnumLists.

:+1: :+1: :+1: :+1:


What is it?


Ah, thanks @Steve

On my account, they are yet coming up.

So without copying whole app, we are able to copy data “per table”?
Can we export (not a right words though) single table to other source, like MySQL ?

Including file data could mean that the image or file type fields on that source table would be coping to new source along with the actual files (inc images.) What I tried before was to migrate whole app, including all of app related data, spreadsheet worksheet, as well as the image files sitting in a folder of source app. “Inlcude file data” window looks we are able to copy the actual files to the target account. Just wondering if any restriction in terms of the size of source folders. The app in my mind to user this new feature is holding bunch of images, like 50 k files for the moment, which is likely to fail to copy to target google account to copy the files? Is this case likely to timeout?

It’s only rolled-out to free users so far.

That seems to be the idea. Only data, not app configuration.

I’d guess so, but don’t know.

I’m afraid I don’t know. :frowning:

1 Like

Only hands-on test will be telling answers.
Sure, will test those once they become avail.


Provided that this new feature would work as I imagine, we just migrate single (or multiple table) to scale up to other sources, by coping data only, then we re-direct the source of the data for this table to the newly (copied) one. Surely, useful features I guess.


We never ever suceeded in copying whole app to other source like SQL by copy app due to errors…
for production app to scale up.
Once we get this per table feature, we could slowly migrate app to scale up.
Copy one table to sql, one table per one day while we trouble shoot if we fail to do so.


Hi @Will_Witman
The first part of this post the right hand side is cut off on Android.