Hey @trz-justin-dev, the team is looking to support copy/paste pages in the near future, which would allow you to transfer pages between apps easily! Will let you know when it's shipped
3 Likes
@ming Love the new feature and am trying it out now. One problem I've noticed is that it seems that components can't have the same name even if they are in different pages which are supposedly suppose to have their own scope.
For example, if I have a user_table component on one page, then can't have another component on a different page within my multipage app called user_table as I get the error telling me it already exists on another page.
This is a real shame as it means that we'd have to give things random names on each page. I can understand why names can't clash at a global level but between pages seems unfortunate.
1 Like
@marcus_sohonet Totally get the issue and it's something I've run into myself numerous times. The team is aware of the issue but has deprioritized it for other bug fixes and feature work. In the meantime one suggestion is to rename the clashing components to have their page name prepended, for example: page1_user_table, defaultPage_user_table. Know it's not ideal!
2 Likes
@ming thank you for adding such a great tool! It is great to see that Retool adds more and more new features.
I started to use multipage app for our new project and encountered an strange issue. As one of the flow steps user in our application is asked to input data in few fields to make required calculations. Results of those calculations presented on the next page. I should give the user to go back to previous page and change his input. Unfortunately, all the inputs lose its data once the user leaves the page. Is there any option to save inputs values on the previously visited page or I will have to find workaround?
2 Likes
Hey @MichaelT ! Glad to hear you're liking Multipage 
The issue you outlined makes sense and is something we've heard a couple times in the Beta. Right now in Multipage, when you navigate away from a page, that page's information/context is all dropped and if you navigate back to it then all the queries have to be re-run, components re-rendered, etc.
The team plans to work on a 'Page caching' feature in the future that allows past history to be preserved which I think would also solve your use case, but we haven't been able to prioritize the work.
In the mean time, you could write the input values to global state variable/local storage/url params via event handlers, that way the value is persisted between page loads
1 Like
Hey folks 
thanks so much for all of the feedback so far! Glad to hear there is so much interest in multipage apps 
Please keep the feedback coming!! Since this thread is getting a bit long and tricky to read, I'm going to ask that you start creating new app building or feature request topics as you have more feedback to share 
New topics will be easier for fellow community members to chime in. The Retool team will continue to follow up on any bugs that you share with us in new topics as well.
2 Likes