How to Clear the Concur Upload Queue

This feature enables yous to bulk upload queue items into a specific queue in Orchestrator using a CSV file. To practice that, first upload your file into your Orchestrator example for a specific queue. Afterwards the file is successfully processed, the independent items are uploaded into the queue according to the selected strategy. Please note that the file must exist populated beforehand using predefined formats so that the upload operation is successful.

There is a series of predefined column headers that you tin can use when building your CSV file, only yous tin also utilize other custom headers. Afterwards successfully uploading the CSV file, information contained in columns with predefined headers is mapped to columns as institute in Orchestrator. Information contained in columns with custom headers is placed under the Specific Data department of the corresponding particular in Orchestrator. See detailed information about column mapping here and an instance here.

📘

Note

The upload is limited to 15,000 items per file. You can lower the limit using the Upload.Queues.MaxNumberOfItems app setting.

---

File Column Header	Orchestrator Field
Reference Mandatory for unique reference queues. Information technology supports all special characters, except double quotes - ".	Reference Notation: References are not compatible with v2016.ii or lower versions of Orchestrator or Robot.
Deadline Must be populated with a date in one of the post-obit formats: YYYY-MM-DD YYYY/MM/DD YYYY MM DD YYYY-MM-DD HH:mm YYYY/MM/DD HH:mm YYYY MM DD HH:mm YYYY-MM-DD HH:mm:ss YYYY/MM/DD HH:mm:ss YYYY MM DD HH:mm:ss	Deadline
Postpone Must exist populated with a date in 1 of the post-obit formats: YYYY-MM-DD YYYY/MM/DD YYYY MM DD YYYY-MM-DD HH:mm YYYY/MM/DD HH:mm YYYY MM DD HH:mm YYYY-MM-DD HH:mm:ss YYYY/MM/DD HH:mm:ss YYYY MM DD HH:mm:ss	Postpone
Priority Must be populated with one of the following values: Low or 1 Normal or two High or 3 If the priority is non specified in the file, the items are uploaded with a high priority, by default.	Priority Mapped to the post-obit values, respectively: Low Normal Loftier
[Custom_Name] The proper name can simply be made of alphanumeric characters: 0-9, a-z, or underscores.	Specific Data Mapped in JSON format. For example: On-Us Check: 5540

Please note that you cannot take empty column headers in your file. More details nearly field descriptions are available here.

📘

Important!

The predefined cavalcade headers are instance sensitive, please brand sure to follow the mapping rules to a higher place. A cavalcade in your CSV named reference is mapped to the Specific Data section, instead of the Reference column.

---

In that location are ii strategies for handling the upload:

• ProcessAllIndependently - processes all items individually and adds them to the queue, if successful. If not, it returns a list of those whose processing failed. Yous have the option to download the list into a CSV file populated with the aforementioned fields as in the initially uploaded file.
• AllOrNothing - adds the items only if all of them are successfully processed. Otherwise, none are added.

---

When uploading queue items to queues with schema definitions in that location are times when you need Orchestrator to interpret String characters as Integers or Booleans in club to match the schema definition.
Dynamic typing is an option that allows you to command how Orchestrator parses string value inside of .csv files used to upload queue items.

Numeric data must accommodate to the definition of a decimal literal. Numerical values greater than 2⁵³ or less than -two⁵³ are not converted to Integer to preserve precision. Make sure to apply the dot every bit a decimal separator and the comma as a one thousand separator.

---

This section concerns calculation items to a queue using a CSV file from Orchestrator. For details on how to add items through automation projects aka workflow blueprint in Studio, see Managing queues in Studio.

1. In the Queues folio, click the corresponding More Actions button for the desired queue, and then Upload Items. The Upload Items window is displayed.

2. Click Browse and select the desired CSV file.

📘

Annotation

You lot cannot apply the transactions .CSV file to upload items to a queue.

3. Click Open. If your file is compliant with the supported formatting rules, the upload operation is successful.
4. Select the upload strategy:
   • Process all independently - processes all items individually and adds them to the queue, if successful. If not, it returns a list of those whose processing failed. You accept the option to download the listing into a CSV file populated with the same fields equally in the initially uploaded file
   • All or nothing - adds the items simply if all of them are successfully candy. Otherwise, none are added.
5. Select the Dynamic typing checkbox if you want Orchestrator to translate string characters in the CSV files equally integer or boolean. This is recommended when uploading queue items to queues with schema definitions when information technology's required to lucifer the schema definition. Read more about dynamic typing. Leave it unselected, if y'all desire strings to be interpreted equally strings.

6. Click Upload. The items are added to your queue according to the previously selected strategy.
7. If you used the Process All Independently option and there are unprocessed items, the Upload push becomes Download and enables you lot to download a CSV file containing the unprocessed items.

---

Let's say you lot upload into a queue the content of the following CSV file. An like shooting fish in a barrel way to create such a file is to populate the data into an excel file and salve it equally a CSV file:

Or y'all can download a CSVfile with all the pre-filled column headers and customize information technology to your needs.

Observe that this file contains 3 predefined columns, having the aforementioned proper noun every bit in Orchestrator (Reference, Borderline, and Priority, highlighted in green) and 2 custom columns (Customer and Color, highlighted in red).

1. Click Upload Items for the desired queue, and select the CSV file. Orchestrator parses the file to ostend it meets formatting rules.
2. Select the desired upload strategies and click Upload to finish the process.
3. Select More than Actions > View Transactions to view the uploaded queue items.

The Transactions folio displays each item uploaded from your file. The information independent within the file's predefined columns is mapped to the columns with the same name in Orchestrator (Reference, Deadline, and Priority, highlighted in green):

The information in the custom columns is mapped in JSON format to the Specific Data department of each item. Click View Details for the desired item to see it:

Updated 5 months ago

---

• Table of Contents
• • Column mapping
  • Upload strategies
  • Dynamic typing
  • Uploading queue items using a CSV file
  • Instance

pearsonkinatim.blogspot.com

Source: https://docs.uipath.com/orchestrator/docs/bulk-uploading-queue-items-using-a-csv-file

Share this post