One of the things that I find I need to do often is to jump to a page of data from multiple different pages. In order to return to the specific page it jumped from say with a "Back" button, I use multiple views with copies of the data so it appears to be going to the common page. It actually going to a duplicate view in the page group. Then the back button key can be defined to return from whence it came on the specific view. This all works fine but I find I am duplicating a lot of pages and in some cases I have to duplicate state machines to keep things working.
It would be nice if there was an option in the "Show View" to return from the source. Some kind of return linkage. This would avoid a lot of redundancy in pages and machines. So if you come into a page from another page using the show view feature maybe it could remember the
page it came from since it probably was done with a show view event.
Maybe I am doing this all wrong to begine with.

You can use a relatively simple state machine and 2 variables to store your current page and the page you just left, so you will know where to return to.

Attached is a sample config. The back button is the one in small print in the lower right. The button text is the previous page.

You just have to call an event for changing pages, rather than just changing views.

Another alternative is to put the data page you're navigating to on a layer above the other pages. This way, when you navigate to the data page, you're simply switching from a blank view to the data page view on a higher layer without navigating away from the original page on the layer below. Then you can make your "Back" button just navigate back to a blank view on the higher layer, and you'll be able to see the original page on the lower layer since it was there the whole time.

I'm not sure if you're already using your layers in such a way to make this difficult, but if it is a simple configuration, this is a quick and easy solution.