TMDSAS Transposed Numbers
- edgar
Analytics
If there is a problem with the TMDSAS and TMDSAS Supplemental Application both being submitted but having discrepancies, there are different cases that could be happening:
1) Transposed TMDSAS Applicant Numbers
When an applicant miss types their TMDSAS Applicant number, there will be a mismatch between the Applications List (https://apps.cvm.tamu.edu/Admissions/GetApplicationsForTMDSAS/List) and Supp App List (https://apps.cvm.tamu.edu/Admissions/SupplementalApplication/List). This will also have created a separate TMDSAS Applicant which could be causing problems verifying the User Account for the application. The correct process is to correct this by transferring everything to the correct applicant record with the correct TMDSAS Number. A sample of the database workflow of changes would be something like this:
-- Template
--#region Parameters
DECLARE @tmdsasCorrect INT;
SET @tmdsasCorrect = 0000;
DECLARE @tmdsasWrong INT;
SET @tmdsasWrong = 0000;
DECLARE @yearToCheck INT;
SET @yearToCheck = 0000;
--#endregion Parameters
--#region Variables
DECLARE @correctApplicantId INT;
DECLARE @wrongApplicantId INT;
DECLARE @suppAppId INT;
DECLARE @applicationId int;
--#endregion Variables
--#region Set Variables
SELECT @correctApplicantId = id
FROM dbo.Ads_Applicant t
WHERE t.TmdsasUserId IN (@tmdsasCorrect)
SELECT @wrongApplicantId = id
FROM dbo.Ads_Applicant t
WHERE t.TmdsasUserId IN (@tmdsasWrong)
SELECT @suppAppId = id
FROM dbo.Ads_SupplementalApplication t
WHERE t.ApplicantId IN (@tmdsasWrong)
AND t.[Year] = @yearToCheck
SELECT @applicationId = id
FROM dbo.Ads_Application t
WHERE t.ApplicantId IN (@correctApplicantId)
AND t.EntryYear = @yearToCheck
--#endregion Set Variables
--#region Updates
-- -- Supp App -----------
Update dbo.Ads_SupplementalApplication set ApplicantId = @correctApplicantId where id = @suppAppId
-- -- Application ---------
update dbo.Ads_Application set SupplementalApplicationId = @suppAppId where id = @applicationId
-- -- Applicant ---------
update dbo.Ads_Applicant set UserId = t.UserId, VerificationEamil = t.VerificationEamil, IsVerified = t.IsVerified
FROM dbo.Ads_Applicant t
WHERE t.Id = @wrongApplicantId
and Id = @correctApplicantId
update dbo.Ads_Applicant set UserId = null, VerificationEamil = '', IsVerified = 0 where id = @wrongApplicantId
--#endregion Updates
2) Multiple Applicants same TMDSAS Applicant Number
Another common issue comes when there are multiple TMDSAS Applicant records with the same TMDSAS number. This can cause the importer to match the application to a different applicant record than the Supplemental App. To correct this the process is similar but instead of picking the applicant record based on the correct TMDSAS number, it must be picked based on the most meaningful applicant record. This can be based on the one that was linked to the imported application or the verified user. The important thing is to pick one and merge the applicant accounts.