What are the different types of IDs used in the BusinessObjects Enterprise repository?

Here is a brief overview of the available ID types in BusinessObjects Enterprise:

  • ID (Object ID): A 32-bit number that will uniquely identify an InfoObject within a single CMS Repository (i.e. within a single cluster). Because IDs are simple numbers, they are efficient to use and query for. There is no guarantee that object IDs will be unique across clusters. Do not use the SI_ID to hard-code a reference to another infoObject. The SI_ID of most infoObjects will change during migration and federation.
  • CUID: CUIDs are Globally Unique Identifiers that uniquely identify an InfoObject, both within a single CMS cluster and across multiple CMS clusters. Because CUIDs are strings they are less efficient to use and slower to query for. Unlike an object’s ID, an object’s CUID stays the same when it is migrated to a new cluster. BIAR engine and Import Wizard always refer to CUID. When exporting an object to a new system (e.g. from development to production), the CUID stays the same, therefore you can hardcode a CUID (for example in an OpenDocument link).
  • GUID: GUIDs are similar in function to ObjectIDs except that they are longer and therefore take longer to process (up to 26 bytes; Object IDs are 32 bits). For this reason people tend to use Object IDs rather than GUIDs.
  • RUID: A RUID is a string ID that uniquely identifies an InfoObject within an object package. (A user uses an object package to schedule multiple objects at the same time). No two objects in an object package have the same RUID. InfoObject instances refer to each other by RUIDs, because they do not change during scheduling. That is, objects in the same package can refer to each other using the RUID, and when instances are generated none of the links are broken.

Webi Rich Internet Applet

– Tuning Perfomance Tips: This wiki page will go into detail on some tips, tricks and known issues that can affect the performance and load time of the RIA designer.

– JRE Issues: he purpose of this page is to consolidate and proactively provide information around Web Intelligence Rich Internet Application applet (RIA) and the Oracle Java Runtime environment

– Setting up the correct client-side JRE for Webi Rich Internet Applet

Converting rows into a single cell (comma separated list) in WebI

A couple of ways to fix a typical end user request (that I have agreed, but this is another long story….). By the mean this is a way to say “yes” and pass to another more interesting task

Solution at universe level

Solution at report level (using webi variables)

SAP BusinessObjects BI Universe Connector Technical Guide

The SAP BusinessObjects BI Universe Connector is a Web Service API allowing applications to connect to Universe data and metadata.   With this connectivity, developers and IT can provide interoperability between SAP BusinessObjects BI 4.1 environments and other applications

More info at this link