SP 2010 and Nintex 2010
Sorry for the detailed question, but since I couldn't find info on this issue by searching, I thought I should be as detailed as possible so that it would be clear that I have done my due diligence.
We are currently running SP 2007 but have some test servers running 2010 for learning. Since we had experienced issues with 2007 on large lists (>1000 items), one of the scenarios we wanted to evaluate under 2010 was this matter of large lists. Pretty quickly we found that Querying (using Nintex Query List action for example) tended to return fewer results than it should.
I took a list from our SP 2007 environment and exported then imported into 2010 using the spreadsheet import. My test was going to be iterating through the items where a particular name field X was non-empty, and do a Query LDAP to get the Display Name for each of those. My goal was to see how Nintex performed against large lists and to see how the LDAP query performed.
So my query was set up to filter where x is not null. Taking it slow, I first just had it report back the number of matching items and stop after doing the query ldap for one hit. (The LDAP query was successful.)
What I noticed was that the count was incorrect by a significant amount. It was almost as if the thousands units had been truncated. A coworker tried a similar query using .NET and the SP object model, and also got incorrect results. He then eliminated the filter from his query and got correct results. I eliminated the filter from my Nintex Query, and still had the problem.
I then changed to a different list and changed to filter on a text field, and still got incorrect results.
Is this a known issue, or a known constraint that we need to work with in 2010? If so, how do we work around it?