Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!

Query contains unsupported function. Function name: Resource.Access

Hi Team,

 

We are facing the issue with the Powerbi Service from past 2-3 day. we are getting " Query contains unsupported function. Function name: Resource.Access " through the python scripts.Before that we are using the same through the personal gateway installed. Attaching  the image for you refrence.Please Fix this issue ASAP!!

SathishR_0-1670311850535.png

 

Thanks and Regards

Sathish

 

Status: Delivered

Hi @SathishR 

This issue has been fixed . Please check this issue in your Service .

 

Best Regards,
Community Support Team _ Ailsa Tao

Comments
annav
Frequent Visitor

Experiencing the same issue, is there any updates on it?

thielson
New Member

@annav no update yet

vinod193_123
New Member

Even i am also facing the same issue

estebanb
Frequent Visitor

Hello, same problem with the mariadb connector. The scheduled refresh works for reports already published prior to Dec 6, 2022. But when publishing a new report with sources from this connector, it shows the Resource. access error and does not allow to use the gateway.

lilianarondon
Regular Visitor

I have the same issue.

 

lilianarondon_0-1670421841186.png

 

gcoronadom
New Member

Same issue here! Please let us know when this is resolved.

sklein
Regular Visitor

Same issue. hoping this is resolved soon.

NeutralAlien
Regular Visitor

Same issue for me.

estebanb
Frequent Visitor

Hi all

Same issue here uploading new reports to services, existing reports work fine. PLease try to fix it soon, 

"

You can't schedule refresh for this dataset because the following data sources currently don't support refresh:

  • Data source for Query1

 

Discover Data Sources

Query contains unsupported function. Function name: Resource.Access
"

Regards,
Hector

JulienMartin
New Member

Hello everyone,

 

I am facing the same issue with a custom connector for Neo4j.

 

Any idea when it will be fixed ?