I’m including a Feedback form in most of my apps and I’m putting the link to the form as a tab in the Menu. The way I currently do it is that I have the tab open up a page with a button on it (nothing else). The button links to a form. Is it possible to have a tab that goes directly to a form (so it would act like a button, and not a tab, I guess).
1 Like
May have figured it out… the form fields can just be added individually as components when using the Details view. I think this will work for me.
Scratch that… those fields just let the user enter data, not submit it as a form. I guess I didn’t figure it out. See original post for question/feature request if it doesn’t exist somehow.
I don’t see a way to have just clicking on a page tab open up a form in edit mode. What you are doing is it. You could put that button on any details page, so it doesn’t have to be a dedicated tab, but I suspect you already know that.
Echoing this because I have a different use case. It would make sense to have a button not only “Link to Screen” but go to a screen that is already configured.
I’m building out a cart function and I want to have a “View Cart” button throughout the app. For each button I have to independently configure each screen with the same information. Also, any updates I do to one “Link to Screen” build, I have to do separately.
A “Go to Screen” button would be best since most apps have this functionality.
2 Likes
Or rather, a “Go to Tab” action.
1 Like
I agree!
I have weeks thinking about this and other problems associated to it
I’m not sure if this would work, but what if you created a single relation and used the relation component, or create a multiple relation and used the inline list component to act as your button. You could probably set it up to display “View Cart”. I’m thinking this might work because details are tied to sheets and lists always go to the details view that’s already been created. Whereas Link to Screen buttons and Tabs always act as a top level view, which can have a unique layout compared to the sheet and list details.
2 Likes
Jeff I think I follow but not quite certain.
I created a self relation on the sheet where I wanted to house the ‘view cart’ button. But when I placed a button with the same settings (‘Link to screen’ set to the self relation, that detail screen was different from the first one I set up on the different tab.
No, I’m thinking that using a relation component or inline list component will react differently than a button. The button is designed to always give you a new detail layout. The details of a list are designed to share the layout throughout the app.
I’m not sure is the relation would really be necessary. You could maybe get away with just creating an inline list that points to the cart sheet, which I assume would be filtered by user or something like that.
Basically the list would function as a button.
I will tell you tomorrow if your tip worked
Gracias @Jeff_Hager
1 Like
Wow this is my issue also, going to a tab MUST always bring you to the main page, not the last state (details level etc.), its not the way any app works and its very confusing! Is there any way around this???
Any help is greatly appreciated
1 Like
Thanks Jeff for the idea, it didn’t work as I hoped but your thinking gave me an idea. I will play around with this and let you know if I find a workaround.
1 Like
Your theory DOES work. I used the inline list component and set values from a sheet with only one record. From that sheet, I pulled in the relation column I needed.
Great work around @Jeff_Hager 
2 Likes
Awesome. I thought it might work, since link to screen buttons create new layout screens, but list detail layouts are always linked to the sheet, so they should stick no matter where you view the list details in the app. Glad it worked for you.
2 Likes
That’s a genius idea. I might make some dummy data to create a tutorial for people who need this.
3 Likes