Add option to allow null values in non-null custom fields in sObjects#246
Merged
Add option to allow null values in non-null custom fields in sObjects#246
Conversation
vanathi-g
force-pushed
the
null-in-non-null-fix
branch
from
2d8fab1 to
c49a63a
Compare
vanathi-g
force-pushed
the
null-in-non-null-fix
branch
2 times, most recently
from
c49a63a to
e8bfa13
Compare
vanathi-g
added a commit
that referenced
this pull request
May 16, 2024
[Cherry-Pick #246] Add option to allow null values in non-null custom fields in sObjects
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
2 participants
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.
Changes
Since custom sObject fields that are marked as non-nullable can sometimes have null values, a new option is provided to allow these null values by marking the corresponding CDAP schema field as nullable.