All Collections
Applications - Passive
Other questions
What happens with Deferred applications or course changes?
What happens with Deferred applications or course changes?

How to show your students as being deferred or changed course using the API

Steph Stevens avatar
Written by Steph Stevens
Updated over a week ago

When you are using Applications with a UCAS or direct applications data feed (Passive Applications), existing applications can be updated with a new academic year of entry or new course details.

All applicants who have Deferred or Changed Course will then be flagged in the application record, which allows you to use that value in touchpoint conditions or in a Segment.

It also ensures that the activity log on the application includes all of the activity on the history of that application, even after the deferral or course change.

In order for this to happen you must specify a unique application ID in the <mis_application_id> field with each application that does not change when an application is deferred or changes to a new course.

Read more about the Passive Applications data feed using our API in the Developer Centre (login using your Student CRM login details).


Q. How do I specify a unique application ID?

A. Best practice is to specify a unique and static application ID using a combination of values from your SRS. The following would be a good example for a UCAS application.

MIS_Applicant_ID + UCAS-Choice-No + UCAS-ApplicationSchemeCode

Q. What happens if the mis application ID changes after a course change/deferral?

A. This will result in a new, orphan application record being created in Applications (APV). We call this an orphan as it's disconnected from the original application record. This may have the knock on effect of inflating the number of application records artificially.

Did this answer your question?