Forum Discussion

amarcucio's avatar
amarcucio
Frequent Visitor
3 years ago
Solved

New App Experience: Users receiving Permission Required message

Hello,

 

We recently updated to the new app experience.  Since this update, users receive a Permissions Required message on any new reports added to our app, unless they are members of the Workgroup itself.  The dataset permissions look identical to the reports added before the most recent change.  I have tried removing & re-adding permissions, creating a new audience for the permissions.  They are currently based on a security group pulled from the Active Directory list. 

 

Is there another setting that I am missing (or unable to see) or even a way to role back the new app experience?  See message below that people are receiving.

 

  • Try clearing all the permissions and set it to whole organization & save.  then go in again and set permissions as they originally were.  We did this during troubleshooting and now everyone has permissions again like they did before.  I do not know if this will be a reoccuring work around yet, but it worked for me.

5 Replies

  • Hi amarcucio 

     

    As far as I am aware when a new report is added there also is an underlying dataset (unless using composite models). That then means that you still need to grant the users permissions to the dataset.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Following, because I'm having the same issue since the change. Only happening for new reports and dataset permissions are same as reports published prior to the change. We also use AD. Hope Microsoft fixes this soon, or provides us with rollback. I haven't found a solution yet.

    • amarcucio's avatar
      amarcucio
      Frequent Visitor

      Try clearing all the permissions and set it to whole organization & save.  then go in again and set permissions as they originally were.  We did this during troubleshooting and now everyone has permissions again like they did before.  I do not know if this will be a reoccuring work around yet, but it worked for me.

  • We are experiencing the same error. We've been testing many scenarios. On a fresh workspace with fresh app we don't get the issue. Just on a legacy one that was upgraded. Still haven't found anything, but if we get a solution, I will update back here.

    • amarcucio's avatar
      amarcucio
      Frequent Visitor

      Hi Ed, I found a work around that has worked so far for us.  After the permissions are granted in the app, I went to the dataset itself and granted the same permissions.  It still says permissions granted through the app, but it seems to work after this.