View or Twistie Problem

Hi;We have a web application that contains a form (AllDocuments) and this form has an embedded view. Column 1 of the view is catagorized. When the form first opens it’s URL looks like this:

Http://oursite.com/abcd3/abcd.nsf/AllDocuments?OpenForm&nav=all&cat=Seat%20Arrange/Deployment

When you click on any of the available twisties the URL changes to:

Http://oursite.com/abcd3/abcd.nsf/AllDocuments?OpenFrom&Start=1&Count=30&Expand=1&Seq=1

Several things are in question. Why is the display limited to only 30 documents and how do we change the “count=30” to unlimited or “count=999”? We simply can’t find it. (if you change 30 to 300 manually in the URL then magically 300 documents show up.)

Also there is no “next / previous” selection like on the plain vanilla quick search page. If we can not change the limit created by the twistie is there a way to add “next / previous” to the page?

Thanks for your help, it’s made us bonkers.

Subject: View or Twistie Problem

There are plenty of articles around about displaying views. For example:

http://www.codestore.net/store.nsf/unid/EPSD-66GGUM?OpenDocument

As for the default of 30 rows, it’s a server limit in the server document under Internet Protocols>Domino Web Engine>Conversion/Display

Subject: View or Twistie Problem

You can use count=0 in your urls to show all documents, if you don’t want to have an impact on your whole server.

As for view navigation, it is a little fiddly but very possible. Use the start and count in your urls, in combination with “special” cgi fields on a $$ViewTemplate for [viewname] field to work out where you are in the view and to calculate your previous and next urls.

HTH

Andrew

Subject: SOLVED – View or Twistie Problem

Thanks to both Andrew and Dan. It doesn’t look like they said much, but their comments were jam packed with information for me.Just to clarify what Dan said about the Display Count being set on the Internet Protocols tab. If you have an Internet Site document go there first and open your Internet Site doc > Domino Web Engine tab > and see Conversion\Display right below the HTTP Session block. Until now I have never messed with any of those settings. I’d set the session authentication and then move on.

So my app is fixed now and next I’m going to try that article that Dan referenced in his reply. Thanks again.