So recently I saw the infamous message about getting close to the 5,000 item limit. After spending a couple of days doing some testing, it seemed like the best option would be to simply Index the Modified date and add an additional filter to all my views of "Modified >= [Today]-180"
Basically it takes a bit over 6 months to add 5,000 records. This seemed to do the trick until another Microsoft 'feature' bit me yet again.
Apparently, although [Today] is supported as a valid filter for Views, it makes the view ineligible for Alerts the moment you try to do any math on it.
By ineligible, I mean that when a user tries to sign up for specific view, there is a drop down that shows the views associated with the particular list...
Modified (Indexed) <= [Today] --- This will show up in the Drop Down Modified (Indexed) <= [Today]-90 --- This will NOT
At this point all I can think of is to fall back on the same method I have done for all of the SharePoint shortfalls I have come across... running scheduled PowerShell scripts.
All I can think of is to create a Hidden Yes\No field for all my list called "ExceedsViewThreshHold". Then Index on that column and change all my view so that the 1st filtered field is ExceedsViewThreshHold = No.
Then Daily I would have to run a PowerShell script that would go through every item in every list and look at it's last modified time. If it exceeds over 6 months.. set the value of that field to "Yes".
I believe it shouldn't be too bad only because I can create a CAML query in PowerShell to pull only those records who's value is currently set to "NO" and who'd Modified Date is Older than 6 months.... I shouldn't get to many results especially after the initial run.
Anyone have any better ideas? Options?