Setup Mappings: Static Value Round Mapping

There are a number of useful round mapping options that can be added on the Static Values page. Note that these options should be configured to a Yes value and they should never be used together. The behavior of each item conflicts with the others, and mapping more than one of these at the same time will result in unpredictable outcomes. These can be set on Form import or as Static Mappings in Upload Dataset. 

App: Round Always Create

Add this Static Value if the desired behavior is for Slate to always create an application using the Round that is mapped, even if the record already has an application in that Round. (This overrides Slate’s default behavior.)

App: Round Use Existing

Add this Static Value if the import should use an existing application in the active period, even if the application is not in the same Round that has been mapped.

Setting the App: Round field destination for one of your columns ensures that records with no application will have one created. Adding the App: Round Use Existing static value in Setup Mappings also ensures that records with an existing application in any Round (in an active period) have that application updated. This Static Value preserves the existing application Round information. This is typically useful if you have more than one application source, and you want to prevent a record from having multiple applications in the same application period. It is also useful if you have a Part One application.

For example: A student applied using QuestBridge with an Early Action Application Round. The student later submitted a Common App application with "Regular Decision" mapped for the Application Round. App: Round Use Existing is added as a Static Value and is mapped to Yes. The Common App data updates the existing Early Action application. The application is still in the Early Action Application Round.

App: Round Use Existing and Update

This Static Value is similar to App: Round Use Existing with the sole difference that if a record already has an application in the active application period, the Application Round for that application is updated to match the Round mapped in that import.

For example: A student applied using QuestBridge with an Early Action Application Round. The student later submitted a Common App application with "Regular Decision" mapped for the Application Round. App: Round Use Existing and Update is added as a Static Value and is mapped to Yes. The Common App data updates the existing Early Action application. The application is now in the Regular Decision Application Round.

Was this article helpful?
2 out of 3 found this helpful