For desktop UI (preview), fixes keyboard navigation within EnumList chips. Previously, keyboard navigation with the left/right arrow keys wouldn’t work on chips in the EnumList for the desktop UI. They are now supported, allowing users to quickly traverse through their selected items using the arrow keys.
Bug
For desktop UI (preview), fixed a bug causing the app to freeze when running some looping actions.
Rollout changes
Item
Description
Bug
Fixed an issue with copying apps to team shared data sources.
New: Deployed to 100% of free users and 30% of paid users. Previous: Deployed to 100% of free users and 10% paid users..
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
AppSheet databases (Preview)
The new AppSheet database feature is now in preview release. An AppSheet database is a first-party, native data source for organizing and managing data powering AppSheet apps. An AppSheet database provides an easy and efficient way to build data models for any AppSheet app without needing to use an external data source solution such as cloud-based spreadsheets or databases.
Navigation improvements in AppSheet app editor (Preview)
The app editor includes navigation improvements, currently in preview, to facilitate the configuration of specific features. For example, the new Settings section in the left navigation gathers together all app-wide settings and makes it more intuitive for all app creators to find these types of settings.
Additional usability improvements in AppSheet app editor (Preview)
The app editor includes navigation and app setting improvements, currently in preview, to facilitate the configuration of specific features. The navigation improvements now include a secondary navigation panel that lets you quickly scan all of your components. In addition, there are more direct links in your View component to the table, column, or action that you want to check or edit. Finally, error and warning messages are more prominently displayed in the app.
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.
@lizlynch , Thank you, my looping approach is now working on all platforms. Associated child tasks from selected follow up are all created with save and no freeze now. So in my case solved.
Have you also noticed the same looping action works fine in editor but not in desktop UI and automation bot. How much ever I explain they are not understanding.
I just have a looping action and child table has initial value. Its not fetching that formula value anymore in automation and desktop UI. If it works in editor it must work in both Automation and Desktop UI.
I just got an email from support there is no issues in my looping action anymore. But it still doesn’t work. My request to appsheet team is please make one feature consistent. It was all working before in automation bot. @SkrOYC
This is because the Emulator has the Mobile Mode, not Desktop Mode. Try using the Desktop Mode Emulator view.
As a workaround I’ve been using the Mobile Mode in Desktop by forcing it using DevTools, which is basically the same as using the Emulator (preventing Desktop Mode from being triggered)
Hi @Rifad , sorry it’s taking so long to figure this out. I saw the support ticket and took a look at the app. I found that the Purchase Order rows not being generated in Desktop mode is related to a known issue with the form view not updating certain computed columns after adding related rows through a child form. The condition expression of the looping action that generates the purchase orders depends on computed columns affected by this. A fix for the form behavior should be coming early next week, which will hopefully resolve the inconsistency when the action is run in Desktop mode (I could at least confirm that the Purchase Order rows do get generated after applying the fix).
The same problem could have affected automation when the automation is triggered by form saves in Desktop mode because it relates to the values being sent for the row rather than the action evaluation. However it sounds like the automation is still not producing the right outcome even when triggered from mobile / editor preview, which would imply there is still a different problem specifically with automation.
Part of the challenge of debugging this is I’m not sure exactly what to look for as far as an anomalous vs correct result. The form save runs several loops which create rows in multiple tables. Lack of rows being generated was conspicuous enough to notice the difference, but when you said for example
“I just have a looping action and child table has initial value. Its not fetching that formula value anymore in automation and desktop UI.”
Can you tell me the names of the specific looping action and column you were referring to?
@SkrOYC Are you still seeing certain actions cause the app to completely freeze? If so, can you show some screenshot of the action configuration (particularly the condition expression)?
Or do you mean more generally having issues with some actions (e.g. not producing the expected result)?
@Adam-google Thanks for looking into the issue and got someone who understood the issue after struggling for really long time. Yes I have shared bot details and screenshots in the ticket. I will provide more details with exact issue once again for easier debugging.
@Rifad The ticket I saw mentioned a column called List of Bill of Materials being empty, was that the same column you meant above? The screenshots showed it set by the action rather than by an initial value formula, so I wasn’t sure if you meant some other initial value is not computed either.
Yes both has issues. The initial value issue is also having issues there but I lost track of multiple tickets and bugs. You are right [List of bill of materials] is returning empty when adding using automation.
@Rifad I didn’t see the initial value mentioned in the ticket I saw. Can you tell me which column has the initial value you’re referring to, and which action or loop generates the row with the initial value?
Also a change should be in effect for you now which I believe should fix the purchase order rows not being generated when the action is run in Desktop Mode. Can you let me know if you see any improvement?
@Adam-google good afternoon, do you know if this issue was fixed for it has started to show for us since early December but just figured it out today that the issue with the Loop is in the Desktop preview.
Have a loop that creates a row in a Parent table and Child rows that stopped working in the new desktop view but works fine in the editor and old desktop view.
