Updating or Inserting a Sales Stage
This topic describes how to update a sales stage (if it exists) or insert a sales stage (if it does not exist) on your Oracle CRM On Demand environment (customer test environment or production).
About the Upsert Operation
The Upsert
command inserts or updates sales stages based on the user
key: BaseName (the language-independent name of the sales stage) and
SalesProcessBaseName (the language-independent name of the sales process).
Oracle CRM On Demand attempts to locate the sales stage specified in the input file based on the user key. If a match is located, then the sales stage is updated. If Oracle CRM On Demand cannot locate a sales stage based on the user key, then a new sales stage is created.
Syntax
The following is the syntax for using the Oracle Migration Tool On Demand client to insert or update a sales stage:
migrationtool -u UserID -s ServerURL Upsert SalesStage SalesStageXML
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.
-
SalesStageXML is the fully qualified path name of the sales stage XML file, for example:
C:\My Files\Short List.xml
If the fully qualified path name contains any spaces or special characters, such as brackets, then it must be enclosed with quotation marks, for example:
migrationtool -u UserID -s ServerURL Upsert SalesStage "C:\My Files\[High Potential]\Short List.xml"
Example of Updating or Inserting a Sales Stage
The following is an example of updating a sales stage (if it exists) or inserting the sales stage (if it does not exist) in your Oracle CRM On Demand server:
migrationtool -u UserID -s ServerURL Upsert SalesStage "C:\Oracle Migration Tool On Demand\windows\repository\SalesStage\[High Potential]\Short List.xml"