APIv4 - Filter custom fields based on supplied values #23489
Merged
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
This allows targeted getfields for a particular entity or type of entity
|
(Standard links)
|
colemanw
added a commit
to colemanw/de.systopia.eck
that referenced
this pull request
May 18, 2022
This was fixed in civicrm/civicrm-core#23489
|
I could replicate this on r-run
|
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
Improves APIv4 metadata, allows targeted getfields for a particular entity or type of entity.
Before
Calling
getFieldswould return all custom fields even if not relevant for a given entity subtype.After
Custom fields are always filtered based on any relevant values provided.
Notes
Fixes the fixme added in #22827