CRM-18959 #8566
Closed
CRM-18959 #8566
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
|
You copied code to a new function but ended up dropping references to issue CRM-18708 in the comments. I'm guessing CRM-18708 fixed the issue with importing multi-value fields but now things are failing if the imported field requires formatting. Is this the case? Just want to be clear about it before I test. Thanks |
|
Commented to soon. Just saw PR-8556 which explains the issue a bit better. |
|
Hello @darrick Sorry for late response, I was out for weekend. Many Thanks :) |
|
Please check #8662 - proposed replacement PR |
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.
Created a function
getCustomFieldsto fetch all custom fields related to Contact Types and their subtypes