Oracle Transactional Business Intelligence Idea Lab

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Ability to use the the column selector when using logical SQL report.

21
Views
2
Comments

Description

Currently if you are using a custom logical SQL analysis the fields of the subject areas are not available in the Results tab, this is not possible as per application design.
The expected behavior is that when you use custom logical SQL, the fields and subject areas are not available, so you can not drag&drop them to the column selector. 

It would be beneficial if we could change either the selection process of the column selector or if we are able to see the subject areas we are bringing out in the logical SQL report to be able to select the right fields for the column selector. 

Use Case and Business Need

We have a requirement to display Level 3 of the organization hierarchy in the HR help desk environment to do some analytics on raised SRs by "Organization  hierarchy level 3". At the moment there is no connection between the "Service" & "Workforce" subject areas therefore we have converted the analysis to logical SQL to link the raised SR to our organization hierarchy. 

We would like to give the end user the option to choose different bar grapes through selecting different columns in the column selector. However this functionality is not available as the subject areas are not displayed when we convert the analysis to logical SQL. 

Currently the organization hierarchy is not available in any of the "Service" subject areas. 

More details

SR: 3-22811671161  

Original Idea Number: 207d7e3596

Tagged:
1
1 votes

Submitted · Last Updated

Comments

  • Gail Langendorf-Oracle
    Gail Langendorf-Oracle Rank 5 - Community Champion
  • Mitch_123456
    Mitch_123456 Rank 2 - Community Beginner

    Hi Gail,

    thanks for your comment. I agree it would be helpful for some users to have an interface or some sort of tool to use Logical SQL. It is very powerful.

    In my case I do know how to write it however it is more around the loss of OTBI functionality where I have a problem.

    It would be helpful if we have some sort of guideline to say if you are converting an analysis to logical SQL that you might lose some functionality such as in my case the use of Column selectors.  

    Kind regards,

    Mitch