I was reading Alan Lepofsky's blog the other day when I stumbled arcross his post on Column Sorting. Yes, column sorting is great. Not sure when it first came out but I know I've been using them for at least 5 or more years. However, (there's always a "however", right?), they don't work with single category views!
Single Category views have been around since the beginning of R5. You can set one up by either using Domino Designer to embed a view and then set its "show single category" field, or you can use the &RestrictToCategory=x URL argument for a view. The one thing I have never liked was the fact that you could NOT resort columns WITHIN a category and you couldn't do a "Starts With" within a category (&StartKey=x, for the web).
A couple of years ago, I got this SPR'd (SLED5KLMXU).
SLED5KLMXU: Use &RestrictToCategory with either ?OpenView or ?ReadViewEntries precludes other optional arguments
However, from the wording of the SPR, I think they've closed the SPR but didn't fix the bug. I've been told by a couple of Managers at IBM/Lotus that the functionality I'm wanting is considered an enhancement. Well, like all enhancement requests, you can't get them to the top of the priority list without a LOT of people wanting them. So you tell me, would you want this "feature"? Would you want to have true "mini-views" that have the full capabilities as normal views? Or, am I just dreaming like my dream for ?SearchViewEntries
SURE !!! Would ne killer !!!
I run into this limitation all the time, and I wish it would get fixed. The "RestrictToCategory" feature is great for displaying information for a specific user, but it is so limiting when you can't provide the additional functionality.
I'm sure this falls under the very hard to implement category but it would be great. Pull up an uncategorized view in a picklist and you can sort on any column that has a sort on it. Soon as you put a single category on it and the sort doesn't work. Same with embedded views. We've ended up creating many views and then embedding them in tabbed tables... not the prettiest solution.
True mini views - now that would be really useful.
I agree with Les. This would probably be very difficult to implement for Lotus/IBM, but would be very useful.
Yes, go for it!
Downgrading ain't the future.
It's year 2008, LN 8 is out, web 2.0 applications are customer required, but the same bug has been remaining unsolved. I agree with you Jack, this feature is "must" and IBM should not keep overlooking this problem. Our company uses ?ReadViewEntries together with OutputFormat=JSON. I created ViewGenerator, which by Ajax calls ?ReadViewEntries&RestrictToCategory=all_&OutputFormat=JSON gets data from server. Even though the Ajax works great and it simplifies development, I also need to sort data within the category and this is impossible, as you mentioned, because ResortAscending/ResortDescending doesn't work. In nutshell, you have my full support Jack. And IBM please wake up!
@Barty - yep, I still can't believe that this issue hasn't been fixed. Well, actually, maybe I can believe it since IBM doesn't think it's a bug at all and that the behavior we want/expect is considered an "enhancement request" as far as they are concerned. The question is how can we convince that this "enhancement request" is wanted by enough developers/companies/business partners? This blog post is over 3 years old so I think I'll blog about it again and perhaps with planetlotus.org picking it up more people will chime in and perhaps someone at IBM/Lotus will read it again and say "aha! yes, we *should* fix that!" :)
I cannot agree more that this is a nagging issue that should have been resolved years ago.
Thanks!