Logic for Creating and Skipping Records During Import

The import framework includes a methodology in which an institution can determine whether instances of the following records can be imported into Anthology Reach:

Address
Application Registration
Area of Interest
Contact
Experience
Previous Education
Test Score
Extra Curricular Participant

This methodology enables institutions to customize the import framework by defining record creation and skip logic using integration mapping records.

The following table describes integration mapping that is required for creating/skipping instances of the above records:

Field	Description
Template Type	Can be set to an import name.
Internal Field Name	Set to isValidRecord.
Parameters	Includes comma-separated external field names of integration mapping records which will evaluate to a Boolean value. These conditions will be considered before creating a record of the specified test type. The record is created when the condition evaluates to TRUE. Record creation is skipped when the condition evaluates to FALSE.
Data Transformation Type	LOGICALAND
Record Type	The name of the entity. For example, the value in this field can be Contact.TestScore.6.

Example 1

The following integration mapping records enable an institution to skip record creation of entities if values are not specified in the source file.

For instance, an institution wants to skip creation of one or more of the six types of SAT test score records. To enable this behavior, the framework of the following integration mapping records is available out-of-the-box:

The parent integration mapping record:

Field	Description
Template Type	Can be set to an import template name.
Parameters	Includes comma separated external field names in curly braces which are imported for creating or updating a record. Example {ADMIN6_SAT_DATE}, {ADMIN6_SAT_TOTAL}, {ADMIN6_SAT_EBRW}, {ADMIN6_SAT_MATH_SECTION}, {ADMIN6_SAT_ESSAY_READING}, { ADMIN6_SAT_ESSAY_ANALYSIS}, {ADMIN6_SAT_ESSAY_WRITING} The output of the integration mapping record will be as follows: True – when at least one of the specified fields has a value. False –when none of the specified fields has a value.
Data Transformation Type	HASANYVALUE Values from multiple fields that are specified as comma-separated values in the Parameters field are considered. If any of the fields is not blank, the SAT record will be created.
External Field Name	For example ExternalField-HasAnyValue
Name	An appropriate value.

For the above example the Integration Mapping record to be considered to perform or skip creation of the entity record will be as follows:

Field	Description
Template Type	The same template name that is set in the above integration mapping record.
Internal Field Name	Set to isValidRecord.
Parameters	The value of the External field Name in the above integration mapping record. {ExternalField-HasAnyValue}
Data Transformation Type	LOGICALAND
External Field Name	An appropriate value.
Name	An appropriate value.

Such a framework enables the import of records if values are specified in source files. Import of specific records will be skipped if all source fields are blank.