Forum Discussion
Resolver IPull Records where ID#s are from another Query
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?
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.
3 Replies
- Greg_Deckler
Community Champion
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)
- rjs2
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#?
- rjs2
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.