Forum Discussion
Oracle Query Folding Error: Non-null assertion failure: resource should be available for query
The error is fixed. The powerbi parameter is a number. When you add this to the query string, you have be sure to remove the comma's and points. My solution is to use "F0" in number.to_Text(Parameter,"F0"). The parameter is an integer, so I don't need decimal signs.
No error anymore but it still didn't work like expected. It kept using the default value of the parameter. I tried to link the parmaeter with a column from an other table. But that didn't do anything.
I was able to make the performance better in the underling oracle database. So not urgent anymore...
Hi RomanTesolkin ,
Seems like the dataset is too large or the query is complex such that the memory consumed by the query exceeds the configured limit.
You can try these steps-
1.Remove or isolate complex steps (e.g., custom columns, joins across sources).
2.Use View Native Query to confirm folding is active.
3.Disable incremental refresh temporarily to see if the error persists.
4.Switch to DirectQuery Mode:
5.Ensure lists used in filters are properly typed and constructed.
6.Set both sources to “Organizational” if safe, to avoid blocking folding.
If the error still persists, try raising the issue here
Issues - Microsoft Fabric Community
Hope this helps!
Thank you for your response v-sdhruv .
My report is configured in DirectQuery mode, using dynamic parameters with a native Oracle query. The issue occurs when I filter with string types parameters. If i use hard coded values - all good.
After further investigation, I have concluded that the problem is not with the dataset or the query itself. The same .pbip file refreshes without error for my colleagues and also refreshes successfully when published to the Power BI Service.
This strongly suggests that the issue is a bug or a persistent cache problem specific to my local Power BI Desktop installation. Despite having already performed extensive troubleshooting—including clearing all cache folders, reinstalling Power BI, and using different query methods—the error persists.
The link you provided unfortunately leads to a general suggestions page rather than a place to report this specific issue. Wanted to submit the issue there yesterday..