Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago

Reduce the Number of Records Pouring In

Hi:

Through an ODBC connection, we chose one view in our database from which to pull records into Power BI.  But, it's a lot.  We're talking millions upon millions.

We tried clicking the "Transform Data" button., as a possible solution.  But, upon trying to fliter the data based upon say "date", we could no longer find any records associated with the general ledger account number we want to report on.

Why would Transform Data not provide all data?

Regardless, what is the best way to filter on data so that the end user is not sitting in front of her monitor waiting for all of the records from the view or table or whatever to finish pouring into Power BI as she is having to do right now?

Thanks!

John

3 Replies

  • HotChilli's avatar
    HotChilli
    Icon for Community Champion rankCommunity Champion

    What is the data source?

    How did you implement the filter- writing a sql statement or using the dropdown from a column heading?

     

    "We tried clicking the "Transform Data" button., as a possible solution.  But, upon trying to fliter the data based upon say "date", we could no longer find any records associated with the general ledger account number we want to report on."  

    - you'll have to read up on Query Folding.  ODBC data connections don't always fold (sending the query back to the data source).  They sometimes download all data requested from the source and then apply any filter.

    Other things to take into account: Power Query defaults to showing 1000 rows in a preview, so that might be why you don't see the data you expect.  Or the SQL might be incorrect.