Which suggest changing this line in the PBI source step:
= DremioCloud.DatabasesByServerV370(“sql.eu.dremio.cloud”, “<my_project_id>”, null, null, null, null, null)
into this (change the options parameter from null to empty array:
= DremioCloud.DatabasesByServerV370(“sql.eu.dremio.cloud”, “<my_project_id>”, null, null, null, null, [ ])
I am using PBI version from May. Does this fix seem like a valid solution or fighting a symtom? Luckily the online refresh still works, but i don’t dare to upload a new file just yet.
Hi @patrickkooman, We’ve fixed the issue and submitted the fix to Power BI for release. You may want to mitigate the issue as described in the MS community post in the short term.
@isha@patrickkooman – Don’t mean to hijack the thread, but we are experiencing the same issue. We were able to resolve the problem with the individual data connections by making the power query change. However, we are unable to get the scheduled refresh to accept credentials. It appears that it is using power query in the background to verify the credentials and failing in the same way and we can’t find where that would be configured or overridden.
Hi, no worries Just to be sure: did you re-publish your PBI file after you made the changes? The PBI service (online) should then first do a initial refresh. Does that one work?
In the refresh setting, have you tried to edit or remove the credentials to force the service to ask for your Dremio PAT again?
Yes, we did republish. Manual refreshes work fine via the web interface but when we go into schedule a refresh it fails with the same error even after switching users and credentials. It seems like it is generating a power query string based on the connector type and that generation is using the old parameters (just a theory though as I can’t find where that would be configured/stored)..
Just to be sure: did you re-publish your PBI file after you made the changes? The PBI service (online) should then first do a initial refresh. Does that one work?