Naming conventions for objects in a project

All objects in a project must have a unique identifier. The reference can consist of one or more parts, depending upon the type of object. The parts include an object name and a location in the project hierarchy, as expressed in the default language of the project.

Note: If you want two dimensions or query subjects to have the same name in a project, they must be in different namespaces.

One-part identifiers

Some objects in a project have a one-part identifier. The one-part identifier must be unique across the entire project, even if the namespace contains other namespaces. These objects have a one-part identifier:

  • Namespaces
  • Functions
  • Shortcuts to namespaces
  • Shortcuts to folders

Two-part identifiers

Some objects in a project have a two-part identifier consisting of the name of the containing namespace and the name of the object. The object name must be unique in the containing namespace. These objects have a two-part identifier:

  • Regular dimensions
  • Measure dimensions
  • Query subjects
  • Shortcuts to query subjects

For example, a go_sales namespace contains a query subject named Product. The Product query subject has the following name, where the square brackets and periods are the syntax that Framework Manager uses for object identifiers:

[go_sales].[Product]

Three-part identifiers

Some objects in a project have a three-part identifier based on the identifier of the containing query subject. Each name must be unique in the containing query subject. These objects have a three-part identifier:

  • Hierarchies
  • Measures
  • Query items

For example, a go_sales namespace contains a query subject named Product, and a query item named Product Code. The Product Code query item has the following name, where the square brackets and periods are the syntax IBM® Cognos® Framework Manager uses for object identifiers:

[go_sales].[Product].[Product Code]

Four-part identifiers

Levels in a project have a four-part identifier consisting of the namespace name, the dimension name, the hierarchy name, and the level name.

For example, a go_data_warehouse namespace contains a dimension named Account. A hierarchy in Account is Balance sheet, which contains a level named Account. The Account level has the following name, where the square brackets and periods are the syntax Framework Manager uses for object identifiers:

[go_data_warehouse].[Account dimension].[Balance sheet].[Account]

Five-part identifiers

Some objects in a project have a five-part identifier consisting of the namespace name, the dimension name, the hierarchy name, the level name, and the query item name. Five-part identifiers are also used for captions and business keys in member unique names. For more information, see Member Unique Names.

For example, a go_data_warehouse namespace contains a dimension named Account. A hierarchy in Account is Balance sheet, which contains a level named Account. The Account level contains a query item named Account name. The Account name query item has the following name, where the square brackets and periods are the syntax Framework Manager uses for object identifiers:

[go_data_warehouse].[Account dimension].[Balance sheet].[Account].[Account
name]