Grouped Action: Delete and Navigate

[Fabian_Weller]

It has been reported that you cannot use a grouped action that

1. Deletes a row
2. Navigates to a view

The Grouped Action stops after the Delete.

I understand that you cannot navigate to something that uses the ID of the deleted row.
But a simple LINKTOVIEW() action should work.

I would call this a bug, what do you think?
@Steve Should I contact AppSheet Support?

Would it be possible to add more control of w... Questions

@tony It doesn’t seem to work. I have tried the second action alone to make sure it works and it does navigate to the correct view but when I use it after a delete action in a group it doesn’t seem to fire. The view just moves to the next record.

What is best approach for Parent Updates in UI when making Child Add/Edit/Deletes? Questions

With persistence and few hours of trial, I have created a way to workaround the shortcomings identified above and allow for Add/Edit/Delete changes to Children, regardless of how you access them (well not quite with Delete) and still apply updates to the Parent summary fields. Adds/Edits The idea is when any Adds/Edits are made to the children directly, force the Parent Form to show so summary functions there can be executed. This navigation is accomplished by adding an Action on the Child F…

Redirection after a delete action Questions

Hi Appsheet fanatic, [2020-04-29_22-22-51] When having a button linked to the above grouped Action, the system is able to execute the first action (delete the current record) but the follow action (redirection to another page) is not ran. Obviously, if I swapped the order, the redirection happens but the record is not deleted. How could I do that? Thank you!

Sequence of actions issue Questions

An action is associated with a row. The row must exist in order to perform an action associated with it. After you’ve deleted the row, the row no longer exists to perform the navigation action.

[Steve]

I wouldn’t call it a bug; yours would be a feature request.

[Fabian_Weller]

OK I changed it to a feature request.
I thought it is a bug because Tony once said that we should be able to do this.

Would it be possible to add more control of w... Questions

@Cory_Chapman You should be able to have a grouped action that performs the delete and then navigates to a view in your app using a deep link. The actions must appear in that order in the grouped action (delete first, then navigate). In group actions, a navigation action cancels all subsequent actions in the group. Maybe that’s the issue? help.appsheet.com - Column Type: App (Deep Links) Column Type: App (Deep Links) help.appsheet.com

[MultiTech]

Whenever I brought this up the response that I received was something along the lines of:

• after you delete the record, there’s no longer anything present in the system for anything to work off of or on.
  • you’re literally deleting the thing that the computer is using for all of the operations.

Hence why everything after the delete action fails.

---

I agree though, I think the stack should still be able to complete itself.

If you set up something similar in automation, any subsequent actions that fire off after the delete still work.

[Fabian_Weller]

Thank you @MultiTech_Visions for your insight.
I think at least a LINKTOPARENTVIEW() should work.

[WillowMobileSys]

If you are looking for a workaround solution sooner, rather than later, you could introduce a [Delete?] column and in your Grouped Action simply mark the row for deletion. Later, run a scheduled process to remove all rows marked for deletion.

This does require you to make adjustments to remove “deleted” rows from datasources or views.

[MultiTech]

WillowMobileSystems:

you could introduce a [Delete?] column and in your Grouped Action simply mark the row for deletion. Later, run a scheduled process to remove all rows marked for deletion.

This is actually a really good idea for replacing the standard delete action in appsheet.

• Especially if you’ve got “AppSheet Uninformed” users - meaning someone that’s not that knowledgeable about AppSheet - including a (delete queue) sort of thing can really help smooth things out.

• It adds in an “Un-delete” buffer layer into your app, in case someone makes a mistake.

[WillowMobileSys]

I'd like to see this get more attention.  To a slightly different dimension to this problem, I added this Feature Idea to use Slideshow to default navigation behavior.  It only covers certain app usage scenarios but may eliminate the need for some custom delete actions with navigation described above.

https://www.googlecloudcommunity.com/gc/Feature-Ideas/Tie-navigation-after-row-Deletion-in-a-Detail-...

[Kirk_Masden]

I just voted for this, though I would like to do something different.  For reasons I won't try to explain here, I would like to save the key of a row to be deleted for future reference -- before the row is gone.  I can make a grouped action but, if I do so, it will not appear in the top row (with the sync icon) as it does now.  If AppSheet would allow us to put grouped actions in the top bar, this problem would be resolved for me.  😞

P.S.  Apparently, AppSheet is planning to add the kind of functionality I'm looking for.  I hope it comes soon!

https://www.googlecloudcommunity.com/gc/Feature-Ideas/Action-prominence-display-options/idc-p/544062