Now that I have a bit more time, I’ll further explain a navigation table/gallery setup I have in mind that may suit your needs. You appear to want to mix more complex deeplinks, like linktoform that need extra parameters, with simpler ones like linktoview, in the same navigation gallery.
Now it is entirely valid for you to manually input deeplink urls into an App-type column for each record, but that requires a bit of backend work, generating and double-checking each URL. Doesn’t sound too fun to me, but I can see an argument for it.
What I propose as an alernative would have a column structure such as:
key | Display Name | View Name | type | col1 | val1 | col2 | val2 | … | link
Then use an app formula for the link column such as:
IFS( [type] = “simple” , LINKTOVIEW([view name]) ,
[type] = “form” , LINKTOFORM([view name] , [col1] , [val1] , [col2] , [val2]) )
Now what this does is allow you to generate new navigation selections from inside the app by just filling in the fields. I hope you get the idea and can expand/tweak it for your needs.
You mentioned using a virtual column for your link formula. You can achieve the same by putting the formula in a real column, you just have to open each existing record to edit and save it. A virtual column will calculate every sync, but the real column will only calculate when editing that record, and thus will be more efficient, although if we’re just talking about a small number of navigation records, you probably won’t notice.