Dataflow connection configuration not working

[JoshT]

I have a dataflow with a few queries that connect to an Oracle source. It was working fine for a while but after a recent edit I was getting in a loop with the message 'we could not evaluate this query due to invalid or missing credentials', so I selected the credentials from the gateway (which are working), but just got the same message again.

I try to create a new connection and I get an interface with no options and no way to continue:

Checking the settings page, the data source credentials expandable is greyed out:

This is not a problem with the gateway or client software - datasets with oracle sources can still be configured and refreshed successfully. This also only started happening today after attempting to edit the dataflow as it refreshed successfully at midnight this morning. I am also unable to create any new dataflows that connect to an Oracle source without this happening (with a slightly different error message). There aren't any workarounds I can find so this is a breaking bug as it stands.

[Anonymous]

Hi @JoshT ,

Do the credentials you entered still have access to the Oracle data source?
If it is convenient, my best suggestion is that you recreate the new data flow with the new associated configuration and try to see if it works.

Best regards,

Community Support Team Selina zhu

[JoshT]

Hi @Anonymous ,

As explained above, I'm still able to create datasets and refresh them successfully with the same connections, as well as test the connection in the gateway with no issues. Also as explained above, I have tried creating a new dataflow and have run into the same problem, so this is definitely a bug. I suspect it is within the scope of dataflows themselves.

Just want to make this clear at the moment - I have absolutely no way of getting Oracle data through a dataflow at present.

To confirm, I've checked again this morning and the issue is still persisting. I don't get any other information than the below, when I configure the connection or try to create a new one, it just goes back to the same error every single time.

I can also confirm that another version of the same dataflow in a test environment can refresh successfully. Difference between the two is I haven't attempted to edit the test dataflow, this only became a problem once I did, or for any new dataflows.

[JoshT]

I've had this issue again with a SQL Server connection, this time from a dataflow imported from JSON (exported direct from a dataflow in another workspace). The json import works fine and the dataflow is created correctly, it just needs the connection to be configured in the Power Query interface, at which point this bug crops up. As with the other example, the connection works fine through the gateway and is used by other dataflows that refresh successfully.

I don't know how to identify the conditions where this happens as there are plenty of (sometimes identical!) dataflows where I don't experience this issue, but it's definitely a bug judging by the behaviour of the interface and the lack of any returned error message.

[JoshT]

Hi @Anonymous , a colleague of mine figured out that the problem in this case is that the gateway is not configured in the project options. While this has provided a workaround for the issue for the time being, there are still several UX/navigation issues around this that need to be fixed. Could the below be added to the product backlog?

• When configuring connections, the selected source has a gateway associated with it, so should be configured in the project options automatically.
• If the above isn't possible for any reason, an error message should appear explaining that gateway needs to be configured in project options
• After importing from JSON, the 'edit credentials' button takes you to the setting page, before credentials have been configured within Power Query. This also navigates to the top dataflow in the workspace alphabetically, not necessarily the one you've just configured. In the settings page, 'data source credentials' blade is greyed out. This button should redirect to Power Query.
• After importing from JSON, the 'edit tables' function (i.e. opn Power Query) is greyed out until you navigate away from the dataflow and return (refresh does not work). Page still displays previous options as if the dataflow is new