About: Columns Expanding to Match Column Width of Another View or Section
(Doc ID 2392292.1)
Last updated on MAY 14, 2018
Applies to:Oracle Taleo Platform Cloud Service - Reporting for OBI - Version 15A and later
Information in this document applies to any platform.
There are two possible variations of symptoms depending on the current OBIEE setting:
When the setting is set to TRUE:
- Advantages: When Column A contains many varying column widths, Column A will adopt the widest column width. Which will result in a cleaner report without merged columns of all the different column widths.
- Disadvantages: When Column A contains a column with a large width, smaller widths in Column A will adopt that width (e.g. columns matching the width of a graph).
When the setting is set to FALSE:
- Advantages: When Column A contains a column with a large width, smaller widths in Column A will not adopt that width, which will allow other views to retain their original widths.
- Disadvantages: When Column A contains many varying widths, Column A will become a merged column with all the varying widths, so if many views are used or if the view contains many sections, the column could become a merged column of columns with very small widths.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!