The “Maximum allowable nested table row count” property is documented. See Excel Output Properties in the Oracle docs. Also, check Doc ID 2813802.1 for details on increasing export limits greater than 20,000 rows.

There isn’t a one-step “overwrite” flag in BI Publisher web services. This is by design to protect catalog integrity(to prevent accidental loss). The workaround is to first check with objectExists(), then deleteObject() or moveObject() the old file, and finally use uploadObject() to add the new one.

Publisher Desktop (Template Builder / Add-in) supports Word 365 64-bit- https://docs.oracle.com/en/middleware/bi/analytics-server/administer-oas/certification-interoperability.html

Also, check - Is It Possible to Get UCM Files in the FND_ATTACHMENTS Tables from BI or a SQL Query? (Doc ID 2781879.1)

Interactive Layout already supports frozen headers by default. Scrollable tables maintain headers and totals while scrolling (see Oracle Docs).

This is an SVSR (Subledger/General Ledger) functional request, not a BI Publisher feature. Please raise this under the Fusion ERP / Financials (GL) Idea Lab.

BI Publisher doesn’t support blackout/run windows natively. Use Schedule Triggers in the Data Model to conditionally allow execution (e.g., only weekdays 8 AM–6 PM). Alternatively, orchestrate via ESS Job Sets or external schedulers to enforce blackout periods.

Direct access to scheduler tables isn’t available in Fusion SaaS. Use Scheduler Web Services (SOAP) to retrieve job status/history (see example blog: How to Create Oracle Analytics Publisher(BIP) Report to Monitor Scheduled Report Jobs)

Delivery to Object Storage is already available in OAC/OAS; under review for Fusion Publisher. https://community.oracle.com/products/oracleanalytics/discussion/21090/bi-report-bursting-to-object-storage

Duplicate of Idea 21090 (Object Storage delivery). Already available in OAC/OAS; under review for Fusion Publisher.

yes, you can move Analyses /Dashboards along with publisher objects using BAR files. OAC: use Snapshots (BAR files), with REST APIs available to create/restore/manage them: docs. OAS: use WLST scripting utilities for BAR export/import. docs

You are correct in your understanding. REST APIs cover report execution/management and do not support direct upload/download of .xdm catalog objects. There is no deprecation or end-of-life announced for the SOAP CatalogService, and no such plan exists. . These services continue to be supported across all flavors (OAS, OAC)…

You can include a CLOB column in the Data Model, wrap it in <![CDATA[ ]]> and set its type to XML. In the RTF template use:<?html2fo:YourColumnName?> This will render supported HTML/XHTML tags as formatted text. Important to note that Complex tags like tables/images aren’t supported. More details along with example here:

Hi, The Publisher REST API “Run report” - Sends a request to the Publisher to run a specific report with report parameters(optional),and the response contains the report output. We have document with examples of runreport request and response. Latest Document REST API for Oracle Analytics Publisher in OAS: Publisher Blog…

Hi, You can try below XSL_FO element in RTF form field- <fo:basic-link external-destination="tel:{/DATA_DS/G_1/MOBILE_NUMBER}">call <?/DATA_DS/G_1/MOBILE_NUMBER?></fo:basic-link> XML: <DATA_DS><G_1><MOBILE_NUMBER>+13011234567</MOBILE_NUMBER></G_1></DATA_DS> Reference: Supported XSL-FO Elements

Hi Carter, Have you checked whether SMTP configuration is correct & working. You can verify by native export/email option- https://docs.oracle.com/en/cloud/paas/analytics-cloud/acubi/email-file-visualization-canvas-or-dashboard.html FYI, you need to configure the email as per OCI documentation , you need to have approved…

Hi Ankur, I would suggest you to handle in Datamodel via customizing the seeded report as there could be performance issue to handle complex logic in RTF. if you want to handle in RTF, you can try using variable and compare the values, something like this - for ex: <?for-each:ROWSET/ROW1?> <?xdoxslt:set_variable($_XDOCTX,…

You can use <DISPLAY CONDITION> in etext template to specifies the condition when a record should be printed. Ex: <DISPLAY CONDITION> sales >= 10000

The following code hides the chart grid - <O1MajorTick visible="false"/> <X1MajorTick visible="false"/> <Y1MajorTick visible="false"/> <Y2MajorTick visible="false"/> Documentation:

Hi @GoSaaS , You might be unable to download Publisher reports as PDF in Chrome browsers due to the way that the PDF plug-in handles embedded content in iframes, refer below documentation for the same -