-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix standardId issues with phones field migration #7294
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Summary
This pull request addresses standardId issues with the phones field migration, focusing on aligning the 'phones' field ID with the standard format used across the application.
- Updated 'phones' field standardId in
PERSON_STANDARD_FIELD_IDS
to '20202020-3c51-43fa-8b6e-af39e29368ab' - Enhanced migration command in
0-30-migrate-phone-fields-to-phones.command.ts
to handle standard and custom phone fields - Implemented data copying from deprecated phone fields to new phones fields
- Added error handling and rollback mechanisms for the migration process
- Updated view handling to reflect changes in phone field types
2 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings
await this.metadataDataSource.query( | ||
`UPDATE "metadata"."fieldMetadata" SET "standardId" = $1 where "id"=$2`, | ||
[PERSON_STANDARD_FIELD_IDS.phones, standardPersonPhoneField.id], | ||
); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
logic: standardPersonPhoneField.id is used instead of standardPersonPhonesField.id
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-authored-by: Weiko <[email protected]>
No description provided.