Well, I have a new challenge for this subject. What about when the docs contained in that view has a............. reader's field (!!!!!!)
I spent days and days trying to solve this, because in a standard view, the navigation next and previous works wrongly. So, I think is not possible manipulate the position in the view to navigate trough the view.
The only solution I found is categorize the view with that reader field. Then, I embebed the view in a form and set the "show only one category" with the CN value of @UserName. This let you use at least the standard previous and next buttons properly. Otherwise, the next button works right but the previous doesn´t. I think this is logical because you may be founding docs that you are not able to see because the reader field. It's very different in this aspect to navigate a view in web rather than in notes.
Please, I need a Guru to make a complete article about using reader's field. We are having performance troubles in large views. It's a good point to give your docs truly security, but upsets users that have to navigate that views. God bless that possible article!!
Well, I have a new challenge for this subject. What about when the docs contained in that view has a............. reader's field (!!!!!!)
I spent days and days trying to solve this, because in a standard view, the navigation next and previous works wrongly. So, I think is not possible manipulate the position in the view to navigate trough the view.
The only solution I found is categorize the view with that reader field. Then, I embebed the view in a form and set the "show only one category" with the CN value of @UserName. This let you use at least the standard previous and next buttons properly. Otherwise, the next button works right but the previous doesn´t. I think this is logical because you may be founding docs that you are not able to see because the reader field. It's very different in this aspect to navigate a view in web rather than in notes.
Please, I need a Guru to make a complete article about using reader's field. We are having performance troubles in large views. It's a good point to give your docs truly security, but upsets users that have to navigate that views. God bless that possible article!!