KB31815: When a Report Services Document is sent to History, the underlying dataset cache is only of type "Matching" in MicroStrategy 9.x

SYMPTOM:
When a Report Services Document is sent to History, the underlying dataset cache is only of type 'Matching' in Strategy 9.x
 
For details on Report Services Document caching (a new feature in Strategy 9.x), refer to the following Strategy Knowledge Base Document below:
KB20538 - New Feature in Strategy 9 – Report Services Document Caching
KB20540- New Feature in Strategy 9 – Document Cache Monitor
 
STEPS TO REPRODUCE:
Strategy Tutorial Project is used in the steps below to demonstrate the behavior. The steps also assume that Report Services Document caching is enabled and reports and documents are automatically sent to History List.

• Login to Strategy Web and execute a Report Services Document
• When the document execution completes go to the user's History List and notice that the document and the underlying dataset appear in the user's History List:
  

• Now login to Strategy Desktop and go to System Monitors ->Caches ->Report. Notice that although the document was sent to history, the underlying dataset is only of type 'Matching':
  

CAUSE:
This is working as designed. Report Services Documents do not create `History` caches for the underlying datasets. The dataset History List messages appear in the user's History List as seen in Step 2 above but they do not have an associated cache ID. Because of this dataset results cannot be accessed independent from the Report Services Document results.
Dataset History List messages are useful to the extent of providing additional information on the Report Services Document's execution like Document owner, Document path, Server name, Message ID, Document ID, Report owner, Start time, Finish time, Server name, Message ID, Report ID, Status, Message created, Message last updated.
 
If the administrator deletes the underlying dataset cache, the Report Services Document results can still be retrieved from History List. This is because when a document is sent to history, a .strm file is created immediately that includes the master dataset. Only this .strm file is needed to retrieve the document results. The .strm file is stored in the same location on disk where the user's History File is stored as seen below:

 
When the user wants to retrieve the Report Services Document results, this .strm file is loaded in the working set and the user is presented with the results. If the .strm file does not exist on disk and therefore cannot be loaded in memory, the user will see the following error message:

Sample Code/Error
MsiInBox: The persist message result, either a report result in report cache or a document result file, is not found. It may have been manually deleted by system administrator.
 
 
ACTION:
No action is needed.