KB35910: How to hit caches with Dynamic and Static dates in MicroStrategy Intelligence Server

SYMPTOM:
Strategy product administrators might wish to take advantage of Update Cache subscriptions to pre-generate caches. When these caches are generated using dates (e.g. Date and Time Value prompt), only certain answers will allow these caches to be hit, thus it is important to understand them before creating the subscriptions.
 
Consider the following example.
 
In the Strategy Tutorial project, a report containing Day, Region and Revenue has been created. This report also has a Value prompt on Date.
 

 
The following option has been selected in the Project Configuration that contains the previous report in order to avoid expiring automatically caches geneated with dynamic dates.
 

 
 
Considering in this example that the current date is March 22nd, 2009 and a cache is created using "Today + 1" (dynamic instead of static date), the value prompt answer will be labeled as "Date 23/03/2009"
 

 
  
The next day, Mach 23th, 2009, if a user executes this report answering "Today", he will encounter that it is not possible to hit the cache generated the day before; instead a new cache will be created. Notice that in the cache monitor the prompt answers for both caches will appear to be the same.
 

 
The original cache won't be hit even if the user answers with the specific static date (e.g. "3/23/2009").
  
CAUSE:
 This behavior is expected. The way the prompt answers are stored in the cache are not necessarily the same that are shown in the cache monitor.  Anwers have to be stored in the cache exactly as they were given by the user (e.g. "Today + 1") thus dynamic dates are stored as dynamic dates; however, we do support to hit caches created with dynamic dates with static dates in some cases. Using the previous example, a chart with the possible scenarios on which a cache can be hit is shown below:
 

 
ACTION:
In order to pre-generate caches that use dates to be used in the future, it is better to use static dates rather than dynamic dates as this option allows more scenarios for the cache to be hit.