Package com.crystaldecisions.sdk.plugin.desktop.objectpackage

This package provides the functionality to use Object packages.

See:
Description

Interface Summary

IObjectPackage	This interface provides access to the individual BusinessObjects Enterprise objects stored within a package.
IObjectPackageBase	This interfaces represents a top-level container that provides access to the individual SAP BusinessObjects Enterprise components stored within the object package.

Package com.crystaldecisions.sdk.plugin.desktop.objectpackage Description

This package provides the functionality to use Object packages. Object Packages contain a collection of components. These components can be any object that can be scheduled and recognized by SAP BusinessObjects Enterprise, such as Report objects and Program objects. Furthermore, the objects contained within an object package do not have to be of the same type. Therefore, any object that SAP BusinessObjects Enterprise recognizes can be contained within the package, and the package can contain more than one object. For example, an object package can contain a number of Crystal Reports and a batch file, and can be scheduled as a single report object.

Example

If the individual members of a package need to have their plugin or infoObject properties updated, both the enclosing ObjectPackage object and its components need to be retrieved using one query. The most effective way to accomplish this is by retrieving the ObjectPackage object’s CUID and then use the following query:

IInfoObjects objInfoObject = iStore.Query("Select * From CI_INFOOBJECTS Where SI_PARENT_CUID = '" + objPackCUID + "' or SI_CUID= '" + objPackCUID + "' and SI_INSTANCE=0 Order By SI_COMPONENT")

This query will retrieve both the ObjectPackage object and its components with the ObjectPackage object being the first object in the collection. Furthermore, because the Order By clause sorts on the Boolean SI_COMPONENT property, all the objects will be TRUE except the object package itself. Individual items in this collection can then be cast into their respective plugin interfaces and have logon information or parameter information updated prior to scheduling the entire collection.