Fixed Employee Number no longer importing [sc-23497] #13318
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request has been linked to Shortcut Story #23497: Employee ID no longer importing. |
PR Summary
|
uberbrady
approved these changes
Jul 17, 2023
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The field mapping in the User Importer was using an incorrect field name for Employee Number ´employee_number´ instead of ´employee_num´. I was thinking if we made this change to make the field name clearer or more easily readable? But I change it to ´employee_num´ anyways because I don't think it was hard to understand that way either.
Fixes [sc-23497]
Type of change
How Has This Been Tested?
Test Configuration: