regression: Do not throw an error when a required custom field is missing on visitor to contact migration #34071
+10
−2
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.
Proposed changes (including videos or screenshots)
Introduced here: #32727
Issue(s)
Steps to test or reproduce
Further comments
On visitor to contact migration, we shouldn't throw errors in any of these cases:
#34030 has only partially fixed this issue (the second item has been addressed, but not the first one). In order to not throw errors on visitor to contact migration, we should skip the whole repeated validation process so that missing required fields do not generate an error.
SCI-179