Источник:
https://crmtipoftheday.com/1393/if-t...-does-not-work
==============
Have you tried turning it off and on again?
IT Support
Dataverse connector in Power BI is all the rage: fast, efficient, understands metadata well, supports both Import and DirectQuery, makes sushi upon request, you name it. Except that sometimes it does not work. Try selecting account table, for example:
DataSource.Error: Microsoft SQL: Invalid object name 'dbo.FilteredAccountTDS'.RequestId: TDS;a2c61dc8-b400-4d34-b66f-3c30157f0a42;2Time: 2021-01-20T05:24:22.7689085ZDetails:DataSourceKind=CommonDataServiceDataSourcePath=foobar.crm6.dynamics.comMessage=Invalid object name 'dbo.FilteredAccountTDS'.RequestId: TDS;a2c61dc8-b400-4d34-b66f-3c30157f0a42;2Time: 2021-01-20T05:24:22.7689085ZErrorCode=-2146232060Number=40000Class=16If you try accessing it
using SQL Server Management Studio, the result is pretty much the same:
What is this Filtered nonsense you’re talking about? I have no knowledge of this FilteredAccountTDS view, my dude.
SQL Server on behalf of Dataverse
Support request raised, screens shared, emails exchanged. The solution, believe it or not, is in the best traditions of
The IT Crowd. Seriously, go to
Manage Feature Settings, turn TDS off then turn it back on. Rumor has it that there was an update applied recently and, if you had TDS enabled during that update, few things may have gone south. Flipping the switch fixes that.
Источник:
https://crmtipoftheday.com/1393/if-t...-does-not-work