After you set up a connection to Workday, you can create an import and configure these settings.
|
Settings |
Instructions |
|---|---|
|
General |
|
|
Name your import • |
Provide a clear and distinguishable name. You will have the option to choose this import throughout integrator.io, and a unique identifier will prove helpful later when selecting among a list of imports that you’ve created. |
|
Description |
Describe your import so that you and others can quickly understand its purpose. Be sure to highlight any nuances that a user should be aware of before using this import in a flow. As you make changes to the resource, be sure to keep this description up to date. |
|
Connection • |
Select an existing Workday connection. If you want to create a new connection, see Set up a connection to Workday. |
|
One to many |
When importing records, the default for One to many is No. If you've got a scenario where you want to use One to many, that is, you have a single record that internally needs to create multiple records, see Create a one to many import including nested arrays |
|
How would you like the records imported? |
|
|
Choose type • |
Use SQL query once per record is the default selection. When you create an SQL query , it must include Example
Tip
|
After you configure the required settings, click Save.
These import settings are optional, and typically don't have to be configured. However, if required in your scenario, you can configure these settings.
|
Settings |
Instructions |
|---|---|
|
Mock output |
|
|
Mock output |
|
|
Advanced |
|
|
Concurrency ID lock template |
Enter a handlebars template that generates a unique id for each imported record. integrator.io uses the raw imported data to generate the IDs (before any import or mapping logic is invoked), and uses the ID to verify that no two records with the same ID are submitted for import at the same time. For example, if you are exporting Zendesk records and importing them into NetSuite, then you would most likely use {{id}} (the field Zendesk uses to identify unique records). In this case, no two records with the same Zendesk id value would import into NetSuite at the same time. This setting prevents integrator.io from sending duplicate records simultaneously if the connection associated with this import is using a concurrency level greater than 1. The connection associated with your import can be configured to limit the number of concurrent requests that can be made at any one time. If you are allowing more than 1 request at a time then it is possible for imports to overlap each other if multiple messages/updates for the same record are being processed at the same time. This settings allows you to enforce an ordering across concurrent requests such that imports for a specific record id will queue up and be processed one at a time (while still allowing imports for different record ids to process in parallel). |
|
Data URI template |
When your flow runs but has data errors this field can be really helpful in that it allows you to make sure that all the errors in your job dashboard have a link to the target data in the import application (where possible). Use a handlebars template to generate the dynamic links based on the data being imported. The template you provide will run against your data after it has been mapped, and then again after it has been submitted to the import application, to maximize the ability to link to the right place. For example, if you are updating a customer record in Shopify, you would most likely set this field to the following value https://your-store.myshopify.com/admin/customers/{{{id}}}. |
|
Invoke |
Copy the URL if you want to invoke this resource via an HTTP request. |