Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
I created a new report using the September 2020 Desktop version using Direct Query. It runs fine on the desktop and all M code is folded and I can see the native query.
There are two other small tables that I just keyed in (they relate to how fields will work with the DAX SWITCH() function) but are not used by any of the queries in the M code.
The report is connected to the gateway fine and I can trigger a refresh which works. It is connected to an on-prem SQL Server. Again, 100% functional in the PBI Desktop, and nothing works in the service.
But when I publish to the service, I get this for every visual using the direct query table.
The "technical details" are:
Activity ID3c90c1a5-bd9e-4e8a-b863-2ec6c1cf60ae
Request ID0ede5131-493e-d992-3e6c-83fa8f5b5370
Correlation IDad18f583-2e29-de8b-f94e-7a21076e6e98
TimeWed Sep 23 2020 10:50:50 GMT-0700 (Pacific Daylight Time)
Service version13.0.14296.74
Client version2009.1.02987-train
Cluster URIhttps://wabi-west-us-redirect.analysis.windows.net/
Is anyone else seeing this before I start troubleshooting and open a ticket?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.