The Common Application - Previous Mappings

Changes to the Common Application were reflected in data feeds for the 2020-21 application year. While the changes were not enough to warrant a new source format, we enumerate the updates in this article so that you can make any changes prior to activating your imports this year.

Unchanged Source Fields Retain Previous Mappings

Technolutions has updated all existing CommonApp source formats to inactivate the remap settings and set the Remap As Of Date to 2020-08-10. Until the first file is received, remap settings will appear blank. Rest assured, any source fields that have not changed from last year will appear with the same mappings once a file is uploaded, at which point you can update your remap settings, make any necessary changes outlined below, and update any year-specific items, like application round or entry term.

Once you've updated and confirmed your mappings for this year, you may use the Source Formats tool to update the Remap Active setting to Active. All files received will then be imported with those settings.


For testing purposes, we recommend making all changes within production, and then refreshing your test environment and activating the source format there. If the applications are created in the way that you expect, you can then activate the source formats in production. Please note: documents will not be imported into the test environment.

If you are using the scheduled delivery service (SDS) process through Slate for the first time this year, add the CommonApp source formats from the Slate Template Library.

Common App ID Mapping

Accounts have been rolled over for the 2020-21 application year, which means that the Common App ID is not unique to an application. The Field Fusion that has been used the past few years has been removed.  

The Common App ID uniquely identifies a person. In order to make it unique for a specific application, Slate appends the application cycle year to the Slate Common App ID.  As of August 2020, "-2021" is appended to the Slate Common App ID. Each cycle the year will change and the year value will automatically be updated.


Do not edit the Common App ID destination. The mapping of the Common App ID is integral to ensuring that the data and materials are imported to the appropriate record with the necessary timing. As such, it is very important that these fields are not changed from their default mappings, described below. Other pre-mapped destinations may be edited.

Source Formats and Mappings

CommonAppProspects and CommonAppSuspects

These source formats import only person-scoped data. As such, the Common App ID source field is mapped exclusively to the Slate External ID field, which is a person-scoped field that is used for matching onto person records during the import process. If the same person is included in a file another year with the same rolled over Common App ID, Slate will appropriately identify that person record as the same person using this data point.



This source format will bring in the data file that will create the application. As such, the desired behavior is to match onto an existing record, if one exists, so the Common App ID is mapped to the same Slate External ID field that the CommonAppProspects and CommonAppSuspects source formats have mapped. Since the Common App ID is unique to a person, but subsequent applications from the same person will have the same ID, the Common App ID is not mapped to an application-scoped unique field. 

The Slate Common App ID is mapped to the Common App ID unique application-scoped field and the App: External ID field.

Both of these fields are application-scoped and are used to match onto the appropriate application record during the import process. These mapped fields are what the subsequent data and PDF files from Common Application use to match onto the appropriate application.

CommonAppRecommendations, CommonAppPayment, CommonAppWriting, and CommonAppCourses

These source formats should not have the Common App ID source field mapped at all.  Those files should only import data to the existing application. These files should never create a new application or match onto a different existing application if the application with the Common App ID does not already exist.

For this same reason, identifying information, including first name, last name, date of birth, email address, etc., should also remain unmapped for Payments, Writing, Recommendations, and Courses, as this data will be imported through the CommonApp data feed.

CommonAppRecommendations, CommonAppPayment, CommonAppWriting and CommonAppCourses source formats all have the Slate Common App ID mapped to the application-scoped unique fields Common App ID and App: External ID.


Was this article helpful?
1 out of 1 found this helpful



Article is closed for comments.