Currently when searching in OAC when selecting 'Data' both datasets that are manually created datasets (to input into a dataflow) and datasets that are the outputs from a dataflow are shown, it would be useful if these could be separately identified
@Tasha This is a great suggestion. I agree that we should make it more clear which datasets are generated manually versus created via data flow. Currently there is information in dataset Inspect → Developer → Metadata that indicates whether the dataset was created by a data flow.
We want to increase the rest api limit for this payload to incease from current 25 limit to 100. we are calling this api through RF Smart and due to limitation for paging size, the packing units more than 25 does not show up. Can you please increase the limit atleast to 100.…
We have observed a potential issue with dataset refresh schedules when changing the Data Access mode. When a dataset is configured with Automatic Caching, a reload schedule can be defined to refresh the data at specified intervals. However, if the Data Access setting is subsequently changed from Automatic Caching to Live,…
Would like for the old classic BIP bursting feature to be fully Agent aware so that end users no longer need to be concerned with scheduling via the classic console or building out as many BIP reports just to support this one thing.
We have various data sources in Microsoft Fabric and need the ability to build reports in Oracle Analytics Cloud that connect to data sources in Microsoft Fabric. This is an unavoidable reality in today's complex data ecosystems. Microsoft Fabric requires authentication via Microsoft Entra. We opened an SR and Oracle told…
With the OAC Visualization AI Skill, users can potentially extend existing custom visualizations and address limitations encountered in real-world use cases. As an example, we used the AI Skill to enhance the OracleVectorMapsH3 visualization from approximately 10,000 data points to a version supporting up to 50,000 data…