Below is a WordPress-ready weekly roundup template. You didn’t provide any source items (the JSON payload was empty), so this edition uses placeholder bullets and links that you can replace with the real articles when you have them.
Oracle Analytics (OAC & OAS)
1. Placeholder: New Visualisation Enhancements in Oracle Analytics Cloud
TL;DR: Oracle Analytics Cloud continues to refine its visualisation layer, with incremental improvements around layout, filtering, and interaction patterns. These changes are small but useful for day-to-day dashboard authorship and consumption.
In this week’s OAC updates, the focus is on incremental UX and productivity gains rather than headline features. The visualisation canvas gets minor tweaks to how filters are applied and displayed, helping authors keep complex pages readable without resorting to custom workarounds. While none of these changes fundamentally alter existing content, they can reduce the friction of building and maintaining dashboards, particularly in environments with many shared workbooks.
For organisations standardising on OAC for both self-service and governed reporting, these kinds of iterative improvements are often more valuable than big-bang features: they reduce training overhead, cut down on “how do I do X?” support tickets, and make it easier to keep a consistent design language across projects.
Source: OAC Visualisation Update
2. Placeholder: Managing Object Migration Between OAC and OAS
TL;DR: A recent article revisits best practices for moving content between Oracle Analytics Cloud and Oracle Analytics Server, with a focus on RPD, catalog objects, and lifecycle management.
Many customers still operate a hybrid landscape with both OAC and OAS. This piece walks through the practicalities of managing content migration between the two, including repository (RPD) changes, catalog promotion, and environment alignment. The emphasis is on disciplined lifecycle management: using version control for RPDs, standardising naming conventions, and documenting dependencies so that content behaves predictably across dev, test, and prod.
It also highlights the importance of understanding feature parity and differences between OAC and OAS. While the core semantic layer and dashboard paradigms are shared, there are cloud-only capabilities and on-premise nuances that can affect how a given analysis behaves after migration. The recommendation is to treat cross-platform moves as controlled releases, with regression testing and sign-off, rather than ad hoc exports.
Source: OAC & OAS Migration Practices
Fusion Data Intelligence (FDI)
3. Placeholder: Aligning FDI Subject Areas with Operational Reporting Needs
TL;DR: A new guide discusses how to map Fusion Data Intelligence subject areas to real-world reporting requirements, especially for finance and HR teams.
FDI continues to mature as the preferred route for reporting on Fusion SaaS data. This week’s content focuses on helping teams translate business questions into the right FDI subject areas and metrics. Rather than starting from the technical model, the article suggests starting from use cases—such as period-close KPIs, workforce movement, or procurement cycle times—and then working backwards to the relevant entities and measures.
The piece also underlines the importance of validating FDI outputs against the source Fusion application, particularly when introducing new KPIs or joining data across domains. This helps avoid “two versions of the truth” and builds confidence in FDI as the canonical analytics layer for Fusion data.
Source: FDI Subject Area Mapping
4. Placeholder: Governance Considerations for FDI Data Products
TL;DR: Another article looks at how to apply data governance principles to FDI-based data products, covering ownership, documentation, and change management.
As more teams build reports and dashboards on top of FDI, governance becomes critical. The article recommends defining clear ownership for key data products (for example, finance owning P&L packs, HR owning headcount dashboards), along with documented definitions for metrics and filters. It also advocates for a simple change-management process so that modifications to FDI-based content are reviewed and communicated, especially when they affect widely used KPIs.
For organisations already running an enterprise data governance programme, the guidance is to treat FDI as another governed domain: register its datasets in your data catalogue, align naming conventions with enterprise standards, and ensure that FDI-based content is part of your regular data quality and access reviews.
Autonomous Data Warehouse / 23ai
5. Placeholder: Cost Management Patterns in Autonomous Data Warehouse
TL;DR: A recent post revisits cost-optimisation strategies for ADW, focusing on workload isolation, auto-scaling, and storage management.
With more analytics workloads moving to Autonomous Data Warehouse, cost control remains a recurring topic. This week’s piece walks through patterns for separating interactive BI workloads from heavy batch processing, so that you can scale compute up and down without impacting end users. It also highlights the importance of monitoring storage usage—especially for staging areas and intermediate tables that can quietly grow over time.
The article suggests practical steps such as tagging resources for chargeback, scheduling scale-down windows for non-critical environments, and periodically reviewing dormant schemas or tables. None of these techniques are new, but applying them consistently can make a noticeable difference to monthly bills.
6. Placeholder: Using 23ai Features with Autonomous Data Warehouse
TL;DR: Another write-up explores how to start taking advantage of Oracle Database 23ai capabilities in an ADW context, with a focus on incremental adoption rather than wholesale redesign.
As 23ai capabilities become more widely available, teams are looking at how to introduce them into existing ADW-based solutions. The article recommends starting with low-risk, additive use cases—such as new built-in functions or enhanced SQL capabilities—before considering deeper architectural changes. The emphasis is on compatibility and co-existence with existing schemas and ETL processes.
For BI developers, the main takeaway is that you don’t need to redesign your semantic layer to benefit from 23ai. Instead, you can selectively adopt features where they simplify logic, improve performance, or reduce the need for custom code, while keeping the overall data model stable.