jsforce / jsforce/jsforce

Upsert Does Not Set ExternalId

Open
#1,246 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
1.5k
Forks
551
Avg merge
9h 2m
Merged PRs (30d)
3

Description

When calling upsert(record, extId_Field), the extIdField is not set.

Below is current example. Creating a new record of a custom object, with External ID field EXTID__c.

The record gets created, but the external id field (EXTID__c) is not set.

const newProject = await sfconn.sobject("Project__c").upsert({
            Name: "EXAMPLE",
            RecordTypeId: recordTypeId,
            Account__c: "0016A00000EXAMPLE",
            Lead__c: "0056A00000EXAMPLE",
            EXTID__c: 123456
        }, "EXTID__c")

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the SObject.upsert(record, extId_Field) entry point and reproduce the custom-object example with EXTID__c. Trace the create path to determine why the external ID is not retained, then verify that a newly created record contains the supplied value and that existing upsert behavior still works.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
43/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.