Oracle Migration Tool On Demand Guide > Migrating Cascading Picklists > Migrating Cascading Picklists >

Updating or Inserting a Cascading Picklist (Upsert)

This topic describes how to update a specific cascading picklist (if it exists), or insert that cascading picklist (if it does not exist) on your Oracle CRM On Demand environment (customer test environment or production). For the purposes of the Oracle Migration Tool On Demand client, this is known as an Upsert operation. This operation is specified using the Upsert command.

An update to a cascading picklist is derived from the cascading picklist system name. That is, if you run an Upsert operation on a cascading picklist where the cascading picklist system name in the XML file is My CascadePickList, and a cascading picklist of the same name exists in the target company, then the target cascading picklist is updated. If the cascading picklist does not exist on the target company, then the cascading picklist is inserted on the target. The matching of the cascading picklist name is also case sensitive. For example, if the cascading picklist system name in the XML file is MY CascadePickList and the target access profile is My CascadePickList (no uppercase Y), then the MY CascadePickList cascading picklist is inserted in the target.

An Upsert operation on a cascading picklist fails if the following conditions occur:

• The parent picklist is the same as a related picklist because looping cascades are not allowed.
• The parent or related picklist references a field that does not exist on the target system.
• The parent or related picklist references a field that is not of type Picklist.
• The related picklist references a parent picklist that is referenced by another related picklist, because multiple parents for one picklist are not allowed.

The Enable Web Services Access and Customize Application privileges are required for an Upsert operation on a cascading picklist.

NOTE:  Related picklist values override the existing picklist values during an Upsert operation.

Syntax

The following is the syntax for using the Oracle Migration Tool On Demand client to update a specific cascading picklist (if it exists) or insert the cascading picklist (if it does not exist):

migrationtool -u UserID -s ServerURL Upsert CascadingPicklist CascadingPicklistXML 

where:

• UserID is the user sign-in ID that has the appropriate privileges to run the Oracle Migration Tool On Demand client commands.
• ServerURL is the URL for the Oracle CRM On Demand server where your company resides.
• CascadingPicklistXML is the fully qualified path name of the cascading picklist XML file, for example:

  C:\My Files\My CascadingPicklist.xml

The Oracle Migration Tool On Demand client requests your Oracle CRM On Demand password, which can be redirected (using the pipe command) to the client program from standard input; that is, from a file, from the command line, or from another program.

Example of Updating or Inserting a Cascading Picklist

The following is an example of updating a specific cascading picklist (if it exists) or inserting that cascading picklist (if it does not exist) in your Oracle CRM On Demand server:

migrationtool -u UserID -s ServerURL Upsert CascadingPicklist "C:\My Files\My CascadingPicklist.xml"

NOTE:  Quotation marks are required only if the path or file name contains spaces.