Search Results

Upsert depends upon the value of External ID fields being unique. If you choose to not make External ID unique, you cannot leverage this feature. This means that you would need to leverage external lo …

You must not put the external ID field/value in the JSON; it is specified by the URL you're hitting. Simply remove that bit from your file and it should work. Here's an example using Accounts: PATCH …

It's true. Auto-number fields can be external IDs. I can think of at least one good reason. Salesforce.com might be the source of record without explicitly using salesforce.com ID values, which may be …

In short, no, there isn't a direct API to determine such limits. You shouldn't make any assumptions at all about the number of External ID fields that may be available. Even though the usual default …

The main problems are: limit of 25 External ID fields per object, indexes take a while to build (can cause "Org Lock" errors to additional changes until it processes, which may take hours), and duplic …

Generally speaking, no, there isn't a globally unique name system. However, if you take some due diligence, you can upsert most types of records via their Name: Group g = new Group(Name='Some Unique …

CampaignId is automatically indexed, as are all lookup fields. The problem is that your campaigns are too big. You'd have to be more selective, such as limiting the query to simply 50,000 rows (which …

You need to use SObject.putSobject instead of just SObject.put. The former is used to set reference fields, and is even explicitly mentioned as the preferred method of setting SObject values for Exter …

1) Is there a way to upsert by externalId autonumber field type? (without copying that field to new field with workflow). In fact, this is very likely something we will never be able to do. … You would necessarily need to write a trigger to implement this functionality. 2) Is there a way to store values in a Map from soql query that the key will be externalId - without go through on a list …

Basically, no. You need to know the record exists, or create it beforehand. Your best bet would be to upsert the parent records beforehand and/or perform a query to check, thus ensuring that the recor …

See Inside the Force.com Query Optimizer Webinar for details, but basically there are several paths that the system can take: filter first by sharing, filter first by index, or full table scan (when s …

To specify the parent by External ID, you have to create an sObject: public static void createRevenueSchedule(List<Revenue_Pipeline_Schedule__c> scope) { List<Revenue_Schedules__c> revSchedul …

You can't do this with the endpoint you're trying to use; the method only allows updating a single record at a time, and uses the following syntax: (PATCH) /services/data/41.0/sobjects/Contact/Custom …

Unfortunately, the polymorphic nature of ParentId renders External ID values useless (it only works on concrete relationships). Instead, you'll have to match the External ID values to the appropriate …

You're trying to map by an autonumber field, which is read-only, so the mapping logic doesn't support what you're trying to do. This would work if you were working with a mappable field, such as custo …