Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
I have the following Excel Power Query:
let
Source = Sql.Databases("MyConnectionString.datamart.fabric.microsoft.com"),
MyDatabase = Source{[Name="MyDatabase"]}[Data],
MyExcelQuery = MyDatabase{[Schema="model",Item="MyExcelQuery"]}[Data]
in
MyExcelQuery
What did I do?
Does anyone have any insights into this behaviour?
It's got be stumped and I could do with some helpful pointers to work out the root cause of the problem so that I can work around it.
There are multiple users of the report this spreadsheet contains. Forcing a re-query by simply cutting/pasting the power query statement appears to be a universal workaround. Clearing the cache doesn't do that much.
What I'm wondering is what the root cause might be? For example: I'm wondering if an upstream schema change which then arrives in a datamart isn't picked up by the (very simple) query?
Hello @JBCUK,
have you tried deleting/emptying the PQ data cache?
PQ > File > Options and Setting > Options > Global > Data Load > Data Cache Management Options
Best regards from Germany
Manuel Bolz
🤝Follow me on LinkedIn
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 6 | |
| 3 | |
| 3 | |
| 3 | |
| 2 |