dev/core#123 Retrieve existing participant custom fields for import #12159
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
|
I checked & participant import does not support importing custom fields for entities other than participant so I agree this is the same scenario as the link above & hence using the same fix makes sense |
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.
Overview
The date fields are not converted from the import date format to the default date format and thus end up beeing imported with a date value of 0.
See https://lab.civicrm.org/dev/core/issues/123 for details.
Before
Notice errors present.
After
Notice errors not present.
Technical Details
As per comment from @eileenmcnaughton #9072 (comment) there is no need for the custom contact fields, so I've replaced it instead of using an array union.