Ryan
November 23, 2020, 12:56am
1
Hi guys,
My custom action is super simple,
Go Back
Open Form
It was working fine,
but this morning it started bouncing back and actually skipping step #2 .
I tried to test “Notification” as a third step, and this one is working,
So not sure what the problem is
david
November 23, 2020, 5:04am
2
I believe forms must be opened from Detail screens. Can you explain a bit more about your use case?
Ryan
November 23, 2020, 10:17am
3
Hi David,
it was all working as is this morning
Tiles (View Details) -> Custom Action that includes
Go Back
Open Form
david
November 23, 2020, 4:22pm
4
@Ryan by use case, I mean, the particulars of your app that make you want to open the form after you go back, rather than go back after you close the form, for example. Would the latter option be acceptable?
Isn’t the default behaviour to go back to the previous screen after submitting a form anyway? I don’t think that original action (Go back… Open Form) is even necessary.
That being said, other actions that take place after the form submit would be very helpful (going to a different tab, for example).
1 Like
Ryan
November 23, 2020, 9:26pm
6
I know,
I tried to go “two steps” backwards (submitting a form is one step + “go back” which will get me back to the tiles view).
Anyway,
removed the “go back” step and yet the form doesn’t open.
Ryan
November 23, 2020, 10:00pm
7
Had to recreate the same form using the same go back + open form method,
and it’s now working; not sure what the problem was.
Now I have a different issue, the mobile app is behaving differently than Glide editor,
PFA (apologies for the Hebrew )
Ryan
November 27, 2020, 3:33am
8
@david
This just happened again with two of my apps
It was all working this morning and stopped working out of the blue,
without me changing anything.
david
November 27, 2020, 5:13am
9
Strange. Can you please send us a loom.com video showing the behavior?
Ryan
November 27, 2020, 7:17am
10
Sure - https://youtu.be/Fk3O8sLKTC4
Happy to share a link to the app but prefer to do so in private.
Ryan
December 2, 2020, 12:30am
11
@david
Any update please?
This has happened across a brand new app I just built (same non-working scenario, but not nearly closed to the rows limit).
The only ways to “fix it” is to:
Deatch the actions option and move back to the old basic form option
Recreate the same form in the pre-existing action