Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
4 years ago
Solved

Less Data Issue

Hi All,

I am facing an issue post extracting Data from Data bricks into powerbi.

I checked in data lake the data was upto date. However when post extracting Data into powerbi from data bricks it's showing less number of data even after refreshing N number of times. 

Eg: data contains 48 weeks of data. Post extraction into powerbi it's showing only first 26 weeks of data. Anyone know what's the issue. Please help that wuld be grt thanks in advance. 🙂

@members

 

 

  • Anonymous's avatar
    Anonymous
    4 years ago

    My issue is resolved. But the prob was from access token ND path with host name of Azure DB.. But your solution also helped me alot thanks super user:-)

3 Replies

Replies have been turned off for this discussion
  • Anonymous's avatar
    Anonymous
    Not applicable

    My issue is resolved. But the prob was from access token ND path with host name of Azure DB.. But your solution also helped me alot thanks super user:-)

  • v-jingzhang's avatar
    v-jingzhang
    Community Support

    Hi Anonymous 

     

    Where did you notice the less data issue? If it was in Power Query Editor, it is probably not an issue because it will not load all data rows for preview during data transformation. By default, it shows the top 1000 rows. You can find this at bottom in Power Query Editor. You can change this behavior by clicking on it and switching the option. But no matter which option you select, after applying the changes to Power BI Desktop, you will get all data rows there. 

     

    If this is not the cause, please check steps in Applied Steps pane or open Advanced Editor to see if there is any step or statement that applies some filters to reduce rows in the query? If so, remove these filters and check the result. 

     

    I'm not sure which connector you are using to connect to Databricks. In this official document, the Power BI Delta Sharing Connector has a row limit: The data that the Delta Sharing Connector loads must fit into the memory of your machine. To ensure this, the connector limits the number of imported rows to the Row Limit that was set earlier. Maybe this is the cause if you are using this connector. 

     

    Best Regards,
    Community Support Team _ Jing
    If this post helps, please Accept it as Solution to help other members find it.

     

     

    • Anonymous's avatar
      Anonymous
      Not applicable

      I have connected to Azure Data Bricks