I asked the other day if anyone else was having trouble using &RestrictToCategory along with other arguments like &StartKey, &ResortAscending, &ResortDescending, etc.
Am I the only one that wants this to work?
Let me know what you think. In my opinion, if we can get Lotus to fix this issue, then many of us could eliminate many many views in databases thus improving the overall performance of the database and the server.
Here’s my post from the other day:
Subject: Does anyone want to use &RestrictToCategory WITH other optional arguments???
Yes, definitely
Subject: Great News from Lotus on the &RestrictToCategory bug!!! (Thank you Steve Leland!!!)
Just to update everyone,
I was fortunate enough to get Gary Devendorf to look at this bug before he left Lotus last month. He was able to get this bug SPR’d before he left.
Here’s the SPR # and how Lotus’ defines the bug:
SLED5KLMXU: Use &RestrictToCategory with either ?OpenView or ?ReadViewEntries precludes other optional arguments
Then yesterday, I was listening to the IBM Webcast “What’s new in Designer 6 Forms and Views; plus a Designer 6.0.1 update”. During the webcast I posted the question of when this bug would be fixed. Maureen Leland was on the webcast and told everyone that her husband (I am assuming Steve Leland) is working on this very bug right now. Her report is that it is not an easy fix but it makes me feel better that they are working on it!
Everyone that wants this bug fixed should respond here giving Steve a word of encouragement.
Let me be the first to say, Thanks Steve!
Subject: Any news on SLED5KLMXU?
I searched the SPR database and couldn’t find anything. Does anybody has any news?
Subject: RE: Any news on SLED5KLMXU?
SLED5KLMXU is reported as fixed in 6.5.2 and 6.0.4 but still not working for me 6.5.2. Anybody else checked this out?
Subject: RE: Any news on SLED5KLMXU?
Yes, the crap still dont work, and regarding to this in the fixlist Db´s:
SPR# SLED5KLMXU - The OpenView and ReadViewEntries’ RestrictToCategory options no longer override the StartKey and Resort options.
One would expect this to work now… Whats up here?
Subject: RE: Any news on SLED5KLMXU?
I talked to Steve Leland of Lotus in November of 2003. At that time he said that the NSF guys were knee deep in the DB2 work for ND7. Therefore, it wasn’t a priority yet to look into this.
Also, this isn’t considered a bug by Lotus. It’s considered an enhancement request so Steve’s suggestion was to enlist one of the marketing guys (Ed Brill or Alan Lepofsky) to raise the priority of this.
Basically, if we can get enough of the Lotus community saying this would be great to have then and only then would it ever get prioritized and done.
Subject: RE: Any news on SLED5KLMXU?
For MANY years, developers have been looking for better ways to standardize
formats of views. We have proposed solutions such as a
href=“http://www-10.lotus.com/ldd/46dom.nsf/55c38d716d632d9b8525689b005ba1c0/567
4fb86c59fd55885256ccb0050b093?OpenDocument”>“shared columns”], or a “view
publisher”. SingleCategory views offers great promise. However, it’s partial
implementation makes it virtually useless. I strongly support interest in
seeing URL parameters (such as StartKey) working with RestrictToCategory.
ALSO, all Notes view functions should also work with SingleCategory views
(e.g., a
href=“http://www-10.lotus.com/ldd/nd6forum.nsf/ShowMyTopicsAllThreadedweb/39a1ba
6d81e502d685256e300003cbd7?OpenDocument”>ViewCollapseAll does not work with
@SetViewInfo]).
Subject: Frustrated… using XML with RestrictToCategory…
…and wishing I could use StartKey so that jump to new rows more easily. I mean, it works great for XML using a normal view, but once I try to dig into the single-category views (for example, a view of all orders belonging to one user) I lose StartKey and my wonderful AJAX coding becomes oh-so-much-useless-monkey-typing. Sigh.
Subject: RE: Any news on SLED5KLMXU?
It would be an enhancement in my view as well. Not that I’d complain; as enhancements go, that ranks WAY up there with things like “permit user keyboard as a data input source”. It would mark a fundamental shift in the product’s capabilities. This isn’t a web dealie – resort columns become the primary sort column in Notes as well, which precludes the maintenance of categories. It sounds to me, though, like it would also mean an architectural change at the view index level, so I wouldn’t count on it coming out in the current code stream.
Subject: RE: Great News from Lotus on the &RestrictToCategory bug!!! (Thank you Steve Leland!!!)
Yeappy Steve !A beer waitin for your here after fix is done 
Subject: No such luck 
From Steve Leland :-The spr says “So basically, if you use &RestrictToCategory, the StartKey, ResortAscending and ResortDescending arguments produce unpredictable results.”
The Designer Help database offers the following - in the topic “Domino view and folder properties that are not supported on the web”: you can’t “dynamically sort a categorized column on the Web **** OR **** in a Notes client.”
(emphasis mine)
The bug is not that those arguments don’t work on the web in a categorized view - they can’t because Notes/Domino does not, by any default I could find, keep a sub index within each category.
The bug that I fixed was that some combinations of arguments in a url did not give precendence to the RestrictToCategory argument.
Take care!
-sl
Subject: * Yes please! =B-)
Subject: Re:Does anyone want to use &RestrictToCategory WITH other optional arguments???
I spent a whole morning this week trying to get this to work.
I eventually resorted to a Lotusscript agent to get the functionality. What a pain !
Subject: Does anyone want to use &RestrictToCategory WITH other optional arguments???
I’m totally with u on this !
ps : accepting multivalue as restricted categorieS could be cool too…as for partial matches…
Subject: RE: Does anyone want to use &RestrictToCategory WITH other optional arguments???
I would really appreciate when this feature work. Otherwise, what is the reason to have parameters like ResortAscending when it doesn’t work properly?
Subject: YES! re:Does anyone want to use &RestrictToCategory WITH other optional arguments???
This is killing me.
I’d also like to be able to nest sub-categories (without resorting to a hack like concatenating the values) and pass them on the URL.
Subject: RE: YES! re:Does anyone want to use &RestrictToCategory WITH other optional arguments???
Nesting sub-categories would definitely be nice! For now, I would just be happy if they can get all of the optional arguments to work when using &RestrictToCategory.
I have one particular app that has only about a 30 main views. But for each view, the customer wants to see the data filtered out by a status field. Since there are 8 possible statuses, we have 30x12=360 views. If we could just categorize by status and do a &RestrictToCategory then we would only have 30 views to maintain, and the server would only have 30 views to keep updated.