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

KB442260: For a data import intelligent cube which contains attribute with derived geo role, delete table operation may hit error, if Data Engine Version set to 11


Community Admin

• Strategy


This technical article describes an error that potentially prevents users from deleting a table from Data Import Intelligent Cube, if the table contains attribute with derived geo role.

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.
SYMPTOM: 
When "Data Engine Version" set to 11, if a user tries to update a Data Import cube with multiple tables, and deletes a table that has at least one derived geo role, when trying to update dataset, an error may pop up, preventing user to update the Data Import cube.
For more details on enabling "Data Engine Version" setting, refer to Change Data Engine Version.
STEPS TO REPRODUCE: 
1. Use Strategy Tutorial Project to create “New Dossier” and add New Data.
2. Choose “Sample Files”.

ka0PW0000001JU2YAM_0EM44000000RTPL.png

3. Pick “Airline Sample Data“ and ”Campaign Finance Data”, click to “Prepare Data”.

ka0PW0000001JU2YAM_0EM44000000RTPQ.png

4. On Preview page, define derived geo attribute on "Campaign Finance Data“: Right Mouse Click attribute "Candidate City", choose “Define Geography”, check option "State" in “Additional Attributes”, click “OK”, and click “Finish” to publish the cube.

ka0PW0000001JU2YAM_0EM44000000RTPV.png

5. Notice the derived attribute Candidate City (State) is created.

ka0PW0000001JU2YAM_0EM44000000RTPa.png

6. Delete the table, the error will pop up:

ka0PW0000001JU2YAM_0EM44000000RTPk.png
ka0PW0000001JU2YAM_0EM44000000RTPp.png

CAUSE: 
There are two geo role attributes, the existing city attribute and derived geo role attributes which is defined on the city attribute while data preparation. Each geo role attribute includes additional geo columns. When we delete the table and try to unset the geo role, the additional geo columns are not deleted in the previous implementation. 
ACTION/RESOLUTION: 
This defect is addressed in Strategy 11.1 or above.
Strategy reference numbers for this technical note are KB442260 and DE114739.


Comment

0 comments

Details

Knowledge Article

Published:

November 19, 2018

Last Updated:

March 21, 2024