Export extract sets control which sections are updated in your SIS based on changes in 25Live.
Making an Export Extract Set
Technically, export and import extract sets are completely separate. But for convenience and consistency, it's best to have them mirror each other. If they are the same, then you always know which classes are affected.
The easiest way to create an export extract set is to find the corresponding import extract set and duplicate its criteria. You can read about import extract set criteria at Tips for Import Extract Sets.
Status - Active or Inactive?
An extract set won't send any changes to your SIS unless it's active. If it's inactive, then LYNX will keep track of changes in the background and wait for you to turn it on.
You can create an export extract set at any time but usually you'll wait to make it active. LYNX picks up changes very quickly, so as soon as you make an assignment in 25Live it will appear in the SIS. It's a good practice to keep the extract set inactive while you're placing classes for a term, because you'll probably be making a lot of adjustments and changes over a short period of time. When the dust settles, make the extract set active and bring all your changes to the SIS at once.
What Gets Updated?
25Live allows you to edit many data fields, but only a few are relevant for sending data back to the SIS. This is what LYNX will export:
- If you assign a new location in 25Live, LYNX will assign it in the SIS
- If you remove a location in 25Live, LYNX will remove it in the SIS (this can be disabled)
- If you make changes to the meeting pattern dates and times, LYNX will make these updates in the SIS (may not be available for some SIS types)
LYNX will not update changes to other fields, such as a section's name or head count. If you make changes to these fields in 25Live, they will be overwritten with current values from the SIS the next time LYNX updates the section.
Common Export Errors
Since LYNX mostly just exports location information back to the SIS, the errors you may encounter revolve around those. Avoid problems by:
- Make sure that locations have the same name in the SIS and 25Live. Check your Translation Tables if you encounter issues around names.
- Assign only one location to each meeting pattern. LYNX will only send one back to your SIS.
- Assign the location to all dates in a meeting pattern. If you have dates when a section doesn't meet, add date exceptions to the import extract set.
See Import and Export Messages in LYNX for more details.