Windchill 10.x search behavior - large results

[MikeLockwood]

We're still struggling with many things in preparation for upgrading to 10.1 later this year.

When search returns more than 2000 results (can be configured), the system:

- Tells you there are more but not how many total. This seems absurd - it should at least tell you the total number up front.

- Allows you to sort the first page of results (e.g the first 2000 retrieved which are the sequence retrieved from the database, not for example when created).

If you sort the first page it sorts what is there. This is ok in general but takes some caution. We just did a test search for Change Requests with a few criteria and got 2560 results. Then we sorted (the first 2000) for Created On, and got results from 2009, 2010 and 2011. After selecting Next and sorting again, we got results created in 2012.

Not saying this is a bug, but wondering if anyone else has exercised this and has comments.

Note: We're now testing some downloading of search results to file before and after selecting NEXT.

[AL_ANDERSON]

For searching for 1000s of objects for the purposes of things like
reporting, we use query builder or other reports instead of search. For
100,000's of records, we only use SQL or reports that we write that go
directly to the database since processing that many records in a report is
generally is too slow otherwise.

For me, if I had a user who needed a report of all ECRs created in 2009,
then I'd write a Query Builder report, not use Search.

Our configured limits on queries are

For all Searches: 15,000

For front end method servers for non-search query limits: 150,000

For the back end server only: -1 (unlimited in order to do queue
processing, particularly for publishing)

Al

[AL_ANDERSON]

Sorry, I had a typo.

For all Searches: 150,000
For front end method servers for non-search query limits: 150,000

For the back end server only: -1 (unlimited in order to do queue
processing, particularly for publishing)