Fix duplicate detection issue by applying DML options with all-or-nothing behavior #1502
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.
Critical Changes
DUPLICATES_DETECTED
errors were incorrectly thrown during DML operations, even when duplicates were allowed.Changes
dml.OptAllOrNone = allOrNothing
to ensure proper handling of DML operations based on theallOrNothing
flag.DMLOptions
to allow saving records with duplicates whenallowSave
is set.Issues Closed