Forum Discussion

tessahurr's avatar
tessahurr
Icon for Microsoft Employee rankMicrosoft Employee
5 years ago

Share your thoughts on DirectQuery for Power BI datasets and Azure Analysis Services (preview)

Hit Reply and let us know what you think of the DirectQuery for Power BI datasets and Azure Analysis Services.  To learn more about this feature, please visit this blog post or our documentation.   ...
General Comment
Anonymous's avatar
Anonymous
Not applicable
4 years ago

Looks like DQ is importing calculated tables (not normal tables) flagged as private. This is irrespective of the "Include tables added later" checkbox. I noticed this after adding some clustering via the standard Scatter Chart visual to one of the datasets.

 

I imagine this would be an issue for those who use private tables to track things - like the dataset template version that I've just started tracking using a private table 😞

 

The below images show the tables selected for import (not the private tables are not listed), and the ClusterMappingTable tables that ended up in the model.

 

 

 

  • jeroenterheerdt's avatar
    jeroenterheerdt
    Icon for Microsoft Employee rankMicrosoft Employee
    4 years ago

    thanks for reporting this - I will look into this!

    • jeroenterheerdt's avatar
      jeroenterheerdt
      Icon for Microsoft Employee rankMicrosoft Employee
      4 years ago

      Anonymous it took me a while to get back to you as we are unable to reproduce this problem. Are you still seeing this issue?

      • Anonymous's avatar
        Anonymous
        Not applicable
        4 years ago

        Been a while since I checked. I'll confirm when I'm back in the office on Monday. I ended up manually modifying the json annotation that controls the schema import using TE3; to remove the tables I didn't want included. 😊 (And haven't made any subsequent changes since...)