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

KB319310: Reports no longer dynamically source from from a intelligent cube after a DELETE Incremental Refresh Report is run on the intelligent cube in MicroStrategy 10.x.


Community Admin

• Strategy


 This article discusses an issue with DELETE incremental refresh reports invalidly preventing an intelligent cube from being used for dynamic sourcing in MicroStrategy 10.x.

SUMMARY:
 This article discusses an issue with DELETE incremental refresh reports invalidly preventing an intelligent cube from being used for dynamic sourcing in Strategy 10.x.
 
SYMPTOM:
After running an DELETE incremental refresh report against an intelligent cube in Strategy Developer 10.x, a regular report configured to dynamically source from the same affected intelligent cube does not do so, and instead executes against the database.
 
STEPS TO REPRODUCE:

  1. Create Intelligent Cube “DS Test” with attributes Year, Quarter, and Category, metric Revenue, and attribute qualification filter “Year In List (2014, 2015, 2016)”. Configure the intelligent cube for dynamic sourcing, setting both “Make Intelligent Cube available for Dynamic Sourcing” and “Allow Dynamic Sourcing even if Outer Join properties are not set” options to be “Enabled”. Publish the intelligent cube and save.
  2. Create two value prompts: one text “Value (Text) Quarter”, and one numeric “Value (Number) Number”. The text prompt will be used later for the Quarter attribute, and the numeric prompt for the Year attribute.
  3. Create a regular report with Year and Revenue, and the following filter attribute filter qualifications: “Year (ID) Exactly [ Numeric Value Prompt ]” and “Quarter (DESC) Exactly [Text Value Prompt]” and “Category In List (Electronics)”. Within the VLDB Properties of this report, set the following Dynamic Sourcing settings to be enabled: “Enable Dynamic Sourcing for report (uncheck the default checkbox to make sure that this property is manually set to enabled), “Enable Extended Mismatch Log”, “Enable Mismatch log in SQL View”, and “Enable Report Parse Log in SQL”. Run the report using “2015” without quotes for the numeric value prompt and “2015 Q1” without quotes for the text value prompt. After data is returned, view the Report SQL. Notice that the report is using dynamic sourcing from intelligent cube “DS Test”.
  4. Create a Delete incremental refresh report based off of the “DS Test” intelligent cube, with the attribute qualification filters “Year In List (2014, 2015, 2016)” and “Quarter (DESC) Exactly 2014 Q1”, deleting data from Q1 2014. Run this report.
  5. Purge report cache for the regular report and run it again, using the same prompt answers as from step 3, and notice within the report SQL that dynamic sourcing is not used.

 
In Strategy 9.x, dynamic sourcing is still used for the regular report after running the DELETE incremental refresh report following the same steps.
 
CAUSE:
This issue has been identified as a defect in Strategy 10.x.
 
ACTION:
Currently this issue is still being reviewed by our Technology team as and it is not scoped for any upcoming scheduled Strategy release.
 
WORKAROUND:
The below steps worked to get around the issue as outlined above.

  1. Perform a full republish of the intelligent cube.
  2. Within the incremental refresh report, remove the filter created on Year. Run this report.
  3. Purge report cache for the regular report and run it again, using the same prompt answers as from step 3, and notice that dynamic sourcing is now used.

 
The Strategy Internal Reference Number for the issue discussed in this technical note is DE51392.


Comment

0 comments

Details

Knowledge Article

Published:

June 8, 2017

Last Updated:

June 8, 2017