Couldn’t load data for this visual. Contact dataset owner.

[FK3]

Existing reports with live connection to datasets using DirectQuery. 

Tiles failed to render with error: Couldn’t load data for this visual. Contact dataset owner.

As of 11/12/2021, these errors appeared on table visuals in Power BI service. When report creators checked their .pbix files, they found same error on visuals. Working with the desktop file and removing certain columns caused the visual to render. Reports were working before 11/12, but now do not, so it looks like there was a change in Power BI service which broke these visuals. Also, this error is not documented here: Troubleshooting tile errors - Power BI | Microsoft Docs

[FK3]

One db is Oracle. Not sure about all the others yet.

[FK3]

This may be due to renaming the columns from the model instead of in the query. That is, right click on the name of the column after it's loaded and rename. 

[v-robertq-msft]

Hi,

Unfortunately, but I can’t reproduce the same issue as yours.

I suggest you to refer to this case with a similar issue as yours.

https://community.powerbi.com/t5/Service/quot-Couldn-t-load-the-data-for-this-visual-quot-error-with...

If you still have a problem, you can also try to open a support ticket to ask for opinions from the technical support team of Microsoft.

https://community.powerbi.com/t5/Community-Blog/How-to-create-a-support-ticket-in-Power-BI/ba-p/6830...

https://powerbi.microsoft.com/en-us/support/

Thank you very much!

Best Regards,

Community Support Team _Robert Qin

[FK3]

Hi Robert— Here's the issue, which I'm posting for the sake of others who may see the same issue. We do have a ticket open for this in support hub, so I'm no longer looking to resolve this here. 🙂 

In the original dataset, columns were renamed from the field list instead of the query. "As always, if you want to rename the field for your entire report, instead of in a single visual, you can do that by double clicking that field in the field list." (Power BI Desktop July Feature Summary | Microsoft Power BI-Blog | Microsoft Power BI)

So, the renaming happened in the model metadata. Then reports were published connecting to the dataset which worked. As of 11/12/2021, some (but not all) of these columns stopped working, breaking the reports. Since this issue is due to an instability in the model metadata, I doubt the error could be easily repro'd. The link you provided references a different error in which ALL visuals are broken due to lack of build permission for published reports using DQ over PBI datasets. That's another painful issue for us :(.

The one workaround I would see is to stop trusting the model metadata and instead rename in the query. 

[v-robertq-msft]

OK, thank you for the detailed explanation!