Known Issues
Limitations
Adding
a Character Constant to the Select Statement of an Object
- If you add a character constant
to the Select statement of an Object, you should join it with the
"||" concatenation symbol not the "+" symbol.
Example: City.city || 'a'
Universe Revision Numbering
- The revision number of the universe is not counted correctly each time you save or export the universe.
Authentication
- In Designer, you cannot have a dynamic DB
connection if NT authentication is enabled.
Automation Object Model
- For more information regarding Automation Object Model,
click here.
Miscellaneous
- When exporting universes that include characters that are
not supported by the repository's connectivity, for example the Euro symbol for a Sybase
connectivity, the connection may be lost. If this occurs, you should close and then restart Designer to recreate the repository connection.
- When you create a measure object, the
aggregation function by default for the measure is Sum. If you select None
for this function, incorrect results can be returned if an end user is using
multiple data providers. If end users will be using multiple data providers
to create reports, you should use Sum as the aggregation function.
- Objects separated by
commas are no longer supported for concatenation. A formula with two objects
separated by a comma does not take into account the second object. You must
redefine the SQL.
Import Universe with ODBC Connection
- When importing a universe with a List of Values,
using an ODBC connection, you may receive the following message: Could
not retrieve columns of universe tables. The associated universe connection
is not valid. It is possible to use the universe correctly, except when
using the Refresh Structure function.

There is no security setting for Automation features
distinct from interface settings in the Supervisor module. Access rights to an Automation
object are the same as those for the interface items.
Limit Execution Time Option
- The Limit execution time to option on the
Controls tab of the Universe Parameters dialog box is not supported for
Oracle connectivities. This
option limits the duration of the fetch phase of a query.
Restrictions on Derived Universes
Deriving a universe is a powerful feature that simplifies
the maintenance burden on your universes. However, it is complex
and entails certain restrictions:
- Contexts are not inherited in a linked
universe.
- While carrying out a SQL request on tables of the core
universe, the data is retrieved from the database defined by the connection of the linked
universe.
- In Designer, after changing a source, it is advisable to
close the universe then re-open it in order to initialize the components( List of
Values,...)
- When you "Include" a core universe, a custom list
of values for the core universe is not included in the derived universe. The lists of
values for the universe, derived from objects of the Core universe, can be affected by an
"Include" or a "Change Source" function on the universe core. We
recommend that these values are checked after one of these operations.
Object Names
- You should not create two or more objects with similar names, where the
only difference in their names is a special character (".",
"&", "#", " ", "'",
":", "-" "/", "", "(",
")", "{", "}"). For example, two objects
called object1&object2 and object1#object2. This will cause problems
when the objects are exported to Excel.
Universe File Names
- To avoid naming conflicts in the repository, we recommend that you
do not create universes with the same name and using a different case. For instance, you should
not create a Beach.unv, and then a beach.unv. The export now controls the uniqueness of
the universe name, independently of the case. However, if you have such universes in your
repository, Designer prompts you before overwriting (for instance, Beach.unv by
beach.unv).
Importance of Syntax
- You can no longer rename a connection after its creation.
- In general, we recommend you avoid certain characters in
object names or in class names such as commas, parentheses, less than and greater than
symbols.
- When defining external strategies in Storaen.txt for
instance, remember that parameter names are also case-sensitive.
- When you use an external strategy, we recommend that you
check that no spaces have been inserted in table or column names. An external strategy can
support spaces in the Qualifier or Owner column.
- In order to avoid problems with databases on export time, if
you enter a long description for an object, we recommend that you use Ctrl+Enter to make a
carriage return instead of space characters.
External strategies
- If you use an external object strategy to create an alias,
the alias does not correspond to a table in the database. If you try to
access the properties (using the Edit Join dialog box) for a join between a
table and the alias,
an error will be generated. You need to manually create the alias to access
the Edit Join dialog box.
Alias tables
- When you create an alias with Designer, the name length
limit is 110 characters. However, certain RDBMS, for example Informix and DB2, are limited
to 18 characters. When you create your universe, you need to use the rules of your RDBMS
when naming tables and aliases.
List of Values
- When you customize a list of values, a file with a
.lov
extension is created in the \UserDocs\UniverseName folder or
\UserDocs\RepositoryName\DomainName\UniverseName folder. If you intend to distribute your universe using a floppy disk or the file
system, you should ensure that you copy the .lov files with the .unv files.
- LOV queries do not use aggregate-aware functions. If
an @aggregate-aware object is defined, the default LOV query is built with the first
argument in the @Aggregate_Aware function.
- To display the
complete list of
values of an object you must select all the values. Workaround: You can
display all the list of values for an object by:
Typing this formula in the Where clause of the object:
Table.Field IN @Prompt('Message (type all for all values)','A','MyClass\MyObject',multi,free)
or
'all' in @Prompt('Message (type all for all values)','A','MyClass\MyObject',multi,free)
- You cannot run a query if the
SQL sentence exceeds the allowed limit of 65536 characters.
Miscellaneous
- Custom Format: you have to select a category before you can
add a custom format in the Number tab of the new Object Format dialog box in Designer.
- If you have Business Objects
Designer installed on the same machine
as a WebIntelligence server the customized list of values can not be taken into
account when you launch Zero Admin Business Objects from a client
machine.
-