Department & Location fields - best way to manage

[fishhead64]

Can someone point me to a doc that explains how Department and Location fields are populated and used in MiCollab and MiVB, or offer a quick explanation?

We see it in several places:
MiCollab - User Tab, as a drop down selection
MiVB - User Profile Tab as a free typed entry
MiVB - Telephone Directory
MiVB - Departments & Locations as a table we believe gets populated when MiVB fields are populated.

We want to clean up the database; fill in the blanks, correct spelling, eliminate duplicates, (ex. Human Resources, HR, Hum.Res, etc.).

Also since we sync new employees using AD, Mitel IO, Azure, can we push that data from AD?

[lundah]

They're customer defined fields, so you can use them however you want, really. In my org, we use Department for the department the extension is assigned/billed to, and the Location field for the building the phone/user is in across our campus and remote buildings. I've also seen it used to specify the exact location of the phone, though if you are using an E911 integration the CESID Comment field is a better place to store that.

If you're IDS integrated, check the Attribute Mappings to see what AD fields push into MiCollab/MiVB. I believe the default mappings are Department = department, and Location = physicalDeliveryOfficeName. Once you have AD cleaned up, running a sync and then saving any update records in the BUP Detained Queue should take care of your corrections.