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

Limiting “Drill to Attribute/Hierarchy” columns for user in OAC

Nilesh Talekar-Oracle

Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of):

Description (Required):

For Enterprise Application where there can be many columns and Tables in Data Sources.

It may be helpful to limit columns in “Drill to Attribute/Hierarchy” instead of current option of displaying all columns.

So that users can drill now on specific columns and not getting lost in many columns and Tables which don’t have proper naming convention.

Use Case and Business Need (Required):

Good To have if we want OAC to get used for reporting/Analytics on Enterprise Applications as Data source.

Enhancement Request / Service Request:

Enhancement Request

Find more posts tagged with

Analysis and Data Visualization

Needs Votes

Status: Needs Votes

Comments

Anirban Basu-133546

Hi Nilesh ,

I think this is designed to offer more flexibility . there is a search option . we can use that to reach to specific columns faster .

Thanks

Anirban

Nilesh Talekar-Oracle

@Anirban Basu-133546 Thanks for your comments.We were also thinking on same lines.

when we discussed with user below points came out of our discussion.

1> Enterprise Level application have many columns and tables with internal names which are not meaningful for Humans.

2> Even in other application Tables and Columns may not always have meaningful names.

We agree ability to “Drill to Attribute/Hierarchy” on any column gives flexibility.

It also limits users in above cases to “Drill to Attribute/Hierarchy” on specific columns for lack of Limiting “Drill to Attribute/Hierarchy” columns for user in OAC.

Imagine 5 Tables as below.

1> T1 having 20 columns. (Col1,Col2.... ,Col20)

2>T2 having 20 columns. (Col1,Col2.... ,Col20)

3>T3 having 20 columns. (Col1,Col2.... ,Col20)

4>T4 having 20 columns. (Col1,Col2.... ,Col20)

5>T5having 20 columns. (Col1,Col2.... ,Col20)

Now Imagine how difficult it will be for user to perform “Drill to Attribute/Hierarchy”.

Now consider below Example.

Imagine 5 Tables as below.

1> T1 having 20 columns. (Col1,Col2.... ,Col20) :- Col1 only Available for Drill

2>T2 having 20 columns. (Col1,Col2.... ,Col20):- Col10 only Available for Drill

3>T3 having 20 columns. (Col1,Col2.... ,Col20):- Col5 only Available for Drill

4>T4 having 20 columns. (Col1,Col2.... ,Col20):- Col20 only Available for Drill

5>T5having 20 columns. (Col1,Col2.... ,Col20):- Col11 only Available for Drill

It will be much more easier for user to perform “Drill to Attribute/Hierarchy”.

This limitation is resulting in user thinking OAC not designed for reporting or analytics for Enterprise Level application.

Regards,

Nilesh

LipLooi

Agree with the idea. Drill to attributes also can select the calculations that sometimes developers use to do calculations behind but are not supposed to show to the end user, it might serve no meaning to the end user. Having the capability to select only fields we want them to drill into would be ideal.

Rgds,

LipLooi

Shrey Tandon

Yes, we would like to see this applied to OAS as well.