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
megank's avatar
megank
Icon for Power BI Team rankPower BI Team
5 years ago

ncmiller The second error you mentioned, "The given key was not present in the dictionary", is a known issue. It's related to measure tables in the source, so you should not see this if you try to connect to a dataset that does not have any measure tables. We're already working on the fix and it will be available soon. 

 

The first error, "Sequence contains more than one matching element", is a new one. It looks like it might be happening during an auto-save. Do you remember if you got the error while connecting to a dataset in live-connect mode, or during conversion to DirectQuery (or you already had data in the report when you connected forcing the DQ mode)? 

ncmiller's avatar
ncmiller
Frequent Visitor
5 years ago

Thanks for the response, I look forward to the fix with the measure table. I'd rather not go back through all my models and switch them over. Question, does that error apply even if the table is a fact table, but all columns are hidden leaving only measures? This looks like a measure table, but still has relationships with other tables. 

 

For the 'Sequence contains more than one matching element' I can get that either when twitching to DQ mode from live-connect, or adding a second DQ model. I've been testing with usage report data models and failed to load a second usage report into the same data model today, though yesterday I was successful. 

  • megank's avatar
    megank
    Icon for Power BI Team rankPower BI Team
    5 years ago

    ncmiller st_oleg illeke612 pr2000 MCornish 

    The fix for the error "The given key was not present in the dictionary" when trying to convert a live connect report or add a new DirectQuery AS source that has a measure-only table is fixed in the latest December 2020 build (version 2.88.702.0) which is available in the Download Center and Microsoft Store (might need to manually check for updates). Please let us know if you're still having issues with these data models! 

    • ncmiller's avatar
      ncmiller
      Frequent Visitor
      5 years ago

      Incredible! What a fast turn around. It works like a charm! 

    • st_oleg's avatar
      st_oleg
      Frequent Visitor
      5 years ago

       

      it works.

      great fast job! thanks!

  • megank's avatar
    megank
    Icon for Power BI Team rankPower BI Team
    5 years ago

    It should only impact measure-only tables (no columns at all). If the columns are just hidden then we don't expect to see this error. 

     

    We'll look into the other issue today. I'll reach out if I need more info!

    • Anonymous's avatar
      Anonymous
      Not applicable
      5 years ago

      megank 

      Here's the error about "RELATED" formula not working.

      • megank's avatar
        megank
        Icon for Power BI Team rankPower BI Team
        5 years ago

        Thanks for the screenshot, Anonymous ! I confirmed with the team that this is by-design. Basically RELATED is not supported for weak/limited relationships, which includes cross-island relationships. This is the same behavior you would see if you were to have a composite model with two SQL DirectQuery sources (because they're in different islands), you can do this for import tables because they're all in the same (local) island.

         

        You can find more info about this on the RELATED function docs here: RELATED function (DAX) - DAX | Microsoft Docs and the section on Limited relationships her: Model relationships in Power BI Desktop - Power BI | Microsoft Docs