Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowData Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more
Hello
I can't find any documentation on importing multiple dataframes into a python visual.
By default the python visual places all selected dimensions and measures together:
Solved! Go to Solution.
Hi @Anonymous,
A limitation of visuals (core, custom, R, Python or otherwise) is that they can only execute a single DAX query , and therefore only contain a single dataset, so it is not possible to use two independent data frames. The only way around this might be to to combine all the data as a single dataset and then process into independent data frames accordingly before you start doing your main body of work.
The boilerplate code is a series of comments informing you what pre-processing Power BI does to the dataset prior to the point where you add your code, as well as how to access the visual data (i.e. though the named dataset variable). If this were missing and you had not read the relevant documentation then it might not be clear how to proceed withough seeking information elsewhere. It's basically a succinct version of this section of the doc:
As you select or remove fields, supporting code in the Python script editor is automatically generated or removed.
Based on your selections, the Python script editor generates the following binding code.
- The editor created a dataset dataframe, with the fields you added.
- The default aggregation is: do not summarize.
- Similar to table visuals, fields are grouped and duplicate rows appear only once.
Regards,
Daniel
Proud to be a Super User!
On how to ask a technical question, if you really want an answer (courtesy of SQLBI)
Hi @Anonymous,
A limitation of visuals (core, custom, R, Python or otherwise) is that they can only execute a single DAX query , and therefore only contain a single dataset, so it is not possible to use two independent data frames. The only way around this might be to to combine all the data as a single dataset and then process into independent data frames accordingly before you start doing your main body of work.
The boilerplate code is a series of comments informing you what pre-processing Power BI does to the dataset prior to the point where you add your code, as well as how to access the visual data (i.e. though the named dataset variable). If this were missing and you had not read the relevant documentation then it might not be clear how to proceed withough seeking information elsewhere. It's basically a succinct version of this section of the doc:
As you select or remove fields, supporting code in the Python script editor is automatically generated or removed.
Based on your selections, the Python script editor generates the following binding code.
- The editor created a dataset dataframe, with the fields you added.
- The default aggregation is: do not summarize.
- Similar to table visuals, fields are grouped and duplicate rows appear only once.
Regards,
Daniel
Proud to be a Super User!
On how to ask a technical question, if you really want an answer (courtesy of SQLBI)
Thank you Daniel
I was hoping the boilerplate would get executed at some point internally so I was trying to force two dataframes in it but now I understand it's really just documentation.
So I'm back to square one
Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |