Forum Discussion
Default query when opening Power Query?
Hi Anonymous , Thank you for reaching out to the Microsoft Community Forum.
The file is auto opening on Hormel because your target query is part of an active dependency chain (you show Source = Table.Combine({Hormel, #"Not Hormel"}) and several Table.NestedJoin steps).
Make a truly independent landing query. Either create a topmost Landing query with no references or duplicate the Sales history query and inline the actual source steps from Hormel and Not Hormel into the duplicate (rename those local blocks and set Source = Table.Combine({Source_Hormel, Source_NotHormel})) so the duplicate has no incoming arrows in View -> Query Dependencies. Save the PBIX, fully close Power BI and reopen, the editor will then open to that independent query.
Hi,
As far as I know, there is no way to set a default query for Transform data.
In your case Sales history depends on Hormel and Not Hormel, so Power Query opens the first query in that chain (Hormel).
A simple workaround is to create a new query that just references Sales history and move it to the top of the Queries list, or right-click Sales history in the Fields pane and choose Edit query to open it directly.
Would having query merges cause this behavior in PowerQuery?
Hi Anonymous , Thank you for reaching out to the Microsoft Community Forum.
Yes, merges, appends or any step that references another query make that query part of a dependency chain and Power Query auto expands dependency chains on file open. That auto expand is what forces the editor to land on the first child even if you put a Landing item above it. So, the landing item must be completely independent, no Table.NestedJoin, no Table.Combine, no steps that use another query name and no references.