 |
You can map data into the HIGH_SCHOOL, LAST_ORG_ATTEND, and
GRAD_YR_LAST_ORG columns on the CANDIDATE table.
However, you should be very cautious about using these mapping columns if you are also mapping data to the columns of the ORG_TRACKING mapping table. There is a tie in theJ1 code between the data stored in the CANDIDATE table and the AD_ORG_TRACKING table in the database. For example, if a change is made in one window (the Candidate tab of the Maintain Candidacy window) for the last high school or the last organization, then the corresponding columns in the other window (the Organizations tab of the Maintain Candidacy window) are updated to ensure that the two tables stay in sync. Additionally, the Graduation Year column on the Candidate tab of the Maintain Candidacy window may be updated from the submitted organization data depending upon the value of the Candidate Grad Year configuration (set through the Configure Function window). Therefore, if data from a form is mapped to both sets of mapping columns, it is possible that the data may become out of sync or that one value may overwrite the other. Jenzabar recommends that you consistently use the mapping columns for one of the tables rather than using both mapping tables in the same form. |