Forum Discussion
Super UserOLE DB OR ODBC error: We cannot convert the value null to type Table
Please read this (ideally the entire series too) Power Query M Primer (Part 21): Identifier Scope & Sections | Ben Gribaudo
These tools use different implementations of the Power Query engine. Power BI has much tighter restrictions around cross partition data bleed etc.
Super User
I though it would simplify things, rather than hard-coding all of the names, to generate a list of queries (using #sections) and then I could simply select the particular queries I wanted to include in the report.
Dynamic number of queries is not supported in Power Query. Each partition needs to be predefined.
Run this whole thing in a single partition and add the query identifier as a column.
Super UserCan you elaborate?
I'm not sure what you mean, nor how to implement what you say.
Could you perhaps create an example using my three sample queries as a base, to create something that will not produce the Power BI error when I close and apply, and avoid my having to hard code every query I want to include in the final report?
Although, for my purposes, I have solved the problem by transferring all the queries to Excel. In Excel, I can apparently select my list of relevant tables from the #sections, and can Close and Load successfully to the worksheet.
Still curious about this business in Power BI.
- lbendlin
Please read this (ideally the entire series too) Power Query M Primer (Part 21): Identifier Scope & Sections | Ben Gribaudo
- ronrsnfld
Thank you for that.
I will go through it and circle back if I still have questions.
- ronrsnfld
lbendlin I went through that excellent reference. (Just the one chapter. I have read some of the others).
What I don't understand, though, is why it does work in Power Query (whether accessed via Power BI or Excel) and it can be Loaded in Excel to a worksheet but cannot be Applied in Power BI.