This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
Hello,
I am having this abnormal behavior in Power Query editor the first. The first screenshot below from Oracle SQL DB.
when I import it into Power Query editor it does not display data. It shows null meanwhile in SQL it shows data.
Any idea on how to fix this problem
Hi @mjsystemss ,
We wanted to check if your question has been resolved or if you are still facing any confusion feel free to reach out. Providing an update can be beneficial for others who might be experiencing similar challenges.
Thank you.
Hi @mjsystemss ,
Thank you for reaching out to Microsoft Fabric Community and Thanks to @danextian and @Juan-Power-bi for Sharing valuable insights.
Just wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Best Regards,
Abdul Rafi.
I used the paste Query window in the import mode but when I converted the query to a View and imported the data showed. I need to change the data source to a view but it is breaking the work I have done.
I dont have any applied steps in the source.
Have you verified whether you're connecting to the same data source (same server, database, table/view) and not another one with the same schema? Do you have applied steps in the query editor other than data source connection that might be causing the issue? Are there data left if you filter out the nulls?
I have resolved this. I deleted the table and imported it again. I am still interested to know how to resolve the query folding problem.
This is most likely a query folding or data type issue with the Oracle connector.
Perhaps you can see if you're importing a view or a query with complex logic (CASE statements, functions, etc.), Oracle sometimes returns nulls when Power BI pushes certain operations back to the database that the source can't handle cleanly.
Try adding a step right after Source to disable query folding: Table.Buffer(Source) — this forces Power Query to pull all the data locally before applying any transformations. If data shows up after that, query folding is the culprit.
Also check the data type Power Query assigned to those columns. If it's detecting the wrong type and casting nulls, removing the "Changed Type" step temporarily will tell you if that's the issue.
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 34 | |
| 31 | |
| 30 | |
| 21 | |
| 16 |
| User | Count |
|---|---|
| 63 | |
| 53 | |
| 31 | |
| 23 | |
| 23 |