I have several views in different databases that are to show documents posted within a certain data range…the last 14 days, 30 days, etc. I’ve set this up using the Simple Search option for the View Selection conditions. I add the condition to view documents:
By Date
Search for docments whose…
date created is in the last xx days
Initially the view documents are correct but after time passes, I notice that documents created before the filter range are still showing up. If I go into Designer, open the condition and click Add Condidtion again and refresh the view, then it once again shows the correct documents. Refreshing the view in the Notes client does not effect what is displayed. Is there any way to get this feature to acutally work?
Do you have a TodaysDate on the form you are using? Are you updating the day everyday to the current day? If so, use the TodaysDate value and compare it with when the documents (14 days, 30 days, etc.) and use the results to determine documents displaying correctly in the various views.
Do not create an agent to assign today’s date into a field in each document daily, as Michael suggests. That’s really bad news for replicated applications. You can write agents to flag documents for inclusion in a view, but don’t modify documents unnecessarily.
The problem is that the server doesn’t recognize that this selection criteria might give a different result for the same document on different days. Unless documents are modified, it doesn’t bother to recheck them to see whether they should still be in the view index.
To force this, you can change the view properties to discard index “after each use”.
Or, you can just write a view selection formula that uses @Today – the server will recognize this as meaning that the view contents have to be rechecked each time it’s used.
This has consequences for performance. See this article and this redbook.
Thanks for the responses. While these databases are not being replicated now, they may be in the near future so it sou nds like the Today’s Date option isn’t advisable. Basically it sounds like while Lotus builds in this View Selection option, it doesn’t really work as one would expect.