Commands used for personal data merge feature Passed some personal data, this commands converts the data into a standard form, which is then cached for the duration of the session. The output contains metadata information about the personal data. The base model that should be used to determine the restrictions governing the physical characterisics (size, row count etc.) of personal data. If not specified, the default values will be nforced. Content of the personal data uploaded to the server Given one or more personal data specification this command creates/replaces a personalized package that augments the base model with query subjects that represent individual personal data sources. Specifies where the target package should be saved. If left unspecified, the package will be saved under user's My Folders using the same name as the first personal data Retrieves any personal data specification defined for a given model. Governor settings in effect, as spcified in the base model. Retrieves detailed query item information for a given query subject within the model. Executes the specified report and stores the result, as Cognos XML, in the session. The result metadata is returned. When true, the item may be used in a relationship, otherwise not Represents the personal data set. Note type and name, if left unspecified, will be defaulted based on source file extension and name. The path to the file originally used. When set to true, the server will attempt to access the file (using the specified sourcePath) if content is not already cached in the session. It is up to the client to ensure the file is accessible. Represents query subject metadata How personal data object is related to an object in the base model or to a tabular extract. When dealing with base model targets, this property is used by the client to locate the target object in the package (using MQP's path protocol). Cardinality on the side of the personal data object Cardinality on the side of the target Whether this relationship links personal data to an object in the base model or the tabular extract? Represents a report and its output which is used in joining personal data with DMP/OLAP objects The ID of the container, namespace for example, under which the personal query sibject and the tabular extrat and other information appear. This value is populated by get command and is used primarily during update. Search path to the model in the base package Represents the a report and its output which is used in joining personal data with DMP/OLAP objects The metadata representing report projection items