Setting Up or Moving to a Database View for the User Sync

Usually what you want to do is look at the fields you are currently pulling in with the AD sync and ensure you are at least grabbing those with your database VIEW (excluding ActiveDirectoryobjectGuid).

Please make sure what you are pulling in now for Office Location doesn't change in your database view (same data, different source e.g. if you are using "Washington, D.C." now in AD, make sure it's an exact match in your database view and not "Washington DC" or some variant. This is because the Calendar is based off of these locations and what you try to sync for a User must match what is already in our system for Office.)

If you are starting from scratch review the fields that are important or useful to UniversitySite.

IMPORTANT: The following two fields cannot be blank and must be unique in your data source:

• Email address
• Network Alias

Required Fields

First Name         nvarchar (50)

Last Name         nvarchar (50)

Email Address   nvarchar (100)

Network Alias    nvarchar (100)         [This is their windows login ID]

Office (city)        nvarchar (100)         [The city where their office is]

Disabled                (bit, not null OR ActiveDirectory)    [0 for Active and 1 for Disabled]

Additional Desirable Fields

Job Title            nvarchar (100)         [eg, attorney vs staff]

Job Class          nvarchar (400)

Hire Date          DATETIME = null  

Profile Pic URL nvarchar (500) 

Manager           nvarchar (100)         [employee's manager's network alias/windows login ID\

Other Fields

Department     nvarchar(100)

Section              nvarchar(100)

External ID        nvarchar(50)           [unique identifier, often an internal Employee number for your user sync;]

Assistants          nvarchar(MAX)      [windows login ID of people who can assist/proxy on behalf of this person in LearningSite]

Custom Fields

In addition to these fields, you can sync user profile data into any of our 10 custom fields (nvarchar (400).

The fields marked in red below are a good starting point. You might also want to grab some additional data using one of our 10 custom fields.

Important Note:

Include disabled User Accounts in your database view for at least 1 sync so that your license count of Active users is updated correctly.

It is important that the Disabled field is mapped to a field in the data source that either contains a 1, T, or True for disabled (inactive) or a 0, F, or False for NOT disabled (active).

You will want to select some sort of guide for Unique Identifier field (please don't use network alias or email because then neither of those can be updated by the sync).

The general order for filling this out is as follows: (3 is Unique Identifier field:).

Tips For Success

• When setting up your DB connection (4-5 above) be sure to check the box to allow saving password.
• Also, for the DB select field (6) , it's recommended that you use TEXT query and delete the placeholder text and replace it with "Select * from [your view]" where you replace the [ ] with your view name. This way any adjustments to the view can be managed in SQL without updating this tool.
• It's usually a good idea to run the sync once manually (don't run the old AD sync along with this sync) from the Main tab of the tool after you save your existing settings and let your UniversitySite application lead spot check some of your users in UniversitySite to see how things look. If you see issues, don't worry, just update the User Sync as needed and run it again. If necessary, re-run your original AD sync.
• Once everything in your new SQL sync is working as desired, be sure you disable the existing AD sync and ONLY use the new SQL sync. Do not try to run both together!