Forum Discussion
Can Not View Datasets/DataFlows in New Look
We just noticed that in the new look we can not see the datasets/flows if the workspace is set to: Members Can Only View content. We are ALL admins, not members to the workspace, yet the entire grou...
I also started having this problem on Friday (April 17). It looks like there has since been an update to the UI to add a tab for Datasets + dataflows; however, it doesn't show anything in it. The lineage view suggestion does work, but it's not very convenient -- I can't search the page to jump straight to the report I want to update. It makes me scroll through the list.
Hi all,
Update time:
The good: the Support engineer I have been working with has been fantastic. I want to get this out there because what follows is not a reflection on her.
The bad: the Microsoft product team (apparently) has no idea what they are doing
After multiple screen share sessions and multiple browser logs sent the answer the power bi team has for this issue is that this is “by design”.
Ok, so here is where my rant begins.
Under the old look I could designate workspace members as members or admins. Awesome! Furthermore I could limit my members to only viewing, but not editing, my datasets. Security, amazing! This was a rational, sensible process.
Now let’s get to the crazy “by design” new look:
1. Roles? Who cares! I can denote someone as a member or admin, but it doesn’t matter which because it makes no difference.
2. Security? Rock solid, because if I set my workspace to “allow members to only view” I not only limit my members from editing datasets but my admins as well. If no one can see them no one can edit them
3. But wait! There’s more (absurdity). You can bypass this “by design” security by changing from list view to whatever the other one is.
When I started this thread Greg (correctly) cautioned that progress comes with bumps. However, this apparent “by design” insanity is not a bump, it’s evidence that the designers are not putting thought into what they are doing.
MS, please reconsider your “by design” decision. I have an open ticket and would be happy to discuss.
Update time:
The good: the Support engineer I have been working with has been fantastic. I want to get this out there because what follows is not a reflection on her.
The bad: the Microsoft product team (apparently) has no idea what they are doing
After multiple screen share sessions and multiple browser logs sent the answer the power bi team has for this issue is that this is “by design”.
Ok, so here is where my rant begins.
Under the old look I could designate workspace members as members or admins. Awesome! Furthermore I could limit my members to only viewing, but not editing, my datasets. Security, amazing! This was a rational, sensible process.
Now let’s get to the crazy “by design” new look:
1. Roles? Who cares! I can denote someone as a member or admin, but it doesn’t matter which because it makes no difference.
2. Security? Rock solid, because if I set my workspace to “allow members to only view” I not only limit my members from editing datasets but my admins as well. If no one can see them no one can edit them
3. But wait! There’s more (absurdity). You can bypass this “by design” security by changing from list view to whatever the other one is.
When I started this thread Greg (correctly) cautioned that progress comes with bumps. However, this apparent “by design” insanity is not a bump, it’s evidence that the designers are not putting thought into what they are doing.
MS, please reconsider your “by design” decision. I have an open ticket and would be happy to discuss.