The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi
We have developed a report with stored procedure in oracle sql with some dynamic paramters. The report is working fine in Power BI Report Builder but when we publish it to the power bi service after giving inputs to the parameters in the report. It throws the below error.
Unable to render paginated report
A data source used by this report returned an error. Received error payload from gateway service with ID 230823
Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.GatewayPipelineWrapperException: Substituted: OracleException:Oracle.DataAccess.Client.OracleException (0x80004005): ORA-06550: line 1, column 7: PLS-00306: wrong number or types of arguments in call to
Can you please let me know is there any problem with the report building style as the reports works fine in the local but not in the service
I have the same issue has anyone found a solution for this yet?
Hi, im having the same problem. Unfortunately still no luck on my side. Works well on local. Gives error while calling on Service via Gateway.
So far only got woraround to work in some cases - use SQL instead of calling a procedure directly. And in this case it works for some reason. Although it has its flaws and is way more complex to:
DECLARE P_RC SYS_REFCURSOR;
BEGIN
MSREPORT.REPORT_462.REPORT_462 (P_RC);
DBMS_SQL.RETURN_RESULT(P_RC);
END;
Hi,
Were you able to fix this? It looks like column 7: PLS-00306: wrong number or types of arguments in call to isn't compatible with one of the parameter value(s) sent.
Please let us know.
unfortunally not, the workaround works, but only for single select parameters. For multiselect i need to use select directly rewrite some logic from procedure and use :p_parameter to input values directly to SQL select. The thing im not understanding is why when I use procedure directly it works in report build but it gives error when published to power bi service