Share
Report
262Hi, I would be using a generic example for privacy reasons.
So let's say we have the following entities in a clinical setting
- Contacts - Patients
- Patient medical records
- Therapist profile (bookable resource)
A therapist profile would include the Microsoft 365 user ID of the therapist, email, supervisors, and other details.
This therapist profile would then be assigned to a patient record as our patient setup does not reference the therapist's Microsoft 365 user ID directly.
There are now two issues
1. An employee leaves the organization
2. A new employee that has the same name
For 1. Since the patient record link to the therapist profile and not directly to the Microsoft 365 user ID, I believe it should not affect the patient record, although the therapist profile could be incomplete when the Microsoft 365 user ID gets deleted. Please correct me if I am wrong here.
For 2. This is where the problem begins.
Let's say a new staff joins the organization and has the same name as the previous staff. Let's say Tom_Hanks.
It seems that Dynamics will assume they are the same person and will link the new Microsoft 365 ID Tom_Hanks to the previous therapist profile.
This may not be what we want, because the new Tom Hanks belongs to a new department.
The previous Tom Hanks could be a speech therapist while the new one could be a physiotherapist.
What is the best approach to managing a new employee that shares a similar user ID as the previous one? Thank you in advance.
All responses (
Answers (
