REST2: On record create load cf using record context#323
Open
elacour wants to merge 2 commits intobestpractical:stablefrom
Open
REST2: On record create load cf using record context#323elacour wants to merge 2 commits intobestpractical:stablefrom
elacour wants to merge 2 commits intobestpractical:stablefrom
Conversation
added 2 commits
March 31, 2022 15:28
Using object context is mandatory when there is more than one customfield using the same name, applied to different queues/catalogs/classes.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Using object context is mandatory when there is more than one
customfield using the same name, applied to different
queues/catalogs/classes. Else the wrong CF is loaded and as it does not applies, the submitted value is silently dropped.