The internal ID prevents duplication of data in th...
# general
j
The internal ID prevents duplication of data in the database, which is great. The problem is duplication of data for the user. If an admin is entering a new Employee record and tries to select a Supervisor, we run into one of the problems above. There are two use cases: 1) When using the employee's name as the Employee ID, if there are duplicate names in the organization, there is no way to tell which one you're selecting in the Supervisor dropdown. Both would just be called "Mike W. Smith", even though one is a supervisor and one is not. 2) When using a unique number for the Employee ID, the dropdown menu for Supervisor concatenates the Employee ID field and the Employee Name field - which would be great if it still sorted alphabetically by name. But it does not. It sorts numerically by the Employee ID field, essentially making the dropdown useless because you have to search through hundreds of names to find the correct one.