Hi everyone!
(First time posting… Long time follower!)
Absolutely love the new NavBar at the bottom. Except for one thing I can’t figure out. I’m not a coder so, perhaps this is likely obvious to everyone else but me.
Anyway, assuming a non-logged in user arrives on a first page with a NavBar with 2 tabs, and, the first tab, where they first land, contains a recordID up in the first block which is a details block…, and then, they click on the NavBar tab to the second page at the bottom,… it will not carry over that current recordID.
I assume this is standard? Is there any way to carry that current record from the first page over to the second page via the second NavBar tab? The user in this case is not a logged in user.
Is there any way to code for this? Potentially using the device’s localStorage? I tried some [chatGPT] codes but none seem to work. I believe this may be possible using the rest API but I’m also not sure how to do it that way.
The obvious way is to have that functionality be done via a list which brings you to a list details page… but, having the NavBar now, I think this ought to make for some good UI navigation.
Anyone else see this as a super-necessary feature? Or is this just a big No-No overall?
Would love to hear anyone’s thoughts on this. Thank you all in advance!