ARTICLE: Synergetic Sync - Exclusion List

ARTICLE: Synergetic Sync - Exclusion List

Sometimes when your school's Synergetic database is syncing to REACH each day you may need to exclude some contacts in REACH that you do not want updated by the Synergetic sync. 

Examples of this may be where a relationship for a Guardian in REACH is not supported by the data stored in REACH or when you have casual or temporary boarders who are not identified as boarders in Synergetic.

Adding an Exclusion List to the Synergetic-to-REACH sync script can ensure that the data stored in REACH for these contacts can be managed manually in REACH and not automatically updated with each Synergetic sync process.

Updating your sync script

To add a student to the exclusion list (this specifically excludes a student or parent from being deleted), open the Perl script file in a text editor and jump down to the bottom.

There should be a line resembling:
exclusionList => '',                 # [] of PK's that you wish to NOT be deleted if not

You will want to add into the single quotes an array with any Synergetic ID's you'd like to be excluded.
For this case, the line should end up looking like:
exclusionList => '["55190"]',                 # [] of PK's that you wish to NOT be deleted if not

Come future students or parents that may need to be added to this list of exclusions, you simply comma separate the IDs like so:
exclusionList => '["52190", "ANOTHER ID", "AND ANOTHER ID"]',                 # [] of PK's that you wish to NOT be deleted if not

Depending on the version of the script, the comment on the right (the part after a "#") may differ or not exist, don't worry about that as it has no impact on how the script operates.

    • Related Articles

    • ARTICLE: Synergetic Integration

      Synergetic (AUS) Synergetic API Setup Instructions: In order to retrieve and sync data between your Synergetic Student Information System (SIS) and Reach, we need to establish an ODBC connection to your SIS, execute a pre-set SQL statement, prepare ...

    • ARTICLE: Magnus Health Integration

      Magnus Health (North America) The integration with Reach/Magnus Health provides a lookup of a student's allergies/conditions as logged in Magnus, as well as their Emergency Contacts. This information is not stored on Reach's servers but rather is ...

    • ARTICLE: FACTS Integration Setup

      FACTS API Setup Instructions The integration between Reach and FACTS allows for the automatic population and updating of user data within Reach. Scheduled to run nightly, this sync ensures that any changes to demographic information in FACTS are ...

    • ARTICLE: iSAMS Direct Integration setup

      iSAMS iSAMS direct integration Many thanks for selecting Reach, one of the first tasks that we need to perform as part of the initial set up is the integration with your iSAMS Management Information System. Integration with iSAMS will provide a safe, ...

    • ARTICLE: List Designer

      The List Designer is part of the larger 'Lists Manager' module, which allows schools to create an unlimited number of lists, which can be used to collect data from your system users. The List Designer is where you design and configure lists. GO TO: ...