Identifier mapping: matching staff and locations

Map it once, then it's automated

Jack

Last Update 10 dagen geleden

An identifier is the name or code your other system uses for a staff member or a location. Your software might call a technician "J. Smith" or store an identifier as "JS123". Praiseworthy might hold that person as "John Smith". Identifier mapping is how you tell Praiseworthy the two are the same person.


NOTE: Integrations automatically create the staff for you if there is a first name for your staff in integrations. Learn why some records need mapping.


The need shows up on import. Most records match automatically because the identifiers already line up. Some records do not. Praiseworthy stages the unmatched identifier instead of guessing. A wrong guess would attribute a review to the wrong person, so the app waits for you.


You resolve a staged identifier in two ways. You map it to an existing record when the person or location already exists under a different identifier. You create a new record when the person or location is genuinely new. Either choice clears the staged identifier. You can delete staged identifiers at any time.


Praiseworthy remembers the mapping. The same identifier never gets staged twice. Future imports carrying "J. Smith" now flow straight through to John Smith automatically. You map once, and the app handles it from then on.

Was this article helpful?

0 out of 0 liked this article