Monday, 30 December 2013

OBIEE 11g Release 11.1.1.7 – Nesting Folders in Answers and BI Composer


Since Siebel Analytics days repository developers could achieve one level of nesting in Answers by adding a hyphen at the beginning of a presentation table name, or by adding an arrow (->) at the beginning of a presentation table description. This option offers only one layer of nesting; it does not support multiple layers of nesting.

Starting from 11.1.1.6.2 an additional tab is included called Child Presentation Tables tab in the Presentation Table dialog, which would be used to give the appearance of nested folders in Answers and BI Composer. This feature supports adding multiple layers of nesting, which is believe is a significant improvement from the previous releases.

This blog is an attempt to mention the process of nesting folders. In addition also include the method of convert presentation folders utility to covert metadata to the new structure.

Nested Folder in Answers

An example of nested folder in Answers is as follows.




Presentation layer in the Administration Tool does not display the nesting; the nesting only appears in Answers and BI Composer. Folders only appear to be nested – they are not actually nested in terms of drill-down

Convert Presentation Folders Utility

As I mentioned, in previous releases of OBIEE, repository developers would have included hyphen at the beginning of a presentation table name, or put arrow (->) at the beginning of the presentation table description to achieve one level of nesting. This method will be removed in a future release.

Convert Presentation Folders utility is provided as part of this release which can be used to convert metadata to the new structure to support the presentation table nesting.

The steps used to convert presentation folders utility are as follows

Administration Tool >> Open Repository in Offline Mode >>Utilities >> Select Convert Presentation Folders > Execute

After execution the hyphens and arrows will disappear from presentation table names and descriptions, and the affected tables are listed as child tables for the appropriate parent object.

I hope you find this information useful.

No comments:

Post a Comment