LinkedIn
Twitter
I just learned a trick from AppSheet guru @Aleksi that I think will be very useful to me in the future.
For quite some time now, I have used grouped actions that, among other things, perform certain maintenance jobs when conditions require them. By grouping actions I can get users to trigger actions A, B, and C when they think they are triggering action A.
I didnโt realized, however, that it is possible to hide such actions in the normal behavior of deck and table views (and probably other views as well).
To do this, you need to make a grouped action for that viewโs table that has your hidden action come first and then has the normal navigation action (that is, usually going to the detail view for that record) last. The navigational action should have the following expression to open the appropriate detail view:
LINKTOROW([Type name of key column in your table here],โType name of detail view hereโ)
Then, you go to the behavior section of the view and change the default action for the selection of a row from โautoโ to your grouped action.
Thatโs it!
Hereโs the post from @Aleski the led me to this.
If you, like me, didnโt happen to know about this, but have a need to hide maintenance actions, please give it a try.
This trick was also introduced by Guru @Steve but I missed it at the time:
If you are interested in using the โRow selectedโ action to turn your table or deck view into an index for other views, check out the โRig checkโ sample app:
@Lynn told me about this a few days ago and I am only now coming to understand what a good bit of advice I she gave me.
