Request File Processing with Calculated Names

Note the following considerations when uploading a request file that uses calculated node names.

Request files with calculated names use the same format as other request files (see Request Load File Format) with the exception of the Name column. If a property has been set up for Calculate and Store, you can leave the name column blank, or you can use the <cn> or <cn ####> keyword. See Understanding the Calculated Name Keywords.

Understanding the Calculated Name Keywords

The following keywords <cn> or <cn ####> (where #### is a string that is used as a unique identifier) can be used when adding a node with a calculated name in a request file.

• <cn>: Used to calculate node names for Add actions only.
• <cn ####>: Provides a unique identifier for the calculated name for Adds and Inserts.

  When a request contains both Add and Insert action, use the <cn ####> keyword with a unique identifier (for example, <cn 1234>) on the Add action, and then use that same keyword with the identifier on the Insert actions. This enables the system to calculate the name for the node during the Add operation (see Understanding Primary Locations), and then use the same name for the insert actions.

  Note:

  The Add action must come first in the load file.

Name Column Processing Overview

The following list provides a brief overview of how the Name column is processed with blank values or the <cn> or <cn ####> keywords when Calculate and Store is set up for a property:

Blank values:

• If an Alternate Name is provided in the file, the alternate name is used for the node.
• If an Alternate Name is not provided in the file:
  • For Adds the name is calculated from the expression.
  • For Updates the name is calculated from the expression if the node doesn't already exist.
  • For Inserts the row is skipped.

<cn>:

• For Adds the name is calculated from the expression, even if an alternate name is provided.
• For Updates the name is calculated from the expression if the node doesn't already exist.
• For Inserts the row is skipped.

<cn ####> (where #### is a string that is used as a unique identifier):

• For Adds the name is calculated from the expression, even if an alternate name is provided.
• For Updates the name is calculated from the expression if the node doesn't already exist.
• For Inserts, if the <cn ####> identifier string matches the identifier string of a previous Add action then the calculated name is used for the insert. If the <cn ####> identifier string does not match a previous Add action, the row is skipped.

Note:

If your request file does not contain a column for Action Code, then the action code for all of the request items in the file is set to Update.