Staff Import using Omatic

Bailey Adams

Hello all!,


My team and I are trying to figure out how to use ImportOmatic to get all of our staff into Raiser's Edge monthly. We are hoping to do the following:


New hires: add relationship to branch they work for, fill in the information with their job, supervisor, etc, add constituency code "Staff - Full Time - Branch Name" (already in table)

Branch changes: break link with old branch, update relationship with new branch, add end date to old constituency code, add new constituency code

Position changes: Break link with old branch, add new relationship with same branch and fill in new position and supervisor information (we want to keep the old info for historical data)

Terminations: Break link with branch relationship, add end date to constituency code, move code to a place not in the primary position


New hires seem to be the easiest for us, and we match our spreadsheet with the Alias where we house the staff ID numbers from HR. Trying to figure out how to break links with relationships in ImportOmatic and add end dates to one specific constituency code rather than all of them on one person's record. Thoughts?

Alan French

Bailey Adams:

Trying to figure out how to break links with relationships in ImportOmatic and add end dates to one specific constituency code rather than all of them on one person's record. Thoughts?

Regarding the constituent codes, there is a tick box in configuration for "If imported constituent code already exists..." which has an option of "update existing". You could include their old code in one column and put the new end date in another column, then when you're mapping the fields in configuration you'll just need to tie the two together by setting the value type of the date field to be the field that contains the code itself, e.g. if your file has the staff code in column B and the end date in column C, set column C's value type equal to B. Happy to provide some screenshots if that's come across as complete gibberish!

Bailey Adams

Alan French:

Bailey Adams:

Trying to figure out how to break links with relationships in ImportOmatic and add end dates to one specific constituency code rather than all of them on one person's record. Thoughts?

Regarding the constituent codes, there is a tick box in configuration for "If imported constituent code already exists..." which has an option of "update existing". You could include their old code in one column and put the new end date in another column, then when you're mapping the fields in configuration you'll just need to tie the two together by setting the value type of the date field to be the field that contains the code itself, e.g. if your file has the staff code in column B and the end date in column C, set column C's value type equal to B. Happy to provide some screenshots if that's come across as complete gibberish!

 

Just so I know we're on the same page, will that tick box still apply when I use ImportOmatic rather than the RE Import system? If you can provide screenshots, that would be great. I think our ideal goal would be to not have to change the spreadsheet one bit, and just organize the fields to give us what we're looking for.

Alan French

So the "tick box" that I mentioned is actually a drop-down... sorry for confusing the issue. I've attached a screenshot of an example profile I've set up, and the second screenshot is of the setting that will determine how IOM treats incoming codes that already exist on the record. Hope that helps!