We would love this functionality as well. As a workaround for customers with Fusion it is possible to setup an ESS Jobset that can contain multiple ESS report jobs and would all be executed at the same time (or serially) when the Jobset is run.

@MandeepGupta The CR LF should only occur at the end of the last 'ZBL' line for each record (in cases where there may be more then on 'ZBL' record before starting over at the 'MSH' header record again (for next recordset). The line containing just the CR LF I do NOT want between recordsets I do NOT want. Where as now all…

@Ian.Gooderham were you able to find a solution to this in Fusion BI Publisher? We would like to setup a dynamic filename with the current date to be output to FTP server. I know we can achieve this using a Bursting query defined in the Data Model, but I was wondering whether we can also accomplish this directly in the…

@Mallikarjuna Kuppauru-Oracle I appreciate the feedback, however I still am confused why an external (non-Oracle) tool can query the same data much quicker than the Oracle Data Model can? I should clarify that this is our BIP within Oracle Fusion.

@Colin Hall We also moved from another (on-prem) ERP system 2 years ago, and while I definitely agree they should allow for increasing this limit, BI Publisher is a more robust reporting and data extract tool that (for the most part) does not have this restriction. As a Developer, BI Publisher is definitely my…

Thanks @Mallikarjuna Kuppauru-Oracle I had thought of using a UNION in the bursting query to achieve this.

Any feedback on this?

I am also facing the same issue, I can not connect to an Azure SFTP server. I will have to use an external FTP transfer tool instead because of this limitation.

This is definitely needed, and will help overcome the .xls 65k row limitation and allow us to embed formulas directly into the template, for which we can not do inside an RTF template.

Please increase this limit to at least 250k rows. This limitation has forced us to re-write several OTBI analyses into BIP Data Models/Reports and required a lot of development time migrating the Logical SQL into Physical SQL, in order to avoid this hard limit.

This is vastly needed! Similar tools like SQL Connect by SplashBI exist and has an IDE-like interface and can connect to Oracle BIP/Cloud instances, much like other traditional SQL Developer client applications, and Oracle needs to implement something similar.

Please increase this limit to at least 250k rows. This limitation has forced us to re-write several OTBI analyses into BIP Data Models/Reports and required a lot of development time migrating the Logical SQL into Physical SQL, in order to avoid this hard limit.

Upvoted - This is needed functionality to trigger BIP Reporting from the ESS Job side.