Option to hide column in Data Visualization

Bharath Raghupathi-Oracle

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

Description (Required):

Request for feature to hide columns in Data Visualizations. This will help is setting up sort in pivot tables.

Use Case and Business Need (Required):

This will help is setting up sort in pivot tables.

This also helps in running a report at a required level of granularity

Enhancement Request / Service Request:

Sahithi Kolasani-Oracle

Need this functionality as sometimes we have to use columns for sorting but don't want to show those columns in the viz.

Branden Pavol

This is another feature that exists in OBIEE but Oracle decided not to include in OAC. What's super frustrating about this is it is actually capable of being done. If you have an Answers report with a hidden column and choose to "explore as workbook" the column will remain hidden. It even shows up as a greyed out field. Unfortunately, there's no way to turn it on or off. So it's smart enough to keep it but not smart enough to let you control it. Very frustrating with the amount of basic functionality DV is missing compared to Answers.

Shaik Gousimiya-Oracle

Yes, this feature should be there as sometimes we have to use columns for sorting but don't want to show those columns in the viz.

Thanks,

Shaik

Anirban Basu-133546

This feature is much required.

Jahnavi-Oracle

Agreed this is required. And has been raised by others as well.

https://community.oracle.com/customerconnect/discussion/633493/ability-to-hide-a-column-in-data-visualization

ALOK SH-Oracle

Yes this feature should required in DV.

Nilanjan Biswas-Oracle

For custom datasets - hiding can be achieved by following, but not for the columns coming from prebuilt subject areas in OAC; https://docs.oracle.com/en/cloud/paas/analytics-cloud/acubi/hide-or-delete-column.html

Marcelo Finkielsztein

Agree this should be possible without using workarounds.

While we wait for Oracle, this is the work around i have used.

1. Edit the properties of the column I need to hide.
2. set [display header] from [Auto] to [Custom]
3. edit each item (header font, data font, subtotal font) to "Arial ", size=1, color=white, background white. (the UI will not offer the number '1' but you CAN type it and it will be accepted!)
4. set the header text of the column to a single dot ".", to make the column narrower

by doing all of the above, you still have a visible column on the DV table; only that it is discrete and friendlier to the end user. You and users can still sort by that column, and if a user right-clicks on the DV Table row and [Edit][Copy Data], the copied data will contain the value of the 'hidden' column.

One more time, agree that all this should NOT be needed (shrug).

Hope this helps ?

Marcelo

CarolineAnderson

This would really come in handy!

Lisa Smith-Oracle

I need hidden columns to use Data Actions that call an api (Launch into another app with the right context). It is much simpler to pass a surrogate key (ID) than the set of user-friendly keys. Also, certain visualizations-such as a sunburst-just aren't workable when I need to include the 'extra' columns that are only required for the api. The key note here is that the data MUST be present within the visualization in order for the data action to recognize/find it.