Oracle Communities

Oracle Analytics and AI

Child Item

Not able to replace data set in a report

Summary:

When trying to replace a dataset in a workbook, the replace button is not selectable and greyed out.

Content (required):

When trying to replace a dataset in OAC, after selecting the new dataset and data mapping, we sometimes see an issue where the replace button is not selectable and greyed out. This OJET error can be seen in the console- ojet_base.js:938 Uncaught TypeError: Cannot read properties of undefined (reading '0')

Screenshot 2022-10-31 at 9.11.04 PM.png

Version (include the version you are using, if applicable):

September 2022

Code Snippet (add any code snippets that support your topic, if applicable):

Find more posts tagged with

Oracle Fusion Analytics

Accepted answers

Steve F-2

Since this is an old abandoned thread, and each situation can be unique and requires contextual information, I suggest that you

a.) either start a new thready and supply all the details of your steps, context, situation;

b.) open a service request with the same.

Replace a Dataset in a Workbook

All comments

Mayura79

Am seeing this issue quite often. Any help here is appreciated!

Steve F-2

Since this is an old abandoned thread, and each situation can be unique and requires contextual information, I suggest that you

a.) either start a new thready and supply all the details of your steps, context, situation;

b.) open a service request with the same.

Replace a Dataset in a Workbook

Banjo

We found one way to solve it, although it is a pain. In our case, the Dataset was linked/blended/joined to other Datasets within the Data tab (essentially a snowflake diagram with Facts and Dimensions). Once we removed the linking lines, and the Dataset we wanted to replace was its own floating rectangle, the Replace button became clickable again.

If you similarly have linking lines, BEWARE, these relationships are stored behind the scenes and can impact other Workbooks that also use these dataset relationships, so breaking the lines here can also break them in entirely separate workbooks. Unfortunate, and confusing, but true.

Hope this helps. Good luck!

[Deleted User]

Good point you're raising there, Banjo. The implicit relationships beyond the perimeter of the Workbook in question can be challenging. It's something you best raise as an idea for change in the Idea Lab:

https://community.oracle.com/products/oracleanalytics/categories/idealab-oracle-analytics-cloud-server

I.e. your idea would be that relationships on the Workbook context reside only in the Workbook context and remain encapsulated there rather than being an unclearly defined "overlapping" concept.

Main point of argumentation for the encapsulation would be that there is already a more overarching concept of shared relationships via the (mutli-table) Data Sets or simply multi-source data sets. In-line modeling in Workbooks should have an exclusive Workbook / Workbook-exclusive scope.