Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and a 50 percent discount on exams.
Get startedEarn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
We have a premium subscription and we're on gen 2. We have a data set that is composed of direct query tables (hubs) as well as dual (spokes) tables. This has been published to a new advanced workspace and has resided there for over a year. This dataset has been shared out to 70+ members of our analyst community and just recently started randomly throwing the following error message.
This is received by all reports, desktop and published, that are sourced from this master "DirectQuery for PBI datasets and AS" dataset.
I have a feeling this may have been caused by the recent upgrade to the service that allows permissions at the master shared dataset to be set to read vs read, build for an individual.
We can temporarily fix this by republishing the dataset. However, it will sporadically reappear, at least once a day, and break all of the related reports that stem from it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have you enabled this feature in Power BI Desktop when facing with this issue?
In addition, you can try to check whether you have met any limitations of this feature, see:
Using DirectQuery for Power BI datasets and Azure Analysis Services (preview)
Best Regards,
Community Support Team _ Yingjie Li