Can you call an Oracle Stored from a Published Paginated Report

[Anonymous]

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.

Unable to render paginated report

Data for this report could not be loaded due to an on-premises gateway error. A query in this report may be returning a field which is not supported by the on-premises gateway. Please remove any fields containing user-defined types or unsupported gateway types and try again.

[Anonymous · Accepted 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.

[Icey]

Hi @Anonymous ,

What are you using? Power BI Service or Power BI Report Server?

Best Regards,

Icey

[Anonymous]

Power BI Reporting servers are on-premise servers and we only used the cloud based solution.