Remove end date as part of appointment unique key #202
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
Why these changes are being introduced: An employee appointment's end date was used as part of its enduring unique key in Quickbase, but this was flawed. When an appointment ended, the end date was changed from 2999-12-31 to the actual end date, changing the unique key, and effectively leaving an extra row in Quickbase. How this addresses that need: Removing the end date as part of the employee appointment key is sufficient to make them enduringly unique. Side effects of this change: * This required dropping and recreating the Employee Appointments table via a manual run, but otherwise no changes. Relevant ticket(s): * None
jonavellecuerdo
approved these changes
Jan 6, 2025
ehanson8
approved these changes
Jan 6, 2025
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.
Purpose and background context
An
Employee Appointmentend date was used as part of its enduring unique key in Quickbase, but this was flawed. When an appointment ended, the end date was changed from2999-12-31to the actual end date, changing the unique key, and effectively leaving an extra row in Quickbase.By removing the end date as part of the employee appointment key, we get an enduringly unique key that can be used for updates to pre-existing rows (e.g. the end date changes).
Includes new or updated dependencies?
NO
Changes expectations for external applications?
NO
What are the relevant tickets?
Developer
Code Reviewer(s)