I see the Quick Edit feature is beta. Is it working? If so, is there a link to instructions for setting this up?
I am attempting to set up a Quick Edit view to allow a new Volunteer to rate a list of ten Abilities. I am using the AppSheet native database. I have four tables for this use. The idea is to have a new Volunteer fill out an application form. After saving the applicatiion the volunteer is presented with a view listing ten abilities and a column to rate each one. I have everything working except the ability of the Volunteer to edit/see the dropdown values for the Ratings. Gemini has given me several suggestions and changes, however, none have worked. I tested the dropdown edit in the Detail View and it is working.
Thanks. I have seen that as well. AppSheets has changed since that article. The functions listed are no longer in the interface. I switched to the Legacy Editor and none of the options shown exist. Currently there is a switch you turn on for Quick Edits and the description says it is in BETA. So, I am guessing I have to wait until it starts working. I have sent an email to support and will wait to see what they say. Thanks again.
Umm… Except for the very last instruction on the page (which makes no sense at all), it looks right to me.
Although in beta for years (a decade, even?), it’s as stable as any general-availability (GA) feature. I have no qualms using it.
Please share a screenshot of the configuration for the detail view, and a screenshot of the configuration screen of the column.
I advise against using AppSheet Database. Google Sheets is better in every way. I’m not saying it’s the problem here, though it might be. It’s just a bad product with lots of problems.
Thanks for taking a look. I hate to hear the Appsheet database is not a good product. I am in the middle of trying to build and app for user by our Home Repair Ministry through our church. I am not a programmer, but have been playing at AppSheet for about a year. I currently have many tables and three apps in process. Nothing is live, I am still trying to get the workflow and team needs finalized.
Anyway, thanks again for the look. I hope these are the screen shots you wanted to see. I have two from each requested view.
OK, you’re talking about Quick Edit in table views, but @Jose_Arteaga and I were referring to Quick Edit in detail views. That’s why the doc confused you.
When you enable Quick Edit for a table, an edit icon is added in the action bar at the top of the table view:
The user has to click the icon to activate the feature. While active, the user can edit any column value that they’re allowed to. To save their changes, they must click Save. To abandon their changes, click Cancel or the X button.
Thanks for the clarification. I will play with those views and settings and see if I can get them to work. I was hoping for the Table View look to display two columns. Column One would be the Ten Ability Descriptions and Column Two would be the Rating Dropdown column the user would edit. I am looking for the easiest and cleanest way for a user to interact with the edits. I don’t think the Table view option will work. Too many clicks. I will try the Detail View. Thanks for the quick response and help. Much appreciated.
Help filtering Linktoview. This view should only show the ten rows newly created when the user saved their application and sends them to the Table View to rate abilities.
I decided to give the Table View as try. The problem I have run into at this point has to do with filtering the Abilities to Rate form, being presented to the applicant, is not filtered. All rows from the Volunteer Ratings of Abilities table are being shown on the form.
As a reminder, I am using the AppSheet native database. I have had problems linking/passing the Volunteer’s ID in expressions. I have tried expression suggested by Gemini, like [_THISROW], CONTEXT, a virtual column attempting to capture the newly created VolunteerID key.
Currently, this is the expression I am using in my actions to link to the VolunteerID,
How is the user getting to the view? You mentioned LINKTOVIEW(), suggesting the user is clicking an action button. If so, you could use LINKTOFILTEREDVIEW() instead. Otherwise, you’d probably want to use a slice with an appropriate row filter expression.
That you are using AppSheet Database is irrelevant here.
To offer more help, we’ll need screenshots of whatever configuration controls what you’re doing now to present the list, like actions and/or views.
