Anonymous's avatar
Anonymous
Not applicable
3 years ago
Status:
Investigating

The role could not be updated

When trying to add a pro AAD user (not guest) to a row-level security role, I keep getting this error:

Something went wrong

The role could not be updated. Please try again later.

Please try again later or contact support. If you contact support, please provide these details


Activity ID: bd6c23ad-f952-488e-8636-ae4fa091d6a8
Request ID: 7ee68ffd-9b89-057f-dac1-f952988f2f7b
Correlation ID: 7d67fd6f-2327-b4d7-e473-29d7de7bbe2c
Status code: 404
Time: Wed Dec 14 2022 19:29:33 GMT-0800 (Pacific Standard Time)
Service version: 13.0.19635.59
Client version: 2212.1.11380-train
Cluster URI: https://wabi-canada-central-b-primary-redirect.analysis.windows.net/

Reports

5 Comments

  • Anonymous's avatar
    Anonymous
    Not applicable
    3 years ago

    Hi Anonymous ,

     

    After my testing, it works fine with me.
    This may be a problem that appears in a specific region, were your colleagues able to reproduce the problem? Or if a different user can be added properly?

     

    Best regards.
    Community Support Team_ Caitlyn

  • Anonymous's avatar
    Anonymous
    Not applicable
    3 years ago

    Hi Anonymous ,

    We are all in Canada and have tried with different users. It seems that we have an issue with a particular large data model when we try to set or remove users from roles. When I upload the same data model to a premium workspace, the issue disappears.

     

    Any idea what this could be?

  • Arthemis_Runner's avatar
    Arthemis_Runner
    Frequent Visitor
    1 year ago

    Also experiencing the same issue. This is isolated to only 1 report in one of our workspaces. The same report in a different workspace works fine.

     

    Error: 

    Activity ID: f0a677e6-0f34-4e8c-8745-9c482d13840c
    Request ID: 1d9b845e-d515-27a8-b22d-7c765182b702
    Correlation ID: aa09e906-4d0a-8cda-93b5-7c7596fe4794
    Status code: 404
    Time: Wed Nov 13 2024 14:54:40 GMT-0600 (Central Standard Time)
    Service version: 13.0.24656.36
    Client version: 2411.1.21758-train
    Cluster URI: https://5ca9f2e0b1864263b982f2908b5ad472-api.analysis.windows.net/

  • dedy_dp's avatar
    dedy_dp
    Regular Visitor
    1 year ago

    19 nov 24

    i got that notification

    and my weird solution is create new role with same security 

    enjoy 😎

     

  • Arthemis_Runner's avatar
    Arthemis_Runner
    Frequent Visitor
    9 months ago
    The only solution that worked for me was to drop the semantic model from Power BI Service and republish. This means that I have to update and republish ALL the upstream models using this dataset. Was a pain but I tried everything else and nothing worked. Tried: 1. Republishing the dataset to the workspace -- Same error 2. Removing Roles from "Edit Semantic Model" in Power BI service; Adding it back; Adding a user -- Same error

Completed Ideas