This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
Hi,
Ok, I have asked this in another format (dates, with no solutions). The difference here is that I have a unique list of IDs (Sequence #s) from a query. I want to pull records from a large table and only the records that match the ID from the other query. I do not want to load all those records and then filter.
I am connecting to an older Oracle database in a fragel environment. I want to limit my data pull and load only the records from the other query.
The field in the database is a number field. Once I create a list from the other query, I get an error when trying to combine from the list to pull just those IDs.
Again, I do not want to pull 100s of thousands of records just to filter down to 90 - 500 records. I have exhausted my search and have tried many different solutions with no results.
Can anyone help?
Solved! Go to Solution.
@rjs2 Best thing, create a view on the Oracle server that does an inner join between the tables. Or, use a Merge query to do the same in Power Query (might fold)
@Greg_Deckler I think I will just pull the history table with the record table, then reference that to a new table to build the history table off that. And just clean up the record table to remove duplicates. It may even run faster that way.
I really wish there was a way you could do more in the WHERE clause.
@rjs2 Best thing, create a view on the Oracle server that does an inner join between the tables. Or, use a Merge query to do the same in Power Query (might fold)
I should have added that I cant make any views or stored procedures in our environment due to restrictions.
The table I am connecting to is a history table for the customer record that logs changes.
So you are saying there is no way for me in PBI to make a list from query1 of seq# and then use that list in the WHERE clause of query2 from the history table to only pull and load records associated with those seq#?
@Greg_Deckler I think I will just pull the history table with the record table, then reference that to a new table to build the history table off that. And just clean up the record table to remove duplicates. It may even run faster that way.
I really wish there was a way you could do more in the WHERE clause.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 29 | |
| 22 | |
| 21 | |
| 20 | |
| 15 |
| User | Count |
|---|---|
| 64 | |
| 41 | |
| 24 | |
| 22 | |
| 22 |