Query contains unsupported function. Function name: Resource.Access

[eirikamadeus]

I started getting this message suddenly for my dataset, and the "Gateway and cloud connections" is not showing. The dataset is using a custom connector (self signed) via a gateway.

I stripped the queries down, and got this dataset to work.

However, when I then tried adding different queries it failed again. Now I have stripped down again, and I am left with the same query as for the dataset/semantic model that works.

I can not find any difference between the working and not working dataset.

How can I figure out what the cause of this error is? All of the versions work perfectly in PowerBI Desktop. Also, I have tried reauthenticating within desktop, before publishing again. 

Highly appreciate any tips and/or help. (PS, I found a very similar thread from 2022, this was a bug that was fixed.

[LucasPBI]

same here with snowflake

[Anonymous]

Hi @eirikamadeus 

What connector are you using ? Have you made any changes in the meantime? Also did your Desktop do an automatic update?

Best Regards,
Community Support Team _ Ailsa Tao

[eirikamadeus]

We're a Saas-solution delivering our own connector. No updates made.

In another channel to Microsoft, I got the message that it was a known issue, and that they were working on a fix that so far had no ETA. I tried to get a link to the issue itself, but did not exist either. Weird way of handling it...

[eirikamadeus]

Not sure how automatic update works in Desktop, but I did update/refresh the data and it all works fine. No errors at all in Desktop.

[Anonymous]

Hi @eirikamadeus 

Yesterday a lot of users reported a little problem with Desktop, but the problems that arose were not the same. However, after the PG team updated the program for the Store App, everything is back to normal. Apparently, your problem could also be caused by a program update. Anyway, glad you can use your Desktop normally now.

Best Regards,
Community Support Team _ Ailsa Tao

[eirikamadeus]

There was different datasets that acted differently, and the error message was not that informing.

However, the problem was due to no connections being available in the setup. Having one valid connection solved the issue.