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

Testing RLS in one model (SASS), getting error about no access to dropdown default model #1188

Closed
FloorDriek opened this issue Oct 6, 2023 · 4 comments
Labels

Comments

@FloorDriek
Copy link

DAX Studio v3.0.8.945
Connection: not connected

Summary of Issue

Opening DAX Studio, connecting to on premisse SSAS environment, selecting another model than the default.
When entering query, no problem, results. However when I want to test with another role(s), and or other user, I get an error telling me that the credential does not have access to the default model.

Just now selected role in the default model itself. No error. It seems that it resets the choice and selects the default and gets confused and gives an error.

Steps to Reproduce

Dax Studio possible bug 231005
@github-actions github-actions bot added the triage issues that need to be classified label Oct 6, 2023
@FloorDriek
Copy link
Author

Found part of the error, mine. Don't know why it went back to default be he, not most important part

@dgosbell
Copy link
Contributor

dgosbell commented Oct 7, 2023

OK, thanks for looping back and letting us know.

@FloorDriek FloorDriek reopened this Oct 12, 2023
@FloorDriek
Copy link
Author

FloorDriek commented Oct 12, 2023

Okay back again

So initially the main culprit was me being unaware that user of account I tried for testing was not in the AD group attached to the dynamic role. I am using Radacad's many to many pattern with DAX in SSAS.

However today the error is back, and I found a work around, this is not the easiest of think, in an otherwise excellent program.

So steps, with error:
1 > I connect to a SSAS server, with more than one model, there I select a model that is not the default/initial model, it connects
2 > then I go to advanced > view as and select a couple of roles
3 > then I get the error seen below in the screenshot

With work around:
1> (same) I connect to a SSAS server, with more than one model, there I select a model that is not the default/initial model, it connects
2> I go to Home> Connect>Connection and open advanced options and change the initial catalog to the model I want to test
3> then I go to advanced > view as and select a couple of roles
4> no error message

Capture

And for complete information, I have now updated to version 3.0.10.

@dgosbell
Copy link
Contributor

Thanks for following up on this. I have been able to reproduce this so I should be able to figure out a fix for it.

@dgosbell dgosbell added bug and removed triage issues that need to be classified labels Oct 29, 2023
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