Articles in this section

Export data from Workday

Anitha Abraham
Updated

After you set up a connection to Workday, you can create an export and configure these settings.

Required export settings

Enter all the required • settings in the sections below.

Settings

Instructions

General

Name your export •

Provide a clear and distinguishable name. You will have the option to choose this export throughout integrator.io, and a unique identifier will prove helpful later when selecting among a list of exports/lookups that you’ve created.

Description

Describe your export 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.

What would you like to export?

SQL query •

Write the SQL query to retrieve records based on your requirements and the web services available (that is, the web services included in the Workday connection).

Tip

  • If you're familiar with SQL, enter your query in the box.

  • If you would like to use handlebars, click handlebars_editor.svg to open the Handlebars editor and create your SQL query. To build your SQL query easily and quickly, you can ask Celigo AI to generate a query. Enter a description of your query in plain English in the space provided, and Celigo AI will attempt to generate a query based on your prompt.

Configure export type

Export type •

Select one of the following export types:

Note

Currently, this connector doesn't support the Once export type.

  • All: To export all data, always

  • Delta: To export only data that has changed since the last time the data flow was run

  • Limit: To export a limited set of records, primarily used for testing to avoid syncing lots of data

    Note

    When you select the export type as Limit - export a set number of records , another setting How many records would you like to export? is enabled for you to enter the maximum number of records to export each time the flow runs. The default value is set to one. You can export a maximum of 100 records.

    For more information, see Four different export types to retrieve data in Fine-tune integrator․io for optimal performance and data throughput.

After you configure the required settings, click Preview to check the export. If the SQL query is not executed successfully, revise the Query or Export type values. Then, click Save.

Configure optional settings

These export settings are optional, and typically don't have to be configured. However, if required in your scenario, you can configure these settings.

Optional sections/settings

Instructions

Would you like to group records?

Group records by fields

See Sort and group records

Mock output

Mock output

See Provide mock response data

Advanced

Page size

See Choosing the right page size in Fine-tune integrator․io for optimal performance and data throughput

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 original data in the export application.

Use a handlebars template to generate the dynamic links based on the data being exported. For example, if you are exporting a customer record from Shopify, you would most likely set this field to the following value https://your-store.myshopify.com/admin/customers/{{{id}}}. Or, if you are just exporting a CSV file from an FTP site then this field could simply be one or more columns from the file: {{{internal_id}}, {{{email}}}, etc...

Do not store retry data

Check this box if you do NOT want integrator.io to store retry data for records that fail in your flow. Storing retry data can slow down your flow's overall performance if you are processing very large numbers of records that are failing.

Override trace key template

If this field is set, you will override the platform default trace key field.

integrator.io uses the trace key to identify a unique record. You can use a single field such as {{{field1}}} or use a handlebar expression. For example, this syntax {{join “_” field1 field2}} will generate a trace key template field1_field2.