External Id should not be mandatory on upsert#589
Merged
stomita merged 1 commit intojsforce:masterfrom Jan 18, 2017
b-n:master
Merged
External Id should not be mandatory on upsert#589stomita merged 1 commit intojsforce:masterfrom b-n:master
stomita merged 1 commit intojsforce:masterfrom
b-n:master
Conversation
stomita
approved these changes
Jan 18, 2017
EsrefDurna
pushed a commit
to EsrefDurna/jsforce
that referenced
this pull request
Nov 12, 2025
External Id should not be mandatory on upsert
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.
Apex/Bulk API can use the Id field as an external Id. In those cases, you can't provide a value, and thus it fails with JSForce due to this error condition. Also, (although it's not a good idea in my opinion), you could have a blank value as an External Id.