nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

Joining Dataset to Subject Area - Left, Inner, Outer Join Options

Megan Terrell

Purpose: create more robust data options with left, inner, outer join options when blending a dataset with a subject area.

Currently when blending a dataset with a subject area there is no option for what type of join. There is this option in the dataflow. We would like this option without having to do a dataflow.

Find more posts tagged with

Delivered

Oracle Fusion Analytics

FDI

Status: Delivered

Comments

User_IKBME

Agreed - this would be a substantial improvement in the user experience for our organization as well.

Luis E. Rivas -Oracle

Blends in OAC are based on a left join. This is because blending is often used for combining data sources that are not directly related. However, if you wish to use other types of joins, this is possible in the Dataset Editor, where all the common join types are supported between tables and LSAs. At this time, there is nothing planned in our roadmap to add additional join types to blending, however, if you could provide some examples of how this would improve your experience, it would help us explore some options.

Bhaskar Konar

https://community.oracle.com/products/oracleanalytics/discussion/comment/62449#Comment_62449

Very helpful.

Thanks for the details @Luis E. Rivas -Oracle!

J.Beckey

It would be useful to be able to choose the join type when the dataset is the primary driver and subject area data is used to enhance it. Left join would be fine if we could define the primary data source.

Marcelo Finkielsztein

voted up.

Richard Long

Voted up for this. Whilst you can use other joins in the Dataset editor I find this is less intuitive for users to do for quick analysis and can also lead to a proliferation of datasets

User_GNIHU

+1 from me

Dorothy Joseph-Oracle

Bret Grinslade - Oracle Analytics-Oracle

There are two features which are delivered.

For a workbook — you can control the Blend behavior (all row, etc.)

For a table or file with a Subject area Local Subject Area, you can create a dataset where you define an explicit join type. Between these two features, I think you can accomplish what is needed.

https://docs.oracle.com/en/cloud/paas/analytics-cloud/acubi/create-dataset-local-subject-area.html

For Blending specifically — what can you not do?

J.Beckey

"For a workbook — you can control the Blend behavior" Is this a new feature? When blending a dataset and a subject area the only options are "Extend a dimension" or "Add facts". These are set automatically. The only other options are the join fields.

Yes, we can use datasets and dataflows to accomplish specific reporting needs but that requires editing the dataset any time additional measures or dimensions are needed. This is not ideal if datasets are shared.