Forum Discussion
Power BI dataflows (legacy) keep error : The credentials provided for the PowerBI source are invalid
Hi Ceeeg ,
Are you using power bi legacy (no 1) connector? I've tried updated the connector using power bi dataflow / newer / not legacy (no 2) and the error dissapear
Here's my step to update connector from 'power bi dataflow (legacy)' to 'dataflow'
1. Open dataflow and remember the first table (in my case I choose 'wmsmakloon_transfer_log_natura')
2. Get data from 'dataflow' and select table 'wmsmakloon_transfer_log_natura' and load it. The table name will be 'wmsmakloon_transfer_log_natura (2)'
3. Go to 'advance editor' and copy these 5 line query from table 'wmsmakloon_transfer_log_natura (2)'
4. Now select 'wmsmakloon_transfer_log_natura' table, go to 'advance editor', paste and customise the code
This is my query before in table 'wmsmakloon_transfer_log_natura' :
let
Source = PowerBI.Dataflows(),
Workspace = Source{[workspaceId="19cfed95-xxxx-xxxx-xxxx-xxxxxxxxxxxx"]}[Data],
Dataflow = Workspace{[dataflowId="0100cd6a-xxxx-xxxx-xxxx-xxxxxxxxxxxx"]}[Data],
Entity = Dataflow{[entity="wmsmakloon_transfer_log_natura"]}[Data]
in
EntityAnd this is my query after I customise based on table 'wmsmakloon_transfer_log_natura (2)' :
let
Source = PowerPlatform.Dataflows([]),
Navigation = Source{[Id = "Workspaces"]}[Data],
#"Navigation 1" = Navigation{[workspaceId = "19cfed95-xxxx-xxxx-xxxx-xxxxxxxxxxxx"]}[Data],
Dataflow = #"Navigation 1"{[dataflowId = "0100cd6a-xxxx-xxxx-xxxx-xxxxxxxxxxxx"]}[Data],
Entity = Dataflow{[entity="wmsmakloon_transfer_log_natura"]}[Data]
in
Entity5. If you want to update another tables, copy these 5 line query from table 'wmsmakloon_transfer_log_natura' (which is customised table based on the new power bi dataflow connector). These query will be paste references for other tables
6. Paste it into another tables (picture below is example for table '
wmsmakloon_transfer_log_infion')
7. Delete unnecessary gateway 'Power BI dataflows (legacy)'
Hi Anonymous ,
Please check this case, is it really because of the 'Power BI dataflows (legacy)' connector?
Sincerely,
Oviedityanto
Hi Ceeeg ,
Are you using power bi legacy (no 1) connector? I've tried updated the connector using power bi dataflow / newer / not legacy (no 2) and the error dissapear
Here's my step to update connector from 'power bi dataflow (legacy)' to 'dataflow'
1. Open dataflow and remember the first table (in my case I choose 'wmsmakloon_transfer_log_natura')
2. Get data from 'dataflow' and select table 'wmsmakloon_transfer_log_natura' and load it. The table name will be 'wmsmakloon_transfer_log_natura (2)'
3. Go to 'advance editor' and copy these 5 line query from table 'wmsmakloon_transfer_log_natura (2)'
4. Now select 'wmsmakloon_transfer_log_natura' table, go to 'advance editor', paste and customise the code
This is my query before in table 'wmsmakloon_transfer_log_natura' :
let
Source = PowerBI.Dataflows(),
Workspace = Source{[workspaceId="19cfed95-xxxx-xxxx-xxxx-xxxxxxxxxxxx"]}[Data],
Dataflow = Workspace{[dataflowId="0100cd6a-xxxx-xxxx-xxxx-xxxxxxxxxxxx"]}[Data],
Entity = Dataflow{[entity="wmsmakloon_transfer_log_natura"]}[Data]
in
Entity
And this is my query after I customise based on table 'wmsmakloon_transfer_log_natura (2)' :
let
Source = PowerPlatform.Dataflows([]),
Navigation = Source{[Id = "Workspaces"]}[Data],
#"Navigation 1" = Navigation{[workspaceId = "19cfed95-xxxx-xxxx-xxxx-xxxxxxxxxxxx"]}[Data],
Dataflow = #"Navigation 1"{[dataflowId = "0100cd6a-xxxx-xxxx-xxxx-xxxxxxxxxxxx"]}[Data],
Entity = Dataflow{[entity="wmsmakloon_transfer_log_natura"]}[Data]
in
Entity
5. If you want to update another tables, copy these 5 line query from table 'wmsmakloon_transfer_log_natura' (which is customised table based on the new power bi dataflow connector). These query will be paste references for other tables
6. Paste it into another tables (picture below is example for table '
wmsmakloon_transfer_log_infion')
7. Delete unnecessary gateway 'Power BI dataflows (legacy)'
Hi Anonymous ,
Please check this case, is it really because of the 'Power BI dataflows (legacy)' connector?
Sincerely,
Oviedityanto
Hey cst_bi ,
I've just been testing this out after reading your earlier response where you mentioned the legacy vs not-legacy connector.
Changing to the not-legacy connector appears to have resolved the issue.
To test it out, I exported the json, opened it in a text editor, and replace all instances of PowerBIDataflowsConnector with PowerPlatformDataflowsConnector. I then loaded that in as a new dataflow, and it seemed to make all the adjustments to the queries as appropriate. It asked me for credentials, I signed in, and it seemed happy. I opened up the manage connections window, and deleted the legacy connection. The privacy level on the new connection was set to private, and I couldn't seem to change that from manage connections, but then I went to the dataflow settings and was able to change it to organisational when I edited credentials there.
This is obviously not ideal, because loading it in as a new dataflow means it will have a different dataflow id, so anything referencing that dataflow will need to be updated. Luckily for me at least, the affected dataflow is the final one before it gets loaded for use, so I only have to update it in one or two reports. Seems like it would be very tedious if the problem had happened in a dataflow that is referenced by another dataflow and I had to update the dataflow id for each query in there.
Hopefully this doesn't all happen again when the Fabric Dataflows connector becomes the 'normal' one and the Power Platform version becomes 'legacy'.