Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Query Builder does not save if you have read-only access to the data source #1119

Closed
dgosbell opened this issue May 20, 2023 Discussed in #1115 · 5 comments
Closed

Query Builder does not save if you have read-only access to the data source #1119

dgosbell opened this issue May 20, 2023 Discussed in #1115 · 5 comments
Assignees
Labels

Comments

@dgosbell
Copy link
Contributor

Discussed in #1115

DAX Studio throws an error trying to access the measure expression if the current user only has read-only access to the data source. A user should be able to save the current state of the query builder even if they have only have read-only access to the data source

@dgosbell dgosbell self-assigned this May 20, 2023
@github-actions github-actions bot added the triage issues that need to be classified label May 20, 2023
@dgosbell dgosbell removed the triage issues that need to be classified label May 20, 2023
@Heidinger35
Copy link

Heidinger35 commented May 24, 2023

Hi @dgosbell. Thank you for creating this bug ticket. To confirm - when I am added as an Admin on the workspace this dataset is saved in, I can export query builder files including a measure. When I am changed back to viewer on the dataset permissions, I get the error and no query builder file is generated.

@Heidinger35
Copy link

Hi @dgosbell. Sorry to prod, but any idea if this solution has been tested / when this bug will be fixed? Is there a set rollout schedule of new versions or is this on an as needed basis? Thank you again for your help here!

@dgosbell
Copy link
Contributor Author

dgosbell commented Jun 8, 2023

I have a couple of datasets at work where I only have read access so I was able to reproduce this issue and test the fix against those. There is no fixed schedule for releases it's just best efforts when I get spare time, but I will try and get 3.0.8 out in the next few days.

@Heidinger35
Copy link

@dgosbell excellent thank you so much!

@dgosbell
Copy link
Contributor Author

dgosbell commented Jul 3, 2023

This should now be fixed in the 3.0.8 release. Sorry for the delay in getting this out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants