Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hello, I have tried to call an oracle stored procedure returning a sys_refcursor and I am getting the below error. Now if I take the same query and use the same parameters it works fine. I know this is an option, but we are converting around 200 reports from OBIEE to Power BI Paginated Reports. I looked online and they are saying it is not possible to call an oracle stored procedure from a published paginated report. I need to know if this is true or is there a work around.
Solved! Go to Solution.
I found out what I was doing wrong. In OBIEE it requires using a OUT parameter for the cursor. This works in local development. However once published it doesn't work. The workaround is to use dbms_sql.return_result(cursorname). This works on the on-premise gateway, but it really doesn't work locally. Go Figure.
I found out what I was doing wrong. In OBIEE it requires using a OUT parameter for the cursor. This works in local development. However once published it doesn't work. The workaround is to use dbms_sql.return_result(cursorname). This works on the on-premise gateway, but it really doesn't work locally. Go Figure.
Power BI Reporting servers are on-premise servers and we only used the cloud based solution.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.