EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB18721: While logging report job statistics, MicroStrategy Intelligence Server log incorrect value for ad-hoc indicator for ad-hoc report jobs which are initiated from saved reports


Community Admin

• Strategy


While logging report job statistics, MicroStrategy Intelligence Server log incorrect value for ad-hoc indicator for ad-hoc report jobs which are initiated from saved reports

SYMPTOM:
If a project is configured to collect statistics for report job executions, for every job that gets executed, along with other information, it is also recorded if the job is from an ad-hoc execution or not.
 
In Strategy Intelligence Server 9.x and 10.x, ad-hoc indicator is logged incorrectly for ad-hoc jobs which are initiated from saved reports.
 
STEPS TO REPRODUCE:
Follow the steps below to reproduce this issue:
 

  • Consider the report shown below containing attribute Region and metric Revenue. This report is saved as Report 1.
ka04W00000148W4QAI_0EM440000002BJ1.jpeg
  • Edit Report 1 to add attribute 'Call Center' to the template.
  • Without saving the report, execute the report. This execution will result in the generation of a new job on the Strategy Intelligence Server 9.x and will execute against the warehouse.
ka04W00000148W4QAI_0EM440000002BIs.jpeg
  • Close Report 1 without making saving the changes.
  • Query the IS_REPORT_STATS table to identify the row of data corresponding to the ad-hoc execution from Step 3.
  • The ad-hoc indicator value for this execution is seen as 0 instead of 1.

CAUSE:
This is a known issue with Strategy Intelligence Server 9.x and 10.x.
 
ACTION:
Currently this issue is being reviewed by Strategy for a potential code fix on an upcoming Strategy release.
 
 


Comment

0 comments

Details

Knowledge Article

Published:

June 13, 2017

Last Updated:

June 13, 2017