Domino View Count Limitations

Recently I replaced some code which was using a couple of @DbLookup calls with an embedded view in a customer's web application. The application was using the @DbLookup to pull a list of products (which was a unique group of "favourite products", and was different for each user) into a web page, and sure enough it didn't take too long before the list exceeded 64kb. The @DbLookup was simply populating a keywords field, so I replaced this with an embedded view rendered as html which generated an options list. Everything worked fine, and it looked like I'd fixed the problem.

A couple of months later, the customer reported to me that the product lists for a couple of users were cutting short. Initially I thought that the cause might be a "bad" character causing the html to prematurely close a tag or something along those lines. The actual cause turned out to be slightly more embarassing.

My previous fix was working so well that the users had been able to keep loading products into their favourites list, and so some of them had exceeded 1000 products - which happens to be the default number for the "Maximum lines per view page" setting. I'd seen this setting before, but I'd never had to change it. I'd also set the Embedded View to show 9999 documents, and so it took me a few minutes to realise that this server setting is the one which takes precedence.

If you don't use Internet Site documents, then the setting will be in your server document under "Internet Protocols\Domino Web Engine". If you use Internet Site documents, then you need to update it in each site under the "Domino Web Engine" tab. Once you've made this change, simply restart the http task (tell http quit / load http), and your web views will once again be complete.

 Print | Posted on Sunday, October 29, 2006 8:19 PM |