Dataflow Settings Greyed Out

[cmengel]

Hi!

I'm the Admin of a workspace that houses a series of dataflows.  I have Admin access to this workspace.

Today, I noticed that all the settings for all the dataflows are greyed out (see screenshot).  I am the owner of the dataflow, so I know it's not a case of having to "Take Over" a dataflow.

All the dataflows pull from Snowflake and refresh just fine.

I checked a different workspace (one I created and I'm the Admin for) that houses a couple other dataflows that I use for testing purposes and those settings are also greyed out.

Finally, I checked with a colleague of mine, and he's seeing the same thing for dataflows that he created in a workspace he's the Admin for.

Perhaps it's some sort of tenant level setting?

Thanks in advance for your help!

Cheers!
Chris

[cmengel · Accepted solution]

Ability to edit settings has been successfully restored!  This topic is closed.

[ThristonS]

Had this issue last week (July 19th - July 22nd). Checked this morning (July the 25th) and I can access and modify my dataflow settings now: 

Thriston 

[sbuecker]

Same issue here.

Options for me and my colleagues (all are Admins) are greyed out.

Does anyone know, where to find detailed information regarding this issue? 

Is Microsoft working on it?

BR

Sebastian 

[rargyle]

Same issue here, using 

Service version 13.0.18666.32

Client version 2207.2.12226-train

Your data is stored in North Europe (Ireland)

[bcdobbs]

@KellyK would you be able to escalate this at Microsoft? Thank you.

[Jan_Hob]

Having the same issue, it was working yesterday and isn't working today

[PaulHet]

Issue is formally logged here Issue - Cannot seem to edit DataFlows Settings on ... - Microsoft Power BI Community

Please go and vote on it to ensure MS understand the scope of the impact!

[MladenJ]

Same here. 

I know there is current issue with dataflows in general (check support page), but they haven't mentioned anything else.

[Anonymous]

I know this isn't helpful as a solution but I am having the exact same issue.  I know this issue hasn't existed for too long since I was just changing things last week.

I wonder if there is an issue with the Service?