Now, using db.Search with the view selection formula, I correctly get 4
documents. However, if the view is collapsed when you open it, there are only 3
entries, for the categories; If the view URL contains &ExpandView, I get 11
entries for the fully expanded view. This is even if a document is not
duplicated in the view.
To take a perverse case to illustrate the point, what happens if the view
contains a single document appearing under (say) 25 categories, and we show 5
entries/page? db.Search will give a count of 1 => 1 page needed, but the
categorised view will have 25 entries (fully collapsed) and 50 entries (fully
expanded), implying 5 pages and 10 pages respectively. I know the example is
contrived, but in real systems, you can duplicate my first example in this
comment to see where the problem is.
Thanks for the quick response, Jake. Consider the following view hierarchy:
Cat 1 Subcat 1.1 Doc 1 Subcat 1.2 Doc 2 Cat 2 Subcat 2.1 Doc3 Cat 3 Subcat 3.1 Doc 4
Now, using db.Search with the view selection formula, I correctly get 4 documents. However, if the view is collapsed when you open it, there are only 3 entries, for the categories; If the view URL contains &ExpandView, I get 11 entries for the fully expanded view. This is even if a document is not duplicated in the view.
To take a perverse case to illustrate the point, what happens if the view contains a single document appearing under (say) 25 categories, and we show 5 entries/page? db.Search will give a count of 1 => 1 page needed, but the categorised view will have 25 entries (fully collapsed) and 50 entries (fully expanded), implying 5 pages and 10 pages respectively. I know the example is contrived, but in real systems, you can duplicate my first example in this comment to see where the problem is.
Once again, thanks for sharing.