Forum Discussion
Advocate IIIQuery contains unsupported function. Function name: Resource.Access
Hi all,
Get the latest feedback:
This issue has been deployed and validated.
PROD - 11.4 QFE –12/10 and 12/11 - Sat with US clusters- Sunday.
Best regards,
Community Support Team Selina zhu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Hi all,
Get the latest feedback:
This issue has been deployed and validated.
PROD - 11.4 QFE –12/10 and 12/11 - Sat with US clusters- Sunday.
Best regards,
Community Support Team Selina zhu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
- Kletzy
Personally, I think Microsoft really dropped the ball on this one - it took 5 days from when I initially posted the issue for it to be acknowledged on the support page - this has been a major problem for many of us.
Absolutely agree. This was worryingly underrated. The PBI service and the gateways should be considered as one. I don't know what kind of company has established a direct communication between their production data servers and the Power BI service, in my case and probably in many entities that value the security of their clients, that will never happen. Therefore, the only way we have to implement the Power BI service is through the gateways, it's just this, without gateways there is no service. So what do they mean when they report that everything is running smoothly, except for an irrelevant issue with the gateways? And the week to solve it...
drannyAdvocate I
So no correction until this week-end on PROD ? So one week with this errors 🤔
I got other information from Microsoft. What is now correct!?
PG has recently confirmed that the fix will be deployed during train 12.2 or 12.4 (12.3 was cancelled) roughly they said it will be deployed between end of December or early January. Unfortunately, there is no workaround provided so far.
We will keep you posted if there will be anything Product group would share for partial mitigation or workaround to be used before the fix will be deployed.I don't think that this issue is being taken with the severity level it really has. How many of us/our companies are paying for this service and depending on this connectors to feed all our information systems. How can they inform that the "Service Status Per Region" is "Good"? Isn't it the Gateway part of the "Service"?
I'm with Western Europe (Netherlands) server. The status is "...error message "Query contains unsupported function. Function name: Resource.Access". Engineers have identified the root cause and a fix is expected to be deployed by end-of-day 12/11/2022."
Confirm the resolution today. My custom connector works fine after republish the report. Thanks.
I have redeployed the dataset today and the refresh finally works again. With us it is a custom denodo connector.
I can confirm that. Works now again for my costum connector as well.
BartNLI just checked and also in Europe the fix is working. I can Refresh it. I had to go into settings of my dataset and hit "Discover Data Sources" to be able to connect to the gateway. I only had to indicate for my Dataset which gateway to use. But that was minor effort and also I had to set the refersh schedule again.
powerapps_tecRefresh works with Python extension data source on Power BI Service. Thanks for the fix.
- dranny
Hi,
it works for me too since this mornig. I just click on Discover Data Sources and the gateway option is available again and I can attach the gateway to my datasource.
