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

KB44190: Error message appears when running a document in MicroStrategy Developer 9.4.1 and 10.x: "The data set is not ready in the document instance. This action cannot perform on the document instance without data set."


Stefan Zepeda

Salesforce Solutions Architect • Strategy


When a user runs a document in MicroStrategy Developer 9.4.1 or 10.x, the following error will show: "The data set is not ready in the document instance. This action cannot perform on the document instance without data set."

SYMPTOM:
When a user runs a document in Strategy Developer 9.4.1 or 10.x, the following error will show:
 

ka02R000000kc0lQAA_0EM440000002Cjh.png


The data set is not ready in the document instance. This action cannot perform on the document instance without data set.

 
CAUSE:
This is working as designed.  The reason why this is happening is because the user who is running the document does not have access to one of the datasets.  Although the user might have full control of the document, this does not override the security for the underlying dataset. 
 
ACTION:
In order to find what document the user does not have access to, right click on the document in question and do search for components..

ka02R000000kc0lQAA_0EM440000002CjO.png

 
Look at all the reports that are returned in the search and right click on each and go to the properties.  From there, locate either the user or the group the user is apart of and make sure they have access to the report.  In this example, the user, "test", was initially given "Denied All" access.  Giving this user "View" access resolves the issue.
 

ka02R000000kc0lQAA_0EM440000002Cjc.png

Comment

0 comments

Details

Knowledge Article

Published:

June 1, 2017

Last Updated:

June 1, 2017