Overview
This article walks you through creating an Export Task from scratch. This article will focus on exporting a data file. To export documents, visit Creating Document Exports.
Creating a New Export
To create a new export:
Navigate to Data + Automations > Import + Export > Exports.
Click on the + button along the right-hand side.
Select Data, and click Confirm.
Selecting a Segment to Export
After creating the new export task, a sidesheet will appear for your new export. The first tab to display will be the Segment tab. On this tab, you will identify a pre-built segment of records you want to export.
Repeat Fields Based On
Select what each row in your file represents. The default is User Profile, which gives you one row per person. You can also choose a different type of item. For example, choose Applications for one row per application, or Decisions for one row per decision.
If a person has three decisions and you repeat on Decisions, that person can appear on up to three rows.
Export Settings
Item to Export
This setting tells the export how many of each person's items to include. The export applies your order settings first, then picks the items.
All includes every item
First includes only the first item in the list
Last includes only the last item in the list
🧠 Good to Know: The order of the list isn't guaranteed unless you set Order By. If you use First or Last, set Order By so you always get the item you expect.
Choosing Which Items Are Exported
The usual way. When you repeat on something like Applications, a Conditions setting appears. Use it to choose which of each person's items go in the file. For example, only applications for a certain term or status.
In addition to changing the Repeat Fields setting, you can add additional export filtering. For example, when repeating rows on applications, you can create a filter only to export applications with specific statuses for a particular term. You can also pull the latest application on their record or their first. These settings are found below the Repeat Fields settings.
The exception. When you repeat on Alerts, Appointments, Cases, Conversations, Decisions, Decision Checklists, Payments, Tasks, or Transcripts, that Conditions setting doesn't appear. You can still filter these items. Instead, you can choose to apply the matching filters from your source segment, using the checkbox below.
Apply source segment filters to repeated records
Your segment decides which people are in your export. Sometimes your segment also filters on the same kind of item you picked in Repeat Fields Based On. This checkbox lets you decide whether the segment's filters should also decide which of each person's items become rows in your file.
Checked: Only items that match your segment's filters are exported.
Unchecked: All of each person's items are exported, even ones that don't match your segment's filters.
Here's an example.
Your segment includes students who have an Admitted decision. Jane has two decisions: one Admitted and one Denied. You set Repeat Fields Based On to Decisions and Item to Export to All.
With the box checked, Jane's file has one row: her Admitted decision.
With the box unchecked, Jane's file has two rows: her Admitted decision and her Denied decision.
New exports default to the box unchecked. Exports created before this update have the box checked, so they work the same as before.
🧠 Good to Know: This setting only matters when your segment filters on the same type of item you're repeating on. In the example, the segment filters on the decision status. Otherwise, checked and unchecked produce the same file.
🚨 Important: If your export uses First or Last, unchecking this box can change which item is exported. Preview your export before your next scheduled run.
If your export only includes one task per person, even when set to "Repeat Fields Based On: Task" and "Item to Export: All," check the Apply source segment filters to repeated records checkbox. When it's checked, a segment that filters on tasks limits the export to only the tasks that match. To export all of each person's tasks, uncheck the box.
Mapping
You can move to the Mapping tab after setting up the audience you want to export. This is where the bulk of your export work will take place.
Templates
Rather than manually adding columns to your export by hand, you can apply a pre-built template that automatically maps the Element451 fields. A list of system templates is available by default, or you can build your own.
In this article, we'll assume you are not using a template.
Simple Mapping
For some fields, the mapping will be simple. For example, when exporting the first name, you can click "Map to Field," search "First name," and select the first name field.
Advanced Mapping
Text fields, like First Name, require no additional setup. Fields with dates, dropdown fields, and application fields will need additional setup in the field's column settings—open column settings by clicking the
at the right of each row. For more information on the column settings, check out our article on Column Setting Options for Exports.
Column Setting tabs include:
Scope: Defining what the column is related to, such as an application or milestone. Read more about Scopes.
Transformations: Transform the data as it leaves the system.
Validations: Ensuring data meets specific criteria before being exported.
Empty Values: Telling the system what to do with blank cells.
To avoid duplicate rows when exporting data, you can use the Scope setting to map multiple application-specific columns. For instance, set "Repeat Fields Based On" to Person and add fields for each application instance (e.g., scope 1–N for multiple applications). This consolidates data into a single row with multiple application columns.
Configuration
The Configuration tab is where you decide where the export will be delivered and what the file will be named.
Source Settings
Filename: Determine how the file should be named. To add a timestamp within the file name, you can utilize date tokens, [date:now,format=m-d-Y,timezone=local]. For example, app_submits_[date:now,format=mdy,timezone=local].csv would export as app_submits_02272024.csv
Delimiter Character: Clarify how the data should be separated in the file. The default is Comma.
Extension: Clarify the file extension. The default is Comma Separated Values (.csv).
Export first row as a header: Decide if you want the first row of your export to be column headers. The default is toggled on.
Destination Settings
Email: A data export task will be delivered to the email address provided. The email will prompt you to Click to Download.
SFTP
Dropbox
Google Drive
Notification
The Notification tab allows you to receive an email notification regarding the export status. This is an excellent feature if a daily report gets dropped into the SFTP and you want to know if it delivered without logging into the SFTP.
Preview
The Preview tab will allow you to preview records in your export to confirm that everything looks good.
Run Export
After mapping and previewing the outgoing data, you are ready to move on to running the export task.
Click Run Export (if running immediately) or Schedule (if running on schedule). Schedules can mean a one-time run in the future or a repeated run.
Run History
The Run History tab shows the results of all runs executed by the export. Each run result will show the number of records exported by the run and the number of skipped rows in the data file. If a row is skipped, the results will show a warning. Read these warnings to understand why rows were skipped.
Best Practices for Data Management
Plan Your Export Criteria: Clearly define the data you need before configuring the export.
Test Export Settings: Run test exports to verify the output meets your requirements.
Use Filters Wisely: Avoid overly restrictive filters that may exclude necessary data.
By following these best practices, you can optimize your data exports in Element451, ensuring they are accurate and comprehensive.






