Bulk API Developer's Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Valid XML Records

A batch request in an XML file contains records for one object type. Each batch uses the following format with each sObject tag representing a record:

1<?xml version="1.0" encoding="UTF-8"?>
2<sObjects xmlns="http://www.force.com/2009/06/asyncapi/dataload">
3   <sObject>
4      <field_name>field_value</field_name>
5      ...
6   </sObject>
7   <sObject>
8      <field_name>field_value</field_name>
9      ...
10   </sObject>
11</sObjects>

You must include the type field for a polymorphic field and exclude it for non-polymorphic fields in any batch. The batch fails if you do otherwise. A polymorphic field can refer to more than one type of object as a parent. For example, either a contact or a lead can be the parent of a task. In other words, the WhoId field of a task can contain the ID of either a contact or a lead.

Note

Note the following when generating records in XML files:

  • Field values aren't trimmed. White space characters at the beginning or end of a field value are included in the saved value. For example, John Smith is saved with the leading and trailing space.
  • Fields that aren't defined in the XML for a record are ignored when you update records. To set a field value to null, set the xsi:nil value for the field to true. For example, <description xsi:nil="true"/> sets the description field to null.
  • Fields with a double data type can include fractional values. Values can be stored in scientific notation if the number is large enough (or, for negative numbers, small enough), as indicated by the W3C XML Schema Part 2: Datatypes Second Edition specification.