I implemented a partial text search as outlined in this article: http://www.wonderlaura.com/Lists/Posts/Post.aspx?List=daba3a3b-c338-41d8-bf52-cd897d000cf3&ID=77&Web=dbb90e85-b54c-49f4-8e97-6d8258116ca0
Basically using partial text filters that push query string parameters to the Data View Web Part. The DVWP is using an XSLT filter that refers to the values supplied by the textboxes. The challenge that I'm facing is thus. The stakeholders want to limit the DVWP to showing 10 rows at a time. If I do a search and the item is not in the 10 items that are showing the user gets a blank view. However, if you click on the next page the item is there. Reason being is that it's on the 2nd page page to begin with.
I've been trying to manipulate the XSLT, by setting a cookie when the user searches, then having the DVWP refer to the cookie value 'Search=bool'. So that part is working. However, I've been trying to fake out the DVWP by setting $RowLimit=0 or $LastRow=100, to no avail. I'm stumped on this one and would appreciate any recommendations to disable paging if 'Search=true'. Or perhaps there's a property setting that I'm overlooking?
Toggling Data View Web Part Paging at Runtime
jive137
- 1
- 2