MicroStrategy | New feature in MicroStrategy Enterprise Manager 9.0: Ability to track export jobs initiated from MicroStrategy Web.

Starting with MicroStrategy Enterprise Manager 9.0, it is possible to track export jobs initiated from MicroStrategy Web.

A new column called ‘EXPORTINDIC’ has been added to the Statistics tables IS_REPORT_STATS and IS_DOCUMENT_STATS to mark report/document jobs that were triggered because of exports done from MicroStrategy Web. This column is available in the IS_REPORT_STATS and IS_DOCUMENT_STATS tables for Statistics tables newly created in MicroStrategy 9.0 or for Statistics tables that have been upgraded from version 8.0 to version 9.0.

Note: Exports from MicroStrategy Desktop cannot be tracked as the export operation is performed by the client i.e. MicroStrategy Desktop and not the MicroStrategy Intelligence Server.

For exports initiated from MicroStrategy Web, a non-zero value is logged in the EXPORTINDIC column as shown below. The value is 0 for jobs which are not for export operations.

The value in the EXPORTINDIC column indicates the type of export that was done. The following table provides the type of export corresponding to each value.

 

 

**TN34360: New PDF Container for Adobe Flash in MicroStrategy Web version 9.0.2

 

Reports:

All report export operations performed from MicroStrategy Web i.e. exports done after report execution and exports done from history list messages and direct exports can be tracked.

Direct export refers to the export operations which are done prior to the execution of the report or document i.e. users click on the ‘PDF’ or ‘Export’ button seen next to the report name, as shown below:

Even in cases, where MicroStrategy Web report export jobs use existing report caches, a report job gets logged in the IS_REPORT_STATS table with a non-zero value for the export indicator.

Documents:

For documents, only the document export jobs which don’t use an existing document cache have a non-zero value for the EXPORTINDIC column.

Consider the following scenario: If there is no existing document cache and a direct export of a document is done to PDF, then the EXPORTINDIC column for this document job has a value of 2 (row 1 in the screenshot below). If an export of the same document is done to Excel, then the EXPORTINDIC column for this document job has a value of 1 (row 2 in the screenshot below). If the same document is exported to PDF again, there is an entry in the IS_DOCUMENT_STATS table, but the EXPORTINDIC column value for this row is 0 as shown below.

This is because there is an existing PDF document cache which was used by the 2nd PDF execution. For more information about document caching (a new feature introduced in MicroStrategy 9.0), refer to the following knowledge base document.

Export jobs initiated after executing the document or exports initiated from history list messages don’t get logged to IS_DOCUMENT_STATS. This is because no MicroStrategy Intelligence Server Job gets created (because of work flow for Web operations) for this operation and hence no data gets logged to IS_DOCUMENT_STATS.