Forum Discussion
Power Query - Turning a VLOOKUP from Excel into Power Query
- 1 year ago
Hi CNFJDF,
Thank you for your response. It's great to hear that you're considering Power BI as an extension of your project.Regarding Merge Queries in Power Query, I understand your concern about excessive columns. By default, Power Query brings in all columns from the merged table, but you can remove unnecessary columns after merging by selecting only the required fields.
Since your goal is to filter out 40+ unnecessary tests and keep only the 10 relevant ones, you might find Table.SelectRows or filtering within Power Query more effective than a direct merge. You can apply a filter step after merging to keep only the relevant test rows.
I trust this information proves useful. If it does, kindly Accept it as a solution and give it a 'Kudos' to help others locate it easily.
Thank you.
Hi CNFJDF,
Thank you for your response. It's great to hear that you're considering Power BI as an extension of your project.
Regarding Merge Queries in Power Query, I understand your concern about excessive columns. By default, Power Query brings in all columns from the merged table, but you can remove unnecessary columns after merging by selecting only the required fields.
Since your goal is to filter out 40+ unnecessary tests and keep only the 10 relevant ones, you might find Table.SelectRows or filtering within Power Query more effective than a direct merge. You can apply a filter step after merging to keep only the relevant test rows.
I trust this information proves useful. If it does, kindly Accept it as a solution and give it a 'Kudos' to help others locate it easily.
Thank you.
After playing around with merges and giving it another chance it is definitley the right course. Thanks.