ApplyTexas
ApplyTexas (opens in a new tab) is a centralized application service for public schools in Texas, provided by the Texas Higher Education Coordinating Board. ApplyTexas offers several transmission options for downloading application data from the platform. These options are accessed via the Admin portal (opens in a new tab). Review the columns below to ensure you have selected the right transmission option.
There are several considerations when importing application data. Please review the “Importing Application Data” help article, specifically to create an application (opens in a new tab) for ApplyTexas and to register the application to decisions (opens in a new tab).
For the template to work for your institution, make note of any notes in the third column below as there may be extra steps to take to ensure the data comes in correct.
New database
435 rows
| Name | Element Notes | Element Slug | Row |
|---|---|---|---|
| non_res_country_code | 1 | ||
| country_legal_perm_res | 2 | ||
| id | 3 | ||
| application_id | 4 | ||
| dest_abbr | 5 | ||
| profile_id | user-identities-stateid | 6 | |
| app_type | 7 | ||
| app_ccyys | 8 | ||
| app_stat | 9 | ||
| app_stat_name | 10 | ||
| school_code_1 | 11 | ||
| school_name_1 | 12 | ||
| major_code_1 | 13 | ||
| major_name_1 | 14 | ||
| school_code_2 | 15 | ||
| school_name_2 | 16 | ||
| major_code_2 | 17 | ||
| major_name_2 | 18 | ||
| tx_res_determination | 19 | ||
| tx_res_exception | 20 | ||
| preferred_email | 21 | ||
| email_addr | 22 | ||
| last_nm | user-last-name | 23 | |
| first_nm | user-first-name | 24 | |
| middle_nm | user-middle-name | 25 | |
| suffix_nm | user-suffix-name | 26 | |
| dob_date | user-dob | 27 | |
| city_of_birth | 28 | ||
| country_of_birth | user-citizenship-country-of-birth | 29 | |
| state_of_birth | 30 | ||
| us_cit | 31 | ||
| hs_name | 32 | ||
| hs_city | 33 | ||
| hs_code | user-education-highschools-ceeb | 34 | |
| hs_country | 35 | ||
| hs_state | 36 | ||
| hs_grad_date | user-education-highschools-graduate-date | 37 | |
| ged | 38 | ||
| ged_version | 39 | ||
| ged_state | 40 | ||
| ged_date_completed | 41 | ||
| acad_suspension | 42 | ||
| created_time | 43 | ||
| submitted_time | 44 | ||
| transmitted_time | 45 | ||
| last_saved_time | 46 | ||
| gender | user-gender | 47 | |
| preferred_nm | user-preferred-name | 48 | |
| province_of_birth | 49 | ||
| hs_province | 50 | ||
| country_of_birth_name | 51 | ||
| hs_country_name | 52 | ||
| cit_country_code | 53 | ||
| us_res | 54 | ||
| alien_number | 55 | ||
| alien_number_date | 56 | ||
| perm_res_app | 57 | ||
| itin | 58 | ||
| alien_permres_intent | 59 | ||
| self_visa | 60 | ||
| cit_country_name | user-citizenship-country | 61 | |
| country_legal_perm_res_name | 62 | ||
| io_curr_reside_us | 63 | ||
| io_visa_held_in_us | 64 | ||
| io_visa_held_in_us_other | 65 | ||
| io_visa_held_in_us_exp_date | 66 | ||
| io_visa_stat_change | 67 | ||
| io_exit_us | 68 | ||
| io_exit_us_date | 69 | ||
| io_visa_type | 70 | ||
| funds_personal | 71 | ||
| funds_gov_private | 72 | ||
| funds_gov_private_desc | 73 | ||
| funds_other | 74 | ||
| funds_other_desc | 75 | ||
| marital_stat | 76 | ||
| app_rep_title | 77 | ||
| app_rep_name | 78 | ||
| app_rep_phone | 79 | ||
| app_rep_country_code | 80 | ||
| app_rep_addr1 | 81 | ||
| app_rep_addr2 | 82 | ||
| app_rep_country_name | 83 | ||
| prev_college | 84 | ||
| three_yr_tx | 85 | ||
| one_yr_tx | 86 | ||
| prev_coll_name | 87 | ||
| prev_coll_ccyys | 88 | ||
| prev_res_status | 89 | ||
| prev_res_basis | 90 | ||
| filed_own_tax | 91 | ||
| claimed_as_dep_this_yr | 92 | ||
| support | 93 | ||
| support_other | 94 | ||
| self_curr_tx_res | 95 | ||
| self_tx_res_yrs | 96 | ||
| self_tx_res_months | 97 | ||
| self_why_move_tx | 98 | ||
| self_tx_mil_home | 99 | ||
| self_tx_mil_legal_state | 100 | ||
| self_tx_title | 101 | ||
| self_tx_title_date | 102 | ||
| self_tx_business | 103 | ||
| self_tx_business_date | 104 | ||
| self_tx_work | 105 | ||
| self_tx_homeless | 106 | ||
| self_tx_spouse | 107 | ||
| self_tx_spouse_other | 108 | ||
| self_tx_spouse_date | 109 | ||
| guar_tx_spouse_date | 110 | ||
| guar_us_cit | 111 | ||
| guar_us_permres | 112 | ||
| guar_alien_permres_app | 113 | ||
| guar_visa | 114 | ||
| guar_curr_tx_res | 115 | ||
| guar_tx_res_yrs | 116 | ||
| guar_tx_res_months | 117 | ||
| guar_why_move_tx | 118 | ||
| guar_tx_mil_home | 119 | ||
| guar_tx_mil_legal_state | 120 | ||
| guar_tx_title | 121 | ||
| guar_tx_title_date | 122 | ||
| guar_tx_business | 123 | ||
| guar_tx_business_date | 124 | ||
| guar_tx_work | 125 | ||
| guar_tx_homeless | 126 | ||
| guar_tx_spouse | 127 | ||
| guar_tx_spouse_other | 128 | ||
| res_comments | 129 | ||
| non_res_country_name | 130 | ||
| non_res_province | 131 | ||
| non_res_state | 132 | ||
| military_vet_status | 133 | ||
| hisp_lat | user-race-hispanic | 134 | |
| ethnic_type | If you are using a regular data source for user-race-categories, you’ll un-map this field and re-map it. On transformations, you’ll want to replace the incoming values with your recognized values. | user-race-categories | 135 |
| deg_sought | 136 | ||
| ult_deg_sought | 137 | ||
| field_of_conc | 138 | ||
| awd_sought | 139 | ||
| enroll_no_award | 140 | ||
| former_student | 141 | ||
| prev_applied | 142 | ||
| gre_taken | 143 | ||
| gre_taken_date | user-unofficial-tests-gre-date | 144 | |
| gre_sent_date | 145 | ||
| gre_verbal | user-unofficial-tests-gre-verbal-score | 146 | |
| gre_quant | user-unofficial-tests-gre-quantitative-score | 147 | |
| gre_analytic_writing | user-unofficial-tests-gre-writing-score | 148 | |
| gmat_taken | 149 | ||
| gmat_taken_date | user-unofficial-tests-gmat-date | 150 | |
| gmat_sent_date | 151 | ||
| gmat_verbal | user-unofficial-tests-gmat-verbal-score | 152 | |
| gmat_quant | user-unofficial-tests-gmat-quantitative-score | 153 | |
| gmat_analytic_writing | user-unofficial-tests-gmat-writing-score | 154 | |
| gmat_int_reasoning | 155 | ||
| gmat_total | user-unofficial-tests-gmat-composite-score | 156 | |
| mcat_taken | 157 | ||
| mcat_taken_date | user-evaluations-date-* | 158 | |
| mcat_sent_date | 159 | ||
| mcat_chem_phys_bio_systems | user-evaluations-cpbs-score-* | 160 | |
| mcat_analysis_reasoning | user-evaluations-cars-score-* | 161 | |
| mcat_bio_living_systems | user-evaluations-bbls-score-* | 162 | |
| mcat_psych_social_bio_behavior | user-evaluations-psbb-score-* | 163 | |
| mat_taken | 164 | ||
| mat_taken_date | user-evaluations-date-* | 165 | |
| mat_sent_date | 166 | ||
| mat_raw_score | user-evaluations-composite-score-* | 167 | |
| mat_pct_general | 168 | ||
| mat_pct_major | 169 | ||
| dat_taken | 170 | ||
| dat_taken_date | user-evaluations-date-* | 171 | |
| dat_sent_date | 172 | ||
| dat_bio_sciences | user-evaluations-biology-score-* | 173 | |
| dat_gen_chem | user-evaluations-chemistry-score-* | 174 | |
| dat_organic_chem | user-evaluations-organic_chemistry-score-* | 175 | |
| dat_perceptual_ability | user-evaluations-perceptual-score-* | 176 | |
| dat_reading | user-evaluations-reading-score-* | 177 | |
| dat_quant | user-evaluations-quantitative-score-* | 178 | |
| lsat_raw_score | user-evaluations-composite-score-* | 179 | |
| lsat_average | 180 | ||
| lsat_pct_rank | 181 | ||
| lsat_taken | 182 | ||
| lsat_taken_date | user-evaluations-date-* | 183 | |
| lsat_sent_date | 184 | ||
| pcat_taken | 185 | ||
| pcat_taken_date | 186 | ||
| pcat_sent_date | 187 | ||
| pcat_verbal | 188 | ||
| pcat_bio_sciences | 189 | ||
| pcat_reading_comp | 190 | ||
| pcat_quant | 191 | ||
| pcat_gen_chem | 192 | ||
| pcat_composite | 193 | ||
| pcat_writing | 194 | ||
| tse_taken | 195 | ||
| tse_taken_date | 196 | ||
| tse_sent_date | 197 | ||
| tse_score | 198 | ||
| twe_taken | 199 | ||
| twe_taken_date | 200 | ||
| twe_sent_date | 201 | ||
| twe_score | 202 | ||
| parent_ed_background_1 | 203 | ||
| parent_relationship_1 | 204 | ||
| parent_ed_background_2 | 205 | ||
| parent_relationship_2 | 206 | ||
| other_lang_1 | 207 | ||
| other_lang_yrs_1 | 208 | ||
| other_lang_2 | 209 | ||
| other_lang_yrs_2 | 210 | ||
| family_income | user-family-household-income | 211 | |
| teaching_cert | 212 | ||
| teaching_cert_type | 213 | ||
| conservatorship_sw | 214 | ||
| conservatorship_info | 215 | ||
| pre_prof | 216 | ||
| intl_transfer_seeking | 217 | ||
| readmit_seeking | 218 | ||
| act_taken | 219 | ||
| act_taken_date | user-unofficial-tests-act-date | 220 | |
| sat_taken | 221 | ||
| sat_taken_date | user-unofficial-tests-nsat-date | 222 | |
| toefl_taken | 223 | ||
| toefl_taken_date | user-unofficial-tests-toefl-date | 224 | |
| toefl_sent_date | 225 | ||
| toefl_type | 226 | ||
| toefl_listening | user-unofficial-tests-toefl-listening-score | 227 | |
| toefl_writing | user-unofficial-tests-toefl-writing-scores | 228 | |
| toefl_reading | user-unofficial-tests-toefl-reading-score | 229 | |
| toefl_speaking | user-unofficial-tests-toefl-speaking-score | 230 | |
| toefl_essay | 231 | ||
| toefl_total | user-unofficial-tests-toefl-composite-score | 232 | |
| ielts_taken | 233 | ||
| ielts_taken_date | user-unofficial-tests-ielts-date | 234 | |
| ielts_sent_date | 235 | ||
| ielts_listening | user-unofficial-tests-ielts-listening-score | 236 | |
| ielts_writing | user-unofficial-tests-ielts-writing-scores | 237 | |
| ielts_reading | user-unofficial-tests-ielts-reading-score | 238 | |
| ielts_speaking | user-unofficial-tests-ielts-speaking-score | 239 | |
| ielts_overall | user-unofficial-tests-ielts-composite-score | 240 | |
| native_lang | If using this field, ensure that the values coming in align with the values you are using. Utilize transformations to make sure the data comes in clean. | user-citizenship-native-language | 241 |
| transient_sem | 242 | ||
| home_schooled | 243 | ||
| number_in_house | user-family-household-persons-count | 244 | |
| family_obligations | 245 | ||
| family_obligations_income | 246 | ||
| family_obligations_income_desc | 247 | ||
| family_obligations_care | 248 | ||
| family_obligations_care_desc | 249 | ||
| family_obligations_other | 250 | ||
| family_obligations_other_desc | 251 | ||
| college_work | 252 | ||
| college_work_hrs | 253 | ||
| college_work_class | 254 | ||
| ib_diploma | 255 | ||
| degree_holder | 256 | ||
| second_bach | 257 | ||
| non_degree_seeking | 258 | ||
| total_hrs_earned | 259 | ||
| phi_theta_kappa | 260 | ||
| last_sem | 261 | ||
| reverse_transfer_sw | 262 | ||
| hs_tech_prep | 263 | ||
| jc_adm_basis | 264 | ||
| jc_reason_attending | 265 | ||
| deadline_type | 266 | ||
| extra_volunteer_module_show | 267 | ||
| summary_education_module_show | 268 | ||
| awards_honors_module_show | 269 | ||
| employment_module_show | 270 | ||
| show_parent_info | 271 | ||
| test_scores_module_show | 272 | ||
| emp_academic_module_show | 273 | ||
| us_or_intl | 274 | ||
| perm_addr1 | user-addresses-home-street1 | 275 | |
| perm_addr2 | user-addresses-home-street2 | 276 | |
| perm_addr3 | user-addresses-home-street3 | 277 | |
| perm_city | user-addresses-home-city | 278 | |
| perm_postal_code | user-addresses-home-zip | 279 | |
| perm_county | 280 | ||
| perm_country_name | user-addresses-home-country | 281 | |
| perm_country_code | 282 | ||
| perm_state | user-addresses-home-state | 283 | |
| perm_province | user-addresses-home-province | 284 | |
| area_addr1 | user-addresses-mailing-street1 | 285 | |
| area_addr2 | user-addresses-mailing-street2 | 286 | |
| area_addr3 | user-addresses-mailing-street3 | 287 | |
| area_city | user-addresses-mailing-city | 288 | |
| area_postal_code | user-addresses-mailing-zip | 289 | |
| area_county | 290 | ||
| area_country_name | user-addresses-mailing-country | 291 | |
| area_country_code | 292 | ||
| area_state | user-addresses-mailing-state | 293 | |
| area_province | user-addresses-mailing-province | 294 | |
| primary_type_of_phone | 295 | ||
| primary_phone_country_code | 296 | ||
| primary_phone_number | user-phone-cell-number | 297 | |
| alt_type_of_phone | 298 | ||
| alt_phone_country_code | 299 | ||
| alt_phone_number | user-phone-home-number | 300 | |
| emer_title | 301 | ||
| emer_first_nm | user-emergency-contacts-first-name | 302 | |
| emer_last_nm | user-emergency-contacts-last-name | 303 | |
| emer_addr1 | user-emergency-contacts-address-street-1 | 304 | |
| emer_addr2 | user-emergency-contacts-address-street-2 | 305 | |
| emer_addr3 | 306 | ||
| emer_city | user-emergency-contacts-address-city | 307 | |
| emer_postal_code | user-emergency-contacts-address-zipcode | 308 | |
| emer_county | 309 | ||
| emer_country_name | user-emergency-contacts-address-country | 310 | |
| emer_country_code | 311 | ||
| emer_state | user-emergency-contacts-address-state | 312 | |
| emer_province | 313 | ||
| emer_type_of_phone | 314 | ||
| emer_phone_country_code | 315 | ||
| emer_phone_number | user-emergency-contacts-cell-phone-number | 316 | |
| parent1_last_nm | user-family-guardian-1-last-name | 317 | |
| parent1_first_nm | user-family-guardian-1-first-name | 318 | |
| parent1_middle_nm | 319 | ||
| parent1_suffix_nm | 320 | ||
| parent1_title | 321 | ||
| parent1_relationship | If using this field, ensure that the values coming in align with the values you are using. Utilize transformations to make sure the data comes in clean. | user-family-guardian-1-relationship | 322 |
| parent1_living | user-family-guardian-1-living | 323 | |
| parent1_reside_with | 324 | ||
| parent1_email_addr | user-family-guardian-email-1 | 325 | |
| parent2_last_nm | user-family-guardian-2-last-name | 326 | |
| parent2_first_nm | user-family-guardian-2-first-name | 327 | |
| parent2_middle_nm | 328 | ||
| parent2_suffix_nm | 329 | ||
| parent2_title | 330 | ||
| parent2_relationship | If using this field, ensure that the values coming in align with the values you are using. Utilize transformations to make sure the data comes in clean. | user-family-guardian-2-relationship | 331 |
| parent2_living | user-family-guardian-2-living | 332 | |
| parent2_reside_with | 333 | ||
| app_status | 334 | ||
| counselor_name | 335 | ||
| counselor_phone | 336 | ||
| scholarship_fafsa | 337 | ||
| funds_applicant | 338 | ||
| funds_others | 339 | ||
| funds_parental | 340 | ||
| appl_marital_stat | 341 | ||
| appl_annual_income | 342 | ||
| spouse_occupation | 343 | ||
| spouse_annual_income | 344 | ||
| fam_live_with | 345 | ||
| fam_live_with_other | 346 | ||
| fam_live_with_mar_stat | 347 | ||
| scholar_parent_relationship_1 | 348 | ||
| scholar_parent_living_1 | 349 | ||
| scholar_parent_occupation_1 | 350 | ||
| scholar_parent_employed_1 | 351 | ||
| scholar_parent_employer_1 | 352 | ||
| scholar_parent_income_1 | 353 | ||
| scholar_parent_relationship_2 | 354 | ||
| scholar_parent_living_2 | 355 | ||
| scholar_parent_occupation_2 | 356 | ||
| scholar_parent_employed_2 | 357 | ||
| scholar_parent_employer_2 | 358 | ||
| scholar_parent_income_2 | 359 | ||
| scholar_step_occupation | 360 | ||
| scholar_step_employed | 361 | ||
| scholar_step_employer | 362 | ||
| scholar_step_income | 363 | ||
| scholar_guardian_occupation | 364 | ||
| scholar_guardian_employed | 365 | ||
| scholar_guardian_employer | 366 | ||
| scholar_guardian_income | 367 | ||
| scholar_more_under25 | 368 | ||
| scholar_nat_merit | 369 | ||
| scholar_hisp_merit | 370 | ||
| fam_special_circumstances | 371 | ||
| why_this_univ | 372 | ||
| why_this_major | 373 | ||
| educational_plans | 374 | ||
| life_goals | 375 | ||
| scholar_created_time | 376 | ||
| scholar_last_saved_time | 377 | ||
| fam_inc_opt_out | 378 | ||
| scholar_step_living | 379 | ||
| scholar_guardian_living | 380 | ||
| No further action required. This formula looks at two columns to pull an email in. IF([C21], [C21], [C22]) | user-email-address | 381 | |
| EDIT: Spring App Term | Scope: Select the Application Type that these applications will feed into. Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built assumes you have your terms set up like Spring XXXX in your data sources. If your term name structure is different, you’ll update the yellow highlighted portion. IF(RIGHT([C8],1)="2",DB_MAP("term",CONCAT("Spring ",LEFT([C8],4)),"name","guid",""),"") Below are a few examples if your term naming structure is different: Spring XXXX Semester CONCAT("Spring ",LEFT([C8],4)," Semester") January XXXX CONCAT("January ",LEFT([C8],4)) XXXX Spring CONCAT(LEFT([C8],4)," Spring") | user-applications-term-* | 382 |
| EDIT: Spring App Major | Scope: Select the Application Type that these applications will feed into. Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built depends on how the majors from Apply Texas line up with your majors from Element451. IF(RIGHT([C8],1)="2",DB_MAP("major",<major column>,"<name or code on data source>","guid",""),"") Below are a few examples for how the DB_MAP portion may look depending on how the majors line up: Names in Apply Texas match Names in Element451: DB_MAP("major",[C14],"name","guid","") Codes in Apply Texas match Codes in Element451: DB_MAP("major",[C13],"code","guid","") Codes in Apply Texas are stored under Custom Codes in Element451: DB_MAP("major",[C13],"custom_1","guid","") | user-applications-major-* | 383 |
| EDIT: Spring App Second Major | Scope: Select the Application Type to the application you want to feed into. Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built depends on how the majors from Apply Texas line up with your majors from Element451. IF(RIGHT([C8],1)="2",DB_MAP("major",<major column>,"<name or code on data source>","guid",""),"") Below are a few examples for how the DB_MAP portion may look depending on how the majors line up: Names in Apply Texas match Names in Element451: DB_MAP("major",[C18],"name","guid","") Codes in Apply Texas match Codes in Element451: DB_MAP("major",[C17],"code","guid","") Codes in Apply Texas are stored under Custom Codes in Element451: DB_MAP("major",[C17],"custom_1","guid","") | user-applications-major-second-* | 384 |
| EDIT: Spring App Student Type | Scope: Select the Application Type to the application you want to feed into. Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: The formula for student type is going to vary. You may want everyone to come in as a First-Time Freshman, or you may want to use another field to determine the student type. If you are wanting every record to come in as the same student type, you’ll put your student type code inside quotes. In the example below, every record will come over as First-Time Freshman if the code in the instance is FTF. IF(RIGHT([C8],1)="2","FTF","") Ultimately, you want the output of your formula to be the codes or values of the student types you use in Element451. Below are a few examples of how to use a data source to map student types in: Using App Type in Apply Texas and it matches Column 1 in your Regular Data Source for Student Types in Element451: DS_MAP([C7],"example.data_source.1234","column_1","column_2","") Using an IF statement to determine student type: IF([C7]="Undergraduate (two - year)","FTF",IF([C7]="Dual-Credit","DC","")) | user-applications-student-type-* | 385 |
| EDIT: Spring App Start Date | Scope: Select the Application Type to the application you want to feed into. Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: No edits required here. The formula just checks the term is Spring and pulls the date from the column and reads it as a date. IF(RIGHT([C8],1)="2",DATE_READ([C43],"m/d/Y h:iA"),"") | user-applications-registered-at-* | 386 |
| EDIT: Spring App Submit Date | Scope: Select the Application Type to the application you want to feed into. Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: No edits required here. The formula just checks the term is Spring and pulls the date from the column and reads it as a date. IF(RIGHT([C8],1)="2",DATE_READ([C44],"m/d/Y h:iA"),"") | user-applications-submitted-time-* | 387 |
| EDIT: Spring App Status | Scope: Select the Application Type to the application you want to feed into. Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: No edits required here. The formula just checks the term is Spring and marks the application as submitted. IF(RIGHT([C8],1)="2","submitted","") | user-applications-status-* | 388 |
| EDIT: Summer App Term | Scope: Select the Application Type that these applications will feed into. Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built assumes you have your terms set up like Summer XXXX in your data sources. If your term name structure is different, you’ll update the yellow highlighted portion. IF(RIGHT([C8],1)="6",DB_MAP("term",CONCAT("Summer ",LEFT([C8],4)),"name","guid",""),"") Below are a few examples if your term naming structure is different: Summer XXXX Semester CONCAT("Summer ",LEFT([C8],4)," Semester") June XXXX CONCAT("June ",LEFT([C8],4)) XXXX Summer CONCAT(LEFT([C8],4)," Summer") | user-applications-term-* | 389 |
| EDIT: Summer App Major | Scope: Select the Application Type that these applications will feed into. Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built depends on how the majors from Apply Texas line up with your majors from Element451. IF(RIGHT([C8],1)="6",DB_MAP("major",<major column>,"<name or code on data source>","guid",""),"") Below are a few examples for how the DB_MAP portion may look depending on how the majors line up: Names in Apply Texas match Names in Element451: DB_MAP("major",[C14],"name","guid","") Codes in Apply Texas match Codes in Element451: DB_MAP("major",[C13],"code","guid","") Codes in Apply Texas are stored under Custom Codes in Element451: DB_MAP("major",[C13],"custom_1","guid","") | user-applications-major-* | 390 |
| EDIT: Summer App Second Major | Scope: Select the Application Type to the application you want to feed into. Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built depends on how the majors from Apply Texas line up with your majors from Element451. IF(RIGHT([C8],1)="6",DB_MAP("major",<major column>,"<name or code on data source>","guid",""),"") Below are a few examples for how the DB_MAP portion may look depending on how the majors line up: Names in Apply Texas match Names in Element451: DB_MAP("major",[C18],"name","guid","") Codes in Apply Texas match Codes in Element451: DB_MAP("major",[C17],"code","guid","") Codes in Apply Texas are stored under Custom Codes in Element451: DB_MAP("major",[C17],"custom_1","guid","") | user-applications-major-second-* | 391 |
| EDIT: Summer App Student Type | Scope: Select the Application Type to the application you want to feed into. Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: The formula for student type is going to vary. You may want everyone to come in as a First-Time Freshman, or you may want to use another field to determine the student type. If you are wanting every record to come in as the same student type, you’ll put your student type code inside quotes. In the example below, every record will come over as First-Time Freshman if the code in the instance is FTF. IF(RIGHT([C8],1)="6","FTF","") Ultimately, you want the output of your formula to be the codes or values of the student types you use in Element451. Below are a few examples of how to use a data source to map student types in: Using App Type in Apply Texas and it matches Column 1 in your Regular Data Source for Student Types in Element451: DS_MAP([C7],"example.data_source.1234","column_1","column_2","") Using an IF statement to determine student type: IF([C7]="Undergraduate (two - year)","FTF",IF([C7]="Dual-Credit","DC","")) | user-applications-student-type-* | 392 |
| EDIT: Summer App Start Date | Scope: Select the Application Type to the application you want to feed into. Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: No edits required here. The formula just checks the term is Summer and pulls the date from the column and reads it as a date. IF(RIGHT([C8],1)="6",DATE_READ([C43],"m/d/Y h:iA"),"") | user-applications-registered-at-* | 393 |
| EDIT: Summer App Submit Date | Scope: Select the Application Type to the application you want to feed into. Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: No edits required here. The formula just checks the term is Summer and pulls the date from the column and reads it as a date. IF(RIGHT([C8],1)="6",DATE_READ([C44],"m/d/Y h:iA"),"") | user-applications-submitted-time-* | 394 |
| EDIT: Summer App Status | Scope: Select the Application Type to the application you want to feed into. Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: No edits required here. The formula just checks the term is Summer and marks the application as submitted. IF(RIGHT([C8],1)="6","submitted","") | user-applications-status-* | 395 |
| EDIT: Fall App Term | Scope: Select the Application Type that these applications will feed into. Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built assumes you have your terms set up like Fall XXXX in your data sources. If your term name structure is different, you’ll update the yellow highlighted portion. IF(RIGHT([C8],1)="9",DB_MAP("term",CONCAT("Fall ",LEFT([C8],4)),"name","guid",""),"") Below are a few examples if your term naming structure is different: Fall XXXX Semester CONCAT("Fall ",LEFT([C8],4)," Semester") August XXXX CONCAT("August ",LEFT([C8],4)) XXXX Fall CONCAT(LEFT([C8],4)," Fall") | user-applications-term-* | 396 |
| EDIT: Fall App Major | Scope: Select the Application Type that these applications will feed into. Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built depends on how the majors from Apply Texas line up with your majors from Element451. IF(RIGHT([C8],1)="9",DB_MAP("major",<major column>,"<name or code on data source>","guid",""),"") Below are a few examples for how the DB_MAP portion may look depending on how the majors line up: Names in Apply Texas match Names in Element451: DB_MAP("major",[C14],"name","guid","") Codes in Apply Texas match Codes in Element451: DB_MAP("major",[C13],"code","guid","") Codes in Apply Texas are stored under Custom Codes in Element451: DB_MAP("major",[C13],"custom_1","guid","") | user-applications-major-* | 397 |
| EDIT: Fall App Second Major | Scope: Select the Application Type to the application you want to feed into. Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built depends on how the majors from Apply Texas line up with your majors from Element451. IF(RIGHT([C8],1)="9",DB_MAP("major",<major column>,"<name or code on data source>","guid",""),"") Below are a few examples for how the DB_MAP portion may look depending on how the majors line up: Names in Apply Texas match Names in Element451: DB_MAP("major",[C18],"name","guid","") Codes in Apply Texas match Codes in Element451: DB_MAP("major",[C17],"code","guid","") Codes in Apply Texas are stored under Custom Codes in Element451: DB_MAP("major",[C17],"custom_1","guid","") | user-applications-major-second-* | 398 |
| EDIT: Fall App Student Type | Scope: Select the Application Type to the application you want to feed into. Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: The formula for student type is going to vary. You may want everyone to come in as a First-Time Freshman, or you may want to use another field to determine the student type. If you are wanting every record to come in as the same student type, you’ll put your student type code inside quotes. In the example below, every record will come over as First-Time Freshman if the code in the instance is FTF. IF(RIGHT([C8],1)="9","FTF","") Ultimately, you want the output of your formula to be the codes or values of the student types you use in Element451. Below are a few examples of how to use a data source to map student types in: Using App Type in Apply Texas and it matches Column 1 in your Regular Data Source for Student Types in Element451: DS_MAP([C7],"example.data_source.1234","column_1","column_2","") Using an IF statement to determine student type: IF([C7]="Undergraduate (two - year)","FTF",IF([C7]="Dual-Credit","DC","")) | user-applications-student-type-* | 399 |
| EDIT: Fall App Start Date | Scope: Select the Application Type to the application you want to feed into. Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: No edits required here. The formula just checks the term is Fall and pulls the date from the column and reads it as a date. IF(RIGHT([C8],1)="9",DATE_READ([C43],"m/d/Y h:iA"),"") | user-applications-registered-at-* | 400 |
| EDIT: Fall App Submit Date | Scope: Select the Application Type to the application you want to feed into. Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: No edits required here. The formula just checks the term is Fall and pulls the date from the column and reads it as a date. IF(RIGHT([C8],1)="9",DATE_READ([C44],"m/d/Y h:iA"),"") | user-applications-submitted-time-* | 401 |
| EDIT: Fall App Status | Scope: Select the Application Type to the application you want to feed into. Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: No edits required here. The formula just checks the term is Fall and marks the application as submitted. IF(RIGHT([C8],1)="9","submitted","") | user-applications-status-* | 402 |
| EDIT: Spring App Start Milestone Date | Scope: Select the Milestone Type to Application Start Date. Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: No edits required here. The formula just checks the term is Spring and pulls the date from the column and reads it as a date. IF(RIGHT([C8],1)="2",DATE_READ([C43],"m/d/Y h:iA"),"") | user-milestones-date-* | 403 |
| EDIT: Spring App Start Milestone Major | Scope: Select the Milestone Type to Application Start Date. Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built depends on how the majors from Apply Texas line up with your majors from Element451. IF(RIGHT([C8],1)="2",DB_MAP("major",<major column>,"<name or code on data source>","guid",""),"") Below are a few examples for how the DB_MAP portion may look depending on how the majors line up: Names in Apply Texas match Names in Element451: DB_MAP("major",[C14],"name","guid","") Codes in Apply Texas match Codes in Element451: DB_MAP("major",[C13],"code","guid","") Codes in Apply Texas are stored under Custom Codes in Element451: DB_MAP("major",[C13],"custom_1","guid","") | user-milestones-major-* | 404 |
| EDIT: Spring App Start Milestone Term | Scope: Select the Milestone Type to Application Start Date. Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built assumes you have your terms set up like Spring XXXX in your data sources. If your term name structure is different, you’ll update the yellow highlighted portion. IF(RIGHT([C8],1)="2",DB_MAP("term",CONCAT("Spring ",LEFT([C8],4)),"name","guid",""),"") Below are a few examples if your term naming structure is different: Spring XXXX Semester CONCAT("Spring ",LEFT([C8],4)," Semester") January XXXX CONCAT("January ",LEFT([C8],4)) XXXX Spring CONCAT(LEFT([C8],4)," Spring") | user-milestones-term-* | 405 |
| EDIT: Spring App Start Milestone Student Type | Scope: Select the Milestone Type to Application Start Date. Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: The formula for student type is going to vary. You may want everyone to come in as a First-Time Freshman, or you may want to use another field to determine the student type. If you are wanting every record to come in as the same student type, you’ll put your student type code inside quotes. In the example below, every record will come over as First-Time Freshman if the code in the instance is FTF. IF(RIGHT([C8],1)="2","FTF","") Ultimately, you want the output of your formula to be the codes or values of the student types you use in Element451. Below are a few examples of how to use a data source to map student types in: Using App Type in Apply Texas and it matches Column 1 in your Regular Data Source for Student Types in Element451: DS_MAP([C7],"example.data_source.1234","column_1","column_2","") Using an IF statement to determine student type: IF([C7]="Undergraduate (two - year)","FTF",IF([C7]="Dual-Credit","DC","")) | user-milestones-student_type-* | 406 |
| EDIT: Spring App Start Milestone GUID | Scope: Select the Milestone Type to Application Start Date. Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: The formula will be the application GUID you are feeding the applicants into. You can find the application GUID by going into the application in your Element451 like you are about to edit it and pull from the url. IF(RIGHT([C8],1)="2","example.applications.12345","") | user-milestones-application-guid-* | 407 |
| EDIT: Summer App Start Milestone Date | Scope: Select the Milestone Type to Application Start Date. Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: No edits required here. The formula just checks the term is Summer and pulls the date from the column and reads it as a date. IF(RIGHT([C8],1)="6",DATE_READ([C43],"m/d/Y h:iA"),"") | user-milestones-date-* | 408 |
| EDIT: Summer App Start Milestone Major | Scope: Select the Milestone Type to Application Start Date. Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built depends on how the majors from Apply Texas line up with your majors from Element451. IF(RIGHT([C8],1)="6",DB_MAP("major",<major column>,"<name or code on data source>","guid",""),"") Below are a few examples for how the DB_MAP portion may look depending on how the majors line up: Names in Apply Texas match Names in Element451: DB_MAP("major",[C14],"name","guid","") Codes in Apply Texas match Codes in Element451: DB_MAP("major",[C13],"code","guid","") Codes in Apply Texas are stored under Custom Codes in Element451: DB_MAP("major",[C13],"custom_1","guid","") | user-milestones-major-* | 409 |
| EDIT: Summer App Start Milestone Term | Scope: Select the Milestone Type to Application Start Date. Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built assumes you have your terms set up like Summer XXXX in your data sources. If your term name structure is different, you’ll update the yellow highlighted portion. IF(RIGHT([C8],1)="6",DB_MAP("term",CONCAT("Summer ",LEFT([C8],4)),"name","guid",""),"") Below are a few examples if your term naming structure is different: Summer XXXX Semester CONCAT("Summer ",LEFT([C8],4)," Semester") June XXXX CONCAT("June ",LEFT([C8],4)) XXXX Summer CONCAT(LEFT([C8],4)," Summer") | user-milestones-term-* | 410 |
| EDIT: Summer App Start Milestone Student Type | Scope: Select the Milestone Type to Application Start Date. Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: The formula for student type is going to vary. You may want everyone to come in as a First-Time Freshman, or you may want to use another field to determine the student type. If you are wanting every record to come in as the same student type, you’ll put your student type code inside quotes. In the example below, every record will come over as First-Time Freshman if the code in the instance is FTF. IF(RIGHT([C8],1)="6","FTF","") Ultimately, you want the output of your formula to be the codes or values of the student types you use in Element451. Below are a few examples of how to use a data source to map student types in: Using App Type in Apply Texas and it matches Column 1 in your Regular Data Source for Student Types in Element451: DS_MAP([C7],"example.data_source.1234","column_1","column_2","") Using an IF statement to determine student type: IF([C7]="Undergraduate (two - year)","FTF",IF([C7]="Dual-Credit","DC","")) | user-milestones-student_type-* | 411 |
| EDIT: Summer App Start Milestone GUID | Scope: Select the Milestone Type to Application Start Date. Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: The formula will be the application GUID you are feeding the applicants into. You can find the application GUID by going into the application in your Element451 like you are about to edit it and pull from the url. IF(RIGHT([C8],1)="6","example.applications.12345","") | user-milestones-application-guid-* | 412 |
| EDIT: Fall App Start Milestone Date | Scope: Select the Milestone Type to Application Start Date. Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: No edits required here. The formula just checks the term is Fall and pulls the date from the column and reads it as a date. IF(RIGHT([C8],1)="9",DATE_READ([C43],"m/d/Y h:iA"),"") | user-milestones-date-* | 413 |
| EDIT: Fall App Start Milestone Major | Scope: Select the Milestone Type to Application Start Date. Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built depends on how the majors from Apply Texas line up with your majors from Element451. IF(RIGHT([C8],1)="9",DB_MAP("major",<major column>,"<name or code on data source>","guid",""),"") Below are a few examples for how the DB_MAP portion may look depending on how the majors line up: Names in Apply Texas match Names in Element451: DB_MAP("major",[C14],"name","guid","") Codes in Apply Texas match Codes in Element451: DB_MAP("major",[C13],"code","guid","") Codes in Apply Texas are stored under Custom Codes in Element451: DB_MAP("major",[C13],"custom_1","guid","") | user-milestones-major-* | 414 |
| EDIT: Fall App Start Milestone Term | Scope: Select the Milestone Type to Application Start Date. Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built assumes you have your terms set up like Fall XXXX in your data sources. If your term name structure is different, you’ll update the yellow highlighted portion. IF(RIGHT([C8],1)="9",DB_MAP("term",CONCAT("Fall ",LEFT([C8],4)),"name","guid",""),"") Below are a few examples if your term naming structure is different: Fall XXXX Semester CONCAT("Fall ",LEFT([C8],4)," Semester") August XXXX CONCAT("August ",LEFT([C8],4)) XXXX Fall CONCAT(LEFT([C8],4)," Fall") | user-milestones-term-* | 415 |
| EDIT: Fall App Start Milestone Student Type | Scope: Select the Milestone Type to Application Start Date. Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: The formula for student type is going to vary. You may want everyone to come in as a First-Time Freshman, or you may want to use another field to determine the student type. If you are wanting every record to come in as the same student type, you’ll put your student type code inside quotes. In the example below, every record will come over as First-Time Freshman if the code in the instance is FTF. IF(RIGHT([C8],1)="9","FTF","") Ultimately, you want the output of your formula to be the codes or values of the student types you use in Element451. Below are a few examples of how to use a data source to map student types in: Using App Type in Apply Texas and it matches Column 1 in your Regular Data Source for Student Types in Element451: DS_MAP([C7],"example.data_source.1234","column_1","column_2","") Using an IF statement to determine student type: IF([C7]="Undergraduate (two - year)","FTF",IF([C7]="Dual-Credit","DC","")) | user-milestones-student_type-* | 416 |
| EDIT: Fall App Start Milestone GUID | Scope: Select the Milestone Type to Application Start Date. Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: The formula will be the application GUID you are feeding the applicants into. You can find the application GUID by going into the application in your Element451 like you are about to edit it and pull from the url. IF(RIGHT([C8],1)="9","example.applications.12345","") | user-milestones-application-guid-* | 417 |
| EDIT: Spring App Submit Milestone Date | Scope: Select the Milestone Type to Application Submit Date. Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: No edits required here. The formula just checks the term is Spring and pulls the date from the column and reads it as a date. IF(RIGHT([C8],1)="2",DATE_READ([C44],"m/d/Y h:iA"),"") | user-milestones-date-* | 418 |
| EDIT: Spring App Submit Milestone Major | Scope: Select the Milestone Type to Application Submit Date. Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built depends on how the majors from Apply Texas line up with your majors from Element451. IF(RIGHT([C8],1)="2",DB_MAP("major",<major column>,"<name or code on data source>","guid",""),"") Below are a few examples for how the DB_MAP portion may look depending on how the majors line up: Names in Apply Texas match Names in Element451: DB_MAP("major",[C14],"name","guid","") Codes in Apply Texas match Codes in Element451: DB_MAP("major",[C13],"code","guid","") Codes in Apply Texas are stored under Custom Codes in Element451: DB_MAP("major",[C13],"custom_1","guid","") | user-milestones-major-* | 419 |
| EDIT: Spring App Submit Milestone Term | Scope: Select the Milestone Type to Application Submit Date. Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built assumes you have your terms set up like Spring XXXX in your data sources. If your term name structure is different, you’ll update the yellow highlighted portion. IF(RIGHT([C8],1)="2",DB_MAP("term",CONCAT("Spring ",LEFT([C8],4)),"name","guid",""),"") Below are a few examples if your term naming structure is different: Spring XXXX Semester CONCAT("Spring ",LEFT([C8],4)," Semester") January XXXX CONCAT("January ",LEFT([C8],4)) XXXX Spring CONCAT(LEFT([C8],4)," Spring") | user-milestones-term-* | 420 |
| EDIT: Spring App Submit Milestone Student Type | Scope: Select the Milestone Type to Application Submit Date. Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: The formula for student type is going to vary. You may want everyone to come in as a First-Time Freshman, or you may want to use another field to determine the student type. If you are wanting every record to come in as the same student type, you’ll put your student type code inside quotes. In the example below, every record will come over as First-Time Freshman if the code in the instance is FTF. IF(RIGHT([C8],1)="2","FTF","") Ultimately, you want the output of your formula to be the codes or values of the student types you use in Element451. Below are a few examples of how to use a data source to map student types in: Using App Type in Apply Texas and it matches Column 1 in your Regular Data Source for Student Types in Element451: DS_MAP([C7],"example.data_source.1234","column_1","column_2","") Using an IF statement to determine student type: IF([C7]="Undergraduate (two - year)","FTF",IF([C7]="Dual-Credit","DC","")) | user-milestones-student_type-* | 421 |
| EDIT: Spring App Submit Milestone GUID | Scope: Select the Milestone Type to Application Submit Date. Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: The formula will be the application GUID you are feeding the applicants into. You can find the application GUID by going into the application in your Element451 like you are about to edit it and pull from the url. IF(RIGHT([C8],1)="2","example.applications.12345","") | user-milestones-application-guid-* | 422 |
| EDIT: Summer App Submit Milestone Date | Scope: Select the Milestone Type to Application Submit Date. Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: No edits required here. The formula just checks the term is Summer and pulls the date from the column and reads it as a date. IF(RIGHT([C8],1)="6",DATE_READ([C44],"m/d/Y h:iA"),"") | user-milestones-date-* | 423 |
| EDIT: Summer App Submit Milestone Major | Scope: Select the Milestone Type to Application Submit Date. Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built depends on how the majors from Apply Texas line up with your majors from Element451. IF(RIGHT([C8],1)="6",DB_MAP("major",<major column>,"<name or code on data source>","guid",""),"") Below are a few examples for how the DB_MAP portion may look depending on how the majors line up: Names in Apply Texas match Names in Element451: DB_MAP("major",[C14],"name","guid","") Codes in Apply Texas match Codes in Element451: DB_MAP("major",[C13],"code","guid","") Codes in Apply Texas are stored under Custom Codes in Element451: DB_MAP("major",[C13],"custom_1","guid","") | user-milestones-major-* | 424 |
| EDIT: Summer App Submit Milestone Term | Scope: Select the Milestone Type to Application Submit Date. Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built assumes you have your terms set up like Summer XXXX in your data sources. If your term name structure is different, you’ll update the yellow highlighted portion. IF(RIGHT([C8],1)="6",DB_MAP("term",CONCAT("Summer ",LEFT([C8],4)),"name","guid",""),"") Below are a few examples if your term naming structure is different: Summer XXXX Semester CONCAT("Summer ",LEFT([C8],4)," Semester") June XXXX CONCAT("June ",LEFT([C8],4)) XXXX Summer CONCAT(LEFT([C8],4)," Summer") | user-milestones-term-* | 425 |
| EDIT: Summer App Submit Milestone Student Type | Scope: Select the Milestone Type to Application Submit Date. Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: The formula for student type is going to vary. You may want everyone to come in as a First-Time Freshman, or you may want to use another field to determine the student type. If you are wanting every record to come in as the same student type, you’ll put your student type code inside quotes. In the example below, every record will come over as First-Time Freshman if the code in the instance is FTF. IF(RIGHT([C8],1)="6","FTF","") Ultimately, you want the output of your formula to be the codes or values of the student types you use in Element451. Below are a few examples of how to use a data source to map student types in: Using App Type in Apply Texas and it matches Column 1 in your Regular Data Source for Student Types in Element451: DS_MAP([C7],"example.data_source.1234","column_1","column_2","") Using an IF statement to determine student type: IF([C7]="Undergraduate (two - year)","FTF",IF([C7]="Dual-Credit","DC","")) | user-milestones-student_type-* | 426 |
| EDIT: Summer App Submit Milestone GUID | Scope: Select the Milestone Type to Application Submit Date. Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: The formula will be the application GUID you are feeding the applicants into. You can find the application GUID by going into the application in your Element451 like you are about to edit it and pull from the url. IF(RIGHT([C8],1)="6","example.applications.12345","") | user-milestones-application-guid-* | 427 |
| EDIT: Fall App Submit Milestone Date | Scope: Select the Milestone Type to Application Submit Date. Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: No edits required here. The formula just checks the term is Fall and pulls the date from the column and reads it as a date. IF(RIGHT([C8],1)="9",DATE_READ([C44],"m/d/Y h:iA"),"") | user-milestones-date-* | 428 |
| EDIT: Fall App Submit Milestones Major | Scope: Select the Milestone Type to Application Submit Date. Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built depends on how the majors from Apply Texas line up with your majors from Element451. IF(RIGHT([C8],1)="9",DB_MAP("major",<major column>,"<name or code on data source>","guid",""),"") Below are a few examples for how the DB_MAP portion may look depending on how the majors line up: Names in Apply Texas match Names in Element451: DB_MAP("major",[C14],"name","guid","") Codes in Apply Texas match Codes in Element451: DB_MAP("major",[C13],"code","guid","") Codes in Apply Texas are stored under Custom Codes in Element451: DB_MAP("major",[C13],"custom_1","guid","") | user-milestones-major-* | 429 |
| EDIT: Fall App Submit Milestone Term | Scope: Select the Milestone Type to Application Submit Date. Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: How the formula is built assumes you have your terms set up like Fall XXXX in your data sources. If your term name structure is different, you’ll update the yellow highlighted portion. IF(RIGHT([C8],1)="9",DB_MAP("term",CONCAT("Fall ",LEFT([C8],4)),"name","guid",""),"") Below are a few examples if your term naming structure is different: Fall XXXX Semester CONCAT("Fall ",LEFT([C8],4)," Semester") August XXXX CONCAT("August ",LEFT([C8],4)) XXXX Fall CONCAT(LEFT([C8],4)," Fall") | user-milestones-term-* | 430 |
| EDIT: Fall App Submit Milestone Student Type | Scope: Select the Milestone Type to Application Submit Date. Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: The formula for student type is going to vary. You may want everyone to come in as a First-Time Freshman, or you may want to use another field to determine the student type. If you are wanting every record to come in as the same student type, you’ll put your student type code inside quotes. In the example below, every record will come over as First-Time Freshman if the code in the instance is FTF. IF(RIGHT([C8],1)="9","FTF","") Ultimately, you want the output of your formula to be the codes or values of the student types you use in Element451. Below are a few examples of how to use a data source to map student types in: Using App Type in Apply Texas and it matches Column 1 in your Regular Data Source for Student Types in Element451: DS_MAP([C7],"example.data_source.1234","column_1","column_2","") Using an IF statement to determine student type: IF([C7]="Undergraduate (two - year)","FTF",IF([C7]="Dual-Credit","DC","")) | user-milestones-student_type-* | 431 |
| EDIT: Fall App Submit Milestone GUID | Scope: Select the Milestone Type to Application Submit Date. Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up. Formula: The formula will be the application GUID you are feeding the applicants into. You can find the application GUID by going into the application in your Element451 like you are about to edit it and pull from the url. IF(RIGHT([C8],1)="9","example.applications.12345","") | user-milestones-application-guid-* | 432 |
| Labels | Here is where you can add any labels you want to the profiles. If you are wanting these applications moved to decisions, following the Move Application to Decisions instructions, we’ll want to add the label that triggers the rule in this formula. You can also add any other labels you use. For importing one label: "example.taxonomy.12345" For importing more labels: "example.taxonomy.12345,example.taxonomy.67890,example.taxonomy.11111" | user-labels-import | 433 |
| Source Code | If you want to add an ApplyTexas source to the records as they come in, make sure you create the source under Contacts>Categories>Source Codes. Copy the taxonomy code from there and paste inside quotes. "example.taxonomy.1234" | user-sources-source-code | 434 |
| Source Date | No further edits on this formula. I pulls the submit date for the source. DATE_READ([C44],"m/d/Y h:iA") | user-sources-source-code-date | 435 |
Was this page helpful?