In my situation I have collections nested. So the "navto://relative/parent" works over the higher level navigation of "navto://collection/[collectionname]?openTo=browsePage" which only works at top level ( A collection you can access directly from the landing/opening part of your app).
This is really mind boggling. We have a collection that contains a collection with articles. The parent collection cannot be accessed from the articles by direct linking via navto://collection/[collectionname]?openTo=browsePage
But navto://relative/parent works. But it is always leading to the collection, even though you said it would lead to the previous article if you came there by a navto link. That is not the case.
So everything is working for us as we would like it to. But I find the behavior so strange as it differs from every documentation I read, including your posts, Bob. Does that have to do with the nested collections?
I think you have that reversed. The Collection Name isn't allowed to have spaces. Try the link with BEPADM.
You can try using navto://relative/parent, which is like a back button. It works if users tap a card to open an article, but if users tap a link from a different article, tapping the link takes them to the previous article, not to the browse page. I think you want to get the navto://collection link to work.