For desktop UI (preview), fixed LinkToRow() to show the selected row in embedded detail views when linking to a non-interactive dashboard.
Bug
Fixed a bug with actions that involve showing a modal (confirm dialog or INPUT form), where a background sync completing while the modal was open could cause the action to fail.
This fix will be rolled out gradually. It is deployed to 100% of free users.
Rollout changes
None
Preview announcements
Preview feature releases enable you to try out new app features that are not yet fully supported. See Product launch stages.
No new preview features were released today.
What’s currently available in Preview?
The following tables summarize the preview features that are currently available.
Item
Description
Feature
Quick sync is now available to all users in preview
Turn on Quick Sync for an app to instantly see other users’ changes as they are saved. For more information, see:
The new desktop design, currently in preview, is optimized for desktop browsers, presenting a more complete view of information with a consistent organization and structure. The new desktop design lets users navigate their apps more easily and access information in context, and provides an efficient way to edit existing records without losing context. The legacy desktop design, enabled by default, provides an experience similar to the mobile and tablet device.
The following features require opt-in to the AppSheet preview program. The AppSheet Preview program lets app creators try out new app features that are not yet fully supported.
Could you include the release status of this fix ?
With my accounts, I still see the same errror messages quite often , so wondering the fix is not reaching to my account yet, but I also wish to make it sure by checking the release status.
As far as my own testing is concerned, it is apparent to me that this fixed has been deployed only to the free users so far. What’s your ETA? (Not asking for K-Pop song… )
I have one app which can easily repro the error (Transaction is already closed error) with my paid account. We copy the same app to the free account, then I luckily managed NOT to repro the same issue, which give me a sense that the fix has been so far deployed only to the free users…
@Koichi_Tsuji correct, it’s still only enabled for free accounts at the moment. I had an additional sync-related fix that I wanted to include before ramping it further. I believe that fix was released yesterday, so I will begin ramping through paid accounts soon. Probably will be fully in effect within two weeks if no problems are identified.
With futhure update (release note) could you keep us posted of the progress of the release to the paid users so that we can trace this important fixes?
