100% found this document useful (2 votes)

2K views

Metadata API Developer's Guide

Salesforce.com and the "no software" logo are registered trademarks. "Success on demand" and "the Business Web" are trademarks of salesforce.com, inc. All other trademarks mentioned in this document are the properties of their respective owners.

Uploaded by

ramkinavy

Available Formats

Download as PDF, TXT or read online on Scribd

100% found this document useful (2 votes)

2K views

Metadata API Developer's Guide

Uploaded by

ramkinavy

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 177

Version 15.

0: Salesforce Spring '09

Force.com Metadata API Developer's Guide

© Copyright 2000-2009 salesforce.com, inc. All rights reserved. Salesforce.com and the “no software” logo are registered trademarks, and
AppExchange, “Success On Demand,” and “The Business Web” are trademarks of salesforce.com, inc. All other trademarks mentioned in
this document are the properties of their respective owners.
Table of Contents

Table of Contents

Chapter 1: Understanding the Metadata API................................................................................3

Supported Salesforce Editions.......................................................................................................................................3
Development Platforms.................................................................................................................................................4
Standards Compliance...................................................................................................................................................4
Metadata API Support Policy.......................................................................................................................................4
What’s New in Version 15.0..........................................................................................................................................5
Related Resources .........................................................................................................................................................5

Chapter 2: Quick Start................................................................................................................6

Prerequisites...................................................................................................................................................................6
Step 1: Obtain a Salesforce Developer Edition Account...............................................................................................6
Step 2: Generate or Obtain the Web Service WSDLs..................................................................................................7
Step 3: Import the WSDL Files Into Your Development Platform..............................................................................7
Step 4: Walk Through the Sample Code.......................................................................................................................8

Chapter 3: Error Handling.........................................................................................................22

Error Handling for Session Expiration .......................................................................................................................22

Chapter 4: CRUD-Based Metadata Development.......................................................................23

checkStatus()...............................................................................................................................................................23
create().........................................................................................................................................................................24
AsyncResult.....................................................................................................................................................25
delete().........................................................................................................................................................................26
AsyncResult.....................................................................................................................................................27
update().......................................................................................................................................................................28
AsyncResult.....................................................................................................................................................30

Chapter 5: Declarative Metadata Development..........................................................................32

Working with the Zip File..........................................................................................................................................32
deploy()........................................................................................................................................................................36
checkDeployStatus()........................................................................................................................................43
DeployResult...................................................................................................................................................44
retrieve()......................................................................................................................................................................48
checkRetrieveStatus()......................................................................................................................................54
RetrieveRequest...............................................................................................................................................55
RetrieveResult..................................................................................................................................................57
describeMetadata()......................................................................................................................................................58
DescribeMetadataResult..................................................................................................................................59
listMetadata()..............................................................................................................................................................60
ListMetadataQuery.........................................................................................................................................61

Chapter 6: Metadata Components..............................................................................................62

i
Table of Contents
Component Field Data Types.....................................................................................................................................62
Supported Calls...........................................................................................................................................................62
ApexClass....................................................................................................................................................................63
ApexComponent.........................................................................................................................................................64
ApexPage.....................................................................................................................................................................65
ApexTrigger.................................................................................................................................................................66
CustomApplication.....................................................................................................................................................68
CustomDataType........................................................................................................................................................69
CustomLabels..............................................................................................................................................................69
CustomObject.............................................................................................................................................................71
CustomField....................................................................................................................................................74
ListView..........................................................................................................................................................79
Picklist.............................................................................................................................................................81
RecordType......................................................................................................................................................84
SearchLayouts..................................................................................................................................................86
SharingReason.................................................................................................................................................88
SharingRecalculation.......................................................................................................................................89
ValidationRule.................................................................................................................................................90
Weblink...........................................................................................................................................................91
Metadata Field Types......................................................................................................................................94
CustomObjectTranslation...........................................................................................................................................95
CustomPageWebLink...............................................................................................................................................100
CustomSite................................................................................................................................................................103
CustomTab................................................................................................................................................................106
Dashboard.................................................................................................................................................................108
Document..................................................................................................................................................................114
EmailTemplate..........................................................................................................................................................115
Folder.........................................................................................................................................................................118
HomePageComponent..............................................................................................................................................119
HomePageLayout......................................................................................................................................................120
Layout........................................................................................................................................................................121
Letterhead.................................................................................................................................................................127
Metadata....................................................................................................................................................................129
MetadataWithContent..............................................................................................................................................130
Portal.........................................................................................................................................................................131
Profile........................................................................................................................................................................133
Report........................................................................................................................................................................140
ReportType................................................................................................................................................................154
Scontrol.....................................................................................................................................................................157
StaticResource...........................................................................................................................................................159
Translations...............................................................................................................................................................160
Workflow...................................................................................................................................................................164

Index....................................................................................................................................................174

ii
Chapter 1
Understanding the Metadata API

Use the asynchronous metadata API to manage setup and customization information (metadata) for your organizations:

• Export the customizations in your organization as XML metadata files. See Working with the Zip File and retrieve().
• Migrate configuration changes between organizations. See deploy() and retrieve().
• Modify existing customizations in your organization using XML metadata files. See deploy() and retrieve().
• Manage customizations in your organization programmatically. See CRUD-Based Metadata Development, create(), update(),
and delete().

You can modify metadata in test organizations on Developer Edition or Sandbox, and then deploy tested changes to production organizations
on Enterprise Edition or Unlimited Editions. You can also create scripts to populate a new organization with your custom objects, custom
fields, and other components.

When to Use the Metadata API

Use the metadata API to create, retrieve, update or delete customization information, such as custom object definitions and
page layouts, for your organization. This API is intended for managing customizations and for building tools that can manage
the metadata model, not the data itself. To create, retrieve, update or delete records, such as accounts or leads, use the Force.com
Web Services API. This API is used to manage your data.

Supported Salesforce Editions

To use the metadata API, your organization must use Enterprise Edition, Unlimited Edition, or Developer Edition. If you
are an existing Salesforce customer and want to upgrade to either Enterprise or Unlimited Edition, contact your account
representative.
To develop client applications, it is strongly recommended that you use Salesforce Sandbox Edition, which is an exact replica
of your Salesforce deployment, including all customization and data. For more information, see
http://www.salesforce.com/products/sandbox.jsp.
Developer Edition provides access to all of the features available with Enterprise Edition. Developer Edition is constrained
only by the number of users and the amount of storage space. Developer Edition provides a development context that allows
you to build and test your solutions without affecting your organization’s live data. Developer Edition accounts are available
for free at http://wiki.apexdevnet.com/index.php/Getting_Started.
Note: A metadata component must be visible in the organization for the API metadata to act on it. Also, a user must
be assigned to a profile with the "API Enabled" permission to have access to metadata components.

3
Understanding the Metadata API Development Platforms

Development Platforms
The metadata API supports both CRUD-based and file-based development.

CRUD-Based Development
The CRUD-based asynchronous metadata API calls create(), update(), and delete() act upon the metadata
components in a manner similar to the way synchronous API calls in the enterprise WSDL act upon objects. For more
information about the enterprise WSDL, see the Force.com Web Services API Developer's Guide.
Note: CRUD (create, read, update, delete) implies that there is a read call, but there is no equivalent read call for
CRUD-based development. If you want to read your metadata, you should use the retrieve() call, described in
File-Based Development on page 4.

Use the create(), update(), and delete()calls with the utility call checkStatus(). For more information, see
CRUD-Based Metadata Development on page 23 and Quick Start on page 6.

File-Based Development
The declarative or file-based asynchronous metadata API deploy() and retrieve() calls deploy or retrieve a .zip file
that holds components in a set of folders, and a manifest file named package.xml. For more information, see Declarative
Metadata Development on page 32. The easiest way to access this functionality is to use the Force.com IDE or Force.com
Migration Tool. However, the underlying calls have been exposed for you to use directly, if needed. For more information
about the Force.com IDE or Force.com Migration Tool, see developer.force.com.

Standards Compliance
The metadata API is implemented to comply with the following specifications:

Standard Name Website

Simple Object Access Protocol (SOAP) 1.1 http://www.w3.org/TR/2000/NOTE-SOAP-20000508/
Web Service Description Language (WSDL) 1.1 http://www.w3.org/TR/2001/NOTE-wsdl-20010315
WS-I Basic Profile 1.1 http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html

Metadata API Support Policy

Salesforce.com support previous versions of the metadata API. However, your new client applications should use the most
recent version of the Force.com metadata API WSDL file to fully exploit the benefits of richer features and greater efficiency.

Backward Compatibility
Salesforce.com strives to make backward compatibility easy when using the Force.com platform.
Each new Salesforce release consists of two components:

4
Understanding the Metadata API What’s New in Version 15.0

• A new release of platform software that resides on salesforce.com systems

• A new version of the API
For example, the Spring '07 release included API version 9.0 and the Summer '07 release included API version 10.0.
We maintain support for each API version across releases of the platform software. The API is backward compatible in that
an application created to work with a given API version will continue to work with that same API version in future platform
software releases.
Salesforce.com does not guarantee that an application written against one API version will work with future API versions:
Changes in method signatures and data representations are often required as we continue to enhance the API. However, we
strive to keep the API consistent from version to version with minimal if any changes required to port applications to newer
API versions.
For example, an application written using API version 9.0 which shipped with the Spring ’07 release will continue to work
with API version 9.0 on the Summer ’07 release and on future releases beyond that. However, that same application may not
work with API version 10.0 without modifications to the application.

API End-of-Life
Salesforce.com is committed to supporting each API version for a minimum of three years from the date of first release. In
order to mature and improve the quality and performance of the API, versions that are more than three years old may cease
to be supported.
When an API version is to be deprecated, advance end-of-life notice will be given at least one year before support for the API
version is ended. Salesforce.com will directly notify customers using API versions planned for deprecation.

What’s New in Version 15.0

New features and changes to existing functionality are described in the Salesforce Release Notes for each release. They are
available in the Salesforce online help.

Related Resources
The salesforce.com developer website provides a full suite of developer toolkits, sample code, sample SOAP messages,
community-based support, and other resources to help you with your development projects. Be sure to visit
https://wiki.apexdevnet.com/index.php/Getting_Started for more information, or visit http://developer.force.com/join to sign
up for a free Developer Edition account.
You can visit these websites to find out more about Salesforce applications:
• Developer Force provides a wealth of information for developers.
• Salesforce.com for information about the Salesforce application.
• Force.com AppExchange for access to apps created for Salesforce.
• Salesforce.com Community for services to ensure Salesforce customer success.

5
Chapter 2
Quick Start

This quick start gives you all the information you need to start writing applications that use the metadata API to manage customizations for
your organization. It shows you how to get started with CRUD-Based Development and file-based development.
The easiest way to start working with file-based development is to use the Force.com IDE or Force.com Migration Tool. However, the
underlying calls have been exposed for you to use directly, if needed. For more information about the Force.com IDE or Force.com Migration
Tool, see developer.force.com.

Prerequisites
Before you can start using the metadata metadata API, you need to do some background work:
• Identify a user that has a profile with the "API Enabled" and "Modify All Data" permissions. These permissions are
required to access metadata API calls.
• Install a SOAP client. The metadata API works with current SOAP development environments, including, but not limited
to, Visual Studio .NET 2005, and Apache Axis. In this document, we provide examples in Java. The Java examples are
based on Apache Axis 1.3 and JDK 5.0 ( Java 2 Platform Standard Edition Development Kit 5.0). For more information
about Apache Axis 1.3, go to http://ws.apache.org/axis/. To see a complete list of compatible development platforms and
more sample code, go to developer.force.com.
Note: Development platforms vary in their SOAP implementations. Implementation differences in certain
development platforms might prevent access to some or all of the features in the metadata API. If you are using
Visual Studio for .NET development, we recommend that you use Visual Studio 2003 or higher.

Step 1: Obtain a Salesforce Developer Edition Account

If you are not already a member of the developer community, go to http://developer.force.com/join and follow the instructions
for signing up for a Developer Edition account. Even if you already have an Enterprise Edition or Unlimited Edition account,
it is strongly recommended that you use Developer Edition for developing, staging, and testing your solutions against sample
data to protect your organization’s live data. This is especially true for applications that will be inserting, updating, or deleting
metadata (as opposed to simply reading metadata).

6
Quick Start Step 2: Generate or Obtain the Web Service WSDLs

Step 2: Generate or Obtain the Web Service WSDLs

To access metadata API calls, you need a Web Service Description Language (WSDL) file. The WSDL file defines the Web
service that is available to you. Your development platform uses this WSDL to generate stub code to access the Web service
it defines. You can either obtain the WSDL file from your organization’s Salesforce administrator or you can generate it
yourself if you have access to the WSDL download page in the Salesforce user interface. For more information about WSDL,
see http://www.w3.org/TR/wsdl.
Before you can access metadata API calls, you must authenticate to use the Web service using the login() call, which is
defined in the enterprise WSDL and the partner WSDL. Therefore, you must also obtain either of these WSDLs. For more
information about the enterprise WSDL and the partner WSDL, see Step 2: Generate or Obtain the Web Service WSDL
in the Force.com Web Services API Developer's Guide.

Generating the WSDL File for Your Organization

Any user with the “Modify All Data” permission can download the Web Services Description Language (WSDL) file to
integrate and extend the Salesforce platform. (The System Administrator profile has this permission.)
The sample code in Step 4: Walk Through the Sample Code uses the enterprise WSDL, though the partner WSDL works
equally well.
To generate the metadata and enterprise WSDL files for your organization:
1. Log in to your Enterprise, Unlimited, or Developer Edition Salesforce account. You must log in as an administrator or as
a user who has the “Modify All Data” permission.
2. Click Setup ➤ Develop ➤ API.
3. Click the Download Metadata WSDL link and save the XML WSDL file to your file system.
4. Click the Download Enterprise WSDL link and save the XML WSDL file to your file system.

Step 3: Import the WSDL Files Into Your Development Platform

Once you have the WSDL files, import them into your development platform so that your development environment can
generate the necessary objects for use in building client Web service applications. This section provides sample instructions
for Apache Axis. For instructions about other development platforms, see your platform’s product documentation.
Note: The process for importing WSDL files is identical for the metadata and enterprise WSDL files.

Instructions for Java Environments (Apache Axis)

Java environments access the API through Java objects that serve as proxies for their server-side counterparts. Before using
the API, you must first generate these objects from your organization’s WSDL file.
Each SOAP client has its own tool for this process. For Apache Axis, use the WSDL2Java utility.
Note: Before you run WSDL2Java, you must have Axis installed on your system and all of its component JAR files
must be referenced in your classpath.

7
Quick Start Step 4: Walk Through the Sample Code

The basic syntax for WSDL2Java is:

java –classpath pathToJAR/Filename org.apache.axis.wsdl.WSDL2Java -a pathToWsdl/WsdlFilename

The -a switch generates code for all elements, referenced or not, which may be necessary depending on your WSDL. For
more information, see the WSDL2Java documentation.
If you have JAR files in more than one location, list them with a semicolon separating the files. For example, if the Axis JAR
files are installed in C:\axis-1.3, and the WSDL is named my_metadata.wsdl and is stored in C:\mywsdls, use
the following command to generate the Java stub files:

java –classpath
c:\axis-1.3\lib\axis.jar;c:\axis-1.3\lib\axis-ant.jar;c:\axis-1.3\lib\axis-schema.jar;
c:\axis-1.3\lib\commons-discovery-0.2.jar;c:\axis-1.3\lib\commons-logging-1.0.4.jar;
c:\axis-1.3\lib\jaxrpc.jar;c:\axis-1.3\lib\log4j-1.2.8.jar;c:\axis-1.3\lib\saaj.jar;
c:\axis-1.3\lib\wsdl4j-1.5.2.jar;c:\axis-1.3\mail.jar;c:\axis-1.3\activation.jar;c:\axis-1.3\wsdl4j.jar;
org.apache.axis.wsdl.WSDL2Java -a C:\mywsdls\my_metadata.wsdl

To generate stub files for the enterprise WSDL, use a similar command:

These commands generate a set of folders and Java source code files in the same directory in which they were run. After these
files are compiled, they can be included in your Java programs for use in creating client applications.
For most Java development environments, you can use wizard-based tools for this process instead of the command line. For
more information about using WSDL2Java, see http://ws.apache.org/axis/java/reference.html. For more information about
using WSDL2Java with Force.com, visit the message boards at http://www.salesforce.com/developer/boards.jsp.

Step 4: Walk Through the Sample Code

Once you have imported the WSDL files, you can begin building client applications that use the metadata metadata API.
The samples listed below are a good starting point for writing your own code.
• Java Sample Code for CRUD-Based Development on page 8
• Java Sample Code for File-Based Development on page 12

Java Sample Code for CRUD-Based Development

This section walks through a sample Java client application that uses CRUD-Based Development calls. The purpose of this
sample application is to show the required steps for authentication using the login() call and to demonstrate the invocation
and subsequent handling of several metadata API calls, including create() and checkStatus(). This sample application
performs the following main tasks:
1. Prompts the user for their Salesforce username and password.
2. Calls login() which is part of the enterprise WSDL and, if the login succeeds:
• Sets the returned sessionId into the session header for the metadata SOAP binding. This is required for session
authentication on subsequent metadata API calls.
• Resets the endpoint to the returned metadataServerUrl, which is the target of subsequent metadata API calls.

8
Quick Start Step 4: Walk Through the Sample Code

All client applications that access the metadata API must complete the tasks in this step before attempting any subsequent
metadata API calls.

3. Calls create() to create a new custom object.

Salesforce returns an AsyncResult object for each component you tried to create. The AsyncResult object is updated with
status information as the operation moves from a queue to completed or error state.
4. Calls checkStatus() in a loop until the status value in AsyncResult indicates that the create operation is completed.
Start with a wait time of one second between iterations of checkStatus() calls, and double the wait time each time
you make a subsequent call.
Note the error handling code that follows each API call.

package com.doc.samples;

import java.io.*;
import javax.xml.rpc.ServiceException;

import com.sforce.soap.enterprise.*;
import com.sforce.soap.enterprise.fault.ExceptionCode;
import com.sforce.soap.enterprise.fault.LoginFault;

/**
* Title: Sample that logs in and creates a custom object.
*
* Description: Console application illustrating login, session management,
* and server redirection.
*
* Assumptions:
* 1. The Enterprise WSDL has been downloaded and sample stub code has been generated
* by a tool like WSDL2Java. The Enterprise or Partner WSDL must be used to
* use the login() call for authentication. In this case, we use the Enterprise WSDL.
* 2. The Metadata WSDL has been downloaded and sample stub code has been generated
* by a tool like WSDL2Java.
*
*/
public class CreateSample {
// binding for the Enterprise WSDL used for login() call
private SoapBindingStub binding;
// binding for the metadata WSDL used for create() and checkStatus() calls
private MetadataBindingStub metadatabinding;

static BufferedReader rdr = new BufferedReader(new InputStreamReader(System.in));

// one second in milliseconds

private static final long ONE_SECOND = 1000;

public CreateSample() {
}

public static void main(String[] args) throws ServiceException {

CreateSample samples1 = new CreateSample();
samples1.run();
}

//The sample client application retrieves the user's login credentials.

9
Quick Start Step 4: Walk Through the Sample Code

// Helper function for retrieving user input from the console

String getUserInput(String prompt) {
System.out.print(prompt);
try {
return rdr.readLine();
}
catch (IOException ex) {
return null;
}
}

/**
* The login call is used to obtain a token from Salesforce.
* This token must be passed to all other calls to provide
* authentication.
*/
private boolean login() throws ServiceException {
String userName = getUserInput("Enter username: ");
String password = getUserInput("Enter password: ");
/** Next, the sample client application initializes the binding stub.
*
* This is our main interface to the API for the Enterprise WSDL.
* The getSoap method takes an optional parameter,
* (a java.net.URL) which is the endpoint.
* For the login call, the parameter always starts with
* http(s)://www.salesforce.com. After logging in, the sample
* client application changes the endpoint to the one specified
* in the returned loginResult object.
*/
binding = (SoapBindingStub) new SforceServiceLocator().getSoap();

// Time out after a minute

binding.setTimeout(60000);
// Log in using the Enterprise WSDL binding
LoginResult loginResult;
try {
System.out.println("LOGGING IN NOW....");
loginResult = binding.login(userName, password);
}
catch (LoginFault ex) {

// The LoginFault derives from AxisFault

ExceptionCode exCode = ex.getExceptionCode();
if (exCode == ExceptionCode.FUNCTIONALITY_NOT_ENABLED ||
exCode == ExceptionCode.INVALID_CLIENT ||
exCode == ExceptionCode.INVALID_LOGIN ||
exCode == ExceptionCode.LOGIN_DURING_RESTRICTED_DOMAIN ||
exCode == ExceptionCode.LOGIN_DURING_RESTRICTED_TIME ||
exCode == ExceptionCode.ORG_LOCKED ||
exCode == ExceptionCode.PASSWORD_LOCKOUT ||
exCode == ExceptionCode.SERVER_UNAVAILABLE ||
exCode == ExceptionCode.TRIAL_EXPIRED ||
exCode == ExceptionCode.UNSUPPORTED_CLIENT) {
System.out.println("Please be sure that you have a valid username " +
"and password.");
} else {
// Write the fault code to the console
System.out.println(ex.getExceptionCode());
// Write the fault message to the console
System.out.println("An unexpected error has occurred." + ex.getMessage());
}
return false;
} catch (Exception ex) {
System.out.println("An unexpected error has occurred: " + ex.getMessage());
ex.printStackTrace();
return false;
}

10
Quick Start Step 4: Walk Through the Sample Code

// Check if the password has expired

if (loginResult.isPasswordExpired()) {
System.out.println("An error has occurred. Your password has expired.");
return false;
}

/** Once the client application has logged in successfully, we use

* the results of the login call to reset the endpoint of the service
* to the virtual server instance that is servicing your organization.
* To do this, the client application sets the ENDPOINT_ADDRESS_PROPERTY
* of the binding object using the URL returned from the LoginResult. We
* use the metadata binding from this point forward as we are invoking
* calls in the metadata WSDL.
*/
metadatabinding = (MetadataBindingStub)
new MetadataServiceLocator().getMetadata();
metadatabinding._setProperty(MetadataBindingStub.ENDPOINT_ADDRESS_PROPERTY,
loginResult.getMetadataServerUrl());

/** The sample client application now has an instance of the MetadataBindingStub
* that is pointing to the correct endpoint. Next, the sample client application
* sets a persistent SOAP header (to be included on all subsequent calls that
* are made with the SoapBindingStub) that contains the valid sessionId
* for our login credentials. To do this, the sample client application
* creates a new SessionHeader object and set its sessionId property to the
* sessionId property from the LoginResult object.
*/
// Create a new session header object and add the session id
// from the login return object
SessionHeader sh = new SessionHeader();
sh.setSessionId(loginResult.getSessionId());
/** Next, the sample client application calls the setHeader method of the
* SoapBindingStub to add the header to all subsequent method calls. This
* header will persist until the binding is destroyed or until the header
* is explicitly removed. The "SessionHeader" parameter is the name of the
* header to be added.
*/
// set the session header for subsequent call authentication
metadatabinding.setHeader(
new MetadataServiceLocator().getServiceName().getNamespaceURI(),
"SessionHeader", sh);

// return true to indicate that we are logged in, pointed

// at the right url and have our security token in place.
return true;
}

/**
* Create a custom object. This method demonstrates usage of the
* create() and checkStatus() calls.
*/
private void createCustomObject() {
CustomObject co = new CustomObject();
String name = "My Custom Object";
co.setFullName("MyCustomObject" + "__c");
co.setDeploymentStatus(DeploymentStatus.Deployed);
co.setDescription("Created by the Metadata API Sample");
co.setEnableActivities(true);
co.setLabel(name);
co.setPluralLabel(co.getLabel() + "s");
co.setSharingModel(SharingModel.ReadWrite);
CustomField nf = new CustomField();
nf.setType(FieldType.Text);
nf.setDescription("The custom object identifier on page layouts, " +
"related lists etc");
nf.setLabel("My Custom Object");
nf.setFullName("MyCustomObject" + " __c");

11
Quick Start Step 4: Walk Through the Sample Code

// The name field appears in page layouts, related lists, and elsewhere.
co.setNameField(nf);

try {
AsyncResult[] ars = metadatabinding.create(new CustomObject[] { co });
if (ars == null) {
System.out.println("The object was not created successfully");
return;
}

String createdObjectId = ars[0].getId();

String[] ids = new String[] {createdObjectId};
boolean done = false;
long waitTimeMilliSecs = ONE_SECOND;
AsyncResult[] arsStatus = null;

/**
* After the create() call completes, we must poll the results
* of the checkStatus() call until it indicates that the create
* operation is completed.
*/
while (!done) {
arsStatus = metadatabinding.checkStatus(ids);
if (arsStatus == null) {
System.out.println("The object status cannot be retrieved");
return;
}
done = arsStatus[0].isDone();
if (arsStatus[0].getStatusCode() != null ) {
System.out.println("Error status code: " +
arsStatus[0].getStatusCode());
System.out.println("Error message: " + arsStatus[0].getMessage());
}
Thread.sleep(waitTimeMilliSecs);
// double the wait time for the next iteration
waitTimeMilliSecs *= 2;
System.out.println("The object state is " + arsStatus[0].getState());
}

System.out.println("The ID for the created object is " +

arsStatus[0].getId());
}
catch (Exception ex) {
System.out.println("\nFailed to create object, error message was: \n"
+ ex.getMessage());
getUserInput("\nHit return to continue...");
}

private void run() throws ServiceException {

if (login()) {
getUserInput("SUCCESSFUL LOGIN! Hit the enter key to continue.");
createCustomObject();
}
}
}

Java Sample Code for File-Based Development

This section walks through a sample Java client application that uses file-based development calls. The purpose of this sample
application is to show the required steps for authentication using the login() call and to demonstrate the invocation and
subsequent handling of several metadata API calls, including retrieve() and deploy(). The sample application performs
the following main tasks:
1. Prompts the user for their Salesforce username and password.

12
Quick Start Step 4: Walk Through the Sample Code

2. Calls login() which is part of the enterprise WSDL and, if the login succeeds:
• Sets the returned sessionId into the session header for the metadata SOAP binding. This is required for session
authentication on subsequent metadata API calls.
• Resets the endpoint to the returned metadataServerUrl, which is the target of subsequent metadata API calls.
All client applications that access the metadata API must complete the tasks in this step before attempting any subsequent
metadata API calls.

3. Prompts the user to execute a retrieve() and deploy() call. The user can execute retrieve() or deploy()
calls until they choose the exit option.
The retrieve() and deploy() calls both operate on a zip file named components.zip. The retrieve() call retrieves
components from your organization into components.zip, and the deploy() call deploys the components in components.zip
to your organization. If you save the sample to your computer and execute it, you should run the retrieve option first so that
you have a components.zip file that you can subsequently deploy.
The retrieve() call uses a manifest file to determine the components to retrieve from your organization. A sample
package.xml manifest file is listed below. For more details on the manifest file structure, see Working with the Zip File on
page 32. For the purposes of this sample, it is sufficient to know that this manifest file retrieves all custom objects, custom
tabs, and page layouts.

<?xml version="1.0" encoding="UTF-8"?>

<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
<members>*</members>
<name>CustomObject</name>
</types>
<types>
<members>*</members>
<name>CustomTab</name>
</types>
<types>
<members>*</members>
<name>Layout</name>
</types>
<version>15.0</version>
</Package>

Note the error handling code that follows each API call.
Note: This sample was created using Apache Axis. The WSDL2Java utility generates a _package class, even though
the metadata type is defined as Package in the Metadata WSDL. Other SOAP clients may generate a different
name for the _package class.

package com.doc.samples;

import java.io.BufferedReader;
import java.io.ByteArrayInputStream;
import java.io.ByteArrayOutputStream;
import java.io.File;
import java.io.FileInputStream;
import java.io.FileOutputStream;
import java.io.IOException;
import java.io.InputStream;
import java.io.InputStreamReader;
import java.nio.ByteBuffer;
import java.nio.channels.Channels;
import java.nio.channels.FileChannel;
import java.nio.channels.ReadableByteChannel;
import java.nio.channels.WritableByteChannel;
import java.rmi.RemoteException;

13
Quick Start Step 4: Walk Through the Sample Code

import java.util.ArrayList;
import java.util.List;

import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.ParserConfigurationException;
import javax.xml.rpc.ServiceException;

import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.xml.sax.SAXException;

import com.sforce.soap._2006._04.metadata.AsyncRequestState;
import com.sforce.soap._2006._04.metadata.AsyncResult;
import com.sforce.soap._2006._04.metadata.CodeCoverageWarning;
import com.sforce.soap._2006._04.metadata.DeployMessage;
import com.sforce.soap._2006._04.metadata.DeployOptions;
import com.sforce.soap._2006._04.metadata.DeployResult;
import com.sforce.soap._2006._04.metadata.MetadataBindingStub;
import com.sforce.soap._2006._04.metadata.MetadataServiceLocator;
import com.sforce.soap._2006._04.metadata.PackageTypeMembers;
import com.sforce.soap._2006._04.metadata.RetrieveMessage;
import com.sforce.soap._2006._04.metadata.RetrieveRequest;
import com.sforce.soap._2006._04.metadata.RetrieveResult;
import com.sforce.soap._2006._04.metadata.RunTestFailure;
import com.sforce.soap._2006._04.metadata.RunTestsResult;
// Note that Axis generates a _package class, even though it is defined as Package
// in the WSDL. Other SOAP clients may generate a different name for the _package class.
import com.sforce.soap._2006._04.metadata._package;
import com.sforce.soap.enterprise.LoginResult;
import com.sforce.soap.enterprise.SessionHeader;
import com.sforce.soap.enterprise.SforceServiceLocator;
import com.sforce.soap.enterprise.SoapBindingStub;
import com.sforce.soap.enterprise.fault.ExceptionCode;
import com.sforce.soap.enterprise.fault.LoginFault;

public class DeployRetrieveFileBased

{
// binding for the Enterprise WSDL used for login() call
private SoapBindingStub binding;
// binding for the metadata WSDL used for create() and checkStatus() calls
private MetadataBindingStub metadatabinding;

static BufferedReader rdr = new BufferedReader(new InputStreamReader(System.in));

private static final String ZIP_FILE = "components.zip";

// manifest file that controls which components get retrieved

private static final String MANIFEST_FILE = "package.xml";

private static final double API_VERSION = 15.0;

// one second in milliseconds

private static final long ONE_SECOND = 1000;
// maximum number of attempts to deploy the zip file
private static final int MAX_NUM_POLL_REQUESTS = 50;

public static void main(String[] args) throws ServiceException, Exception {

DeployRetrieveFileBased sample = new DeployRetrieveFileBased();
sample.run();
}

private void run() throws ServiceException, Exception {

if (login()) {
getUserInput("SUCCESSFUL LOGIN! Hit the enter key to continue.");
// Show the options.

14
Quick Start Step 4: Walk Through the Sample Code

showMenu();
String choice = getUserInput("");
// Show the options to retrieve or deploy until user exits
while (choice != null && !choice.equals("99")) {
try {
if (choice.length() == 1 || choice.length() == 2) {
switch (new Integer(choice).intValue()) {
case 1:
retrieveZip();
break;
case 2:
deployZip();
break;
}
}
// show the menu again
showMenu();

} catch (Exception e) {
System.out.println("An unexpected error has occurred: "
+ e.getMessage());
e.printStackTrace();
}
//wait for the user input.
choice = getUserInput("");
}
}
}

private void deployZip()

throws RemoteException, Exception
{
byte zipBytes[] = readZipFile();
DeployOptions deployOptions = new DeployOptions();
deployOptions.setPerformRetrieve(false);
deployOptions.setRollbackOnError(true);
AsyncResult asyncResult = metadatabinding.deploy(zipBytes, deployOptions);

// Wait for the deploy to complete

int poll = 0;
long waitTimeMilliSecs = ONE_SECOND;
while (!asyncResult.isDone()) {
Thread.sleep(waitTimeMilliSecs);
// double the wait time for the next iteration
waitTimeMilliSecs *= 2;
if (poll++ > MAX_NUM_POLL_REQUESTS) {
throw new Exception("Request timed out. If this is a large set " +
"of metadata components, check that the time allowed by " +
"MAX_NUM_POLL_REQUESTS is sufficient.");
}
asyncResult = metadatabinding.checkStatus(
new String[] {asyncResult.getId()})[0];
System.out.println("Status is: " + asyncResult.getState());
}

if (asyncResult.getState() != AsyncRequestState.Completed) {
throw new Exception(asyncResult.getStatusCode() + " msg: " +
asyncResult.getMessage());
}

DeployResult result = metadatabinding.checkDeployStatus(asyncResult.getId());

if (!result.isSuccess()) {
printErrors(result);
throw new Exception("The files were not successfully deployed");
}

System.out.println("The file " + ZIP_FILE + " was successfully deployed\n");

15
Quick Start Step 4: Walk Through the Sample Code

/**
* Read in the zip file contents into a byte array.
* @return byte[]
* @throws Exception - if cannot find the zip file to deploy
*/
private byte[] readZipFile()
throws Exception
{
// We assume here that you have a deploy.zip file.
// See the retrieve sample for how to retrieve a zip file.
File deployZip = new File(ZIP_FILE);
if (!deployZip.exists() || !deployZip.isFile())
throw new Exception("Cannot find the zip file to deploy. Looking for " +
deployZip.getAbsolutePath());

FileInputStream fos = new FileInputStream(deployZip);

ByteArrayOutputStream bos = new ByteArrayOutputStream();
int readbyte = -1;
while ((readbyte = fos.read()) != -1) {
bos.write(readbyte);
}
fos.close();
bos.close();
return bos.toByteArray();
}

/**
* Print out any errors, if any, related to the deploy.
* @param result - DeployResult
*/
private void printErrors(DeployResult result)
{
DeployMessage messages[] = result.getMessages();
StringBuilder buf = new StringBuilder("Failures:\n");
for (DeployMessage message : messages) {
if (!message.isSuccess()) {
String loc = (message.getLineNumber() == null ? "" :
("(" + message.getLineNumber() + "," +
message.getColumnNumber() + ")"));
if (loc.length() == 0
&& !message.getFileName().equals(message.getFullName())) {
loc = "(" + message.getFullName() + ")";
}
buf.append(message.getFileName() + loc + ":" +
message.getProblem()).append('\n');
}
}
RunTestsResult rtr = result.getRunTestResult();
if (rtr.getFailures() != null) {
for (RunTestFailure failure : rtr.getFailures()) {
String n = (failure.getNamespace() == null ? "" :
(failure.getNamespace() + ".")) + failure.getName();
buf.append("Test failure, method: " + n + "." +
failure.getMethodName() + " -- " +
failure.getMessage() + " stack " +
failure.getStackTrace() + "\n\n");
}
}
if (rtr.getCodeCoverageWarnings() != null) {
for (CodeCoverageWarning ccw : rtr.getCodeCoverageWarnings()) {
buf.append("Code coverage issue");
if (ccw.getName() != null) {
String n = (ccw.getNamespace() == null ? "" :
(ccw.getNamespace() + ".")) + ccw.getName();

16
Quick Start Step 4: Walk Through the Sample Code

buf.append(", class: " + n);

}
buf.append(" -- " + ccw.getMessage() + "\n");
}
}

System.out.println(buf.toString());
}

private void retrieveZip() throws RemoteException, Exception

{
RetrieveRequest retrieveRequest = new RetrieveRequest();
retrieveRequest.setApiVersion(API_VERSION);
setUnpackaged(retrieveRequest);

AsyncResult asyncResult = metadatabinding.retrieve(retrieveRequest);

// Wait for the retrieve to complete
int poll = 0;
long waitTimeMilliSecs = ONE_SECOND;
while (!asyncResult.isDone()) {
Thread.sleep(waitTimeMilliSecs);
// double the wait time for the next iteration
waitTimeMilliSecs *= 2;
if (poll++ > MAX_NUM_POLL_REQUESTS) {
throw new Exception("Request timed out. If this is a large set " +
"of metadata components, check that the time allowed " +
"by MAX_NUM_POLL_REQUESTS is sufficient.");
}
asyncResult = metadatabinding.checkStatus(
new String[] {asyncResult.getId()})[0];
System.out.println("Status is: " + asyncResult.getState());
}

if (asyncResult.getState() != AsyncRequestState.Completed) {
throw new Exception(asyncResult.getStatusCode() + " msg: " +
asyncResult.getMessage());
}

RetrieveResult result = metadatabinding.checkRetrieveStatus(asyncResult.getId());

// Print out any warning messages

StringBuilder buf = new StringBuilder();
if (result.getMessages() != null) {
for (RetrieveMessage rm : result.getMessages()) {
buf.append(rm.getFileName() + " - " + rm.getProblem());
}
}
if (buf.length() > 0) {
System.out.println("Retrieve warnings:\n" + buf);
}

// Write the zip to the file system

System.out.println("Writing results to zip file");
ByteArrayInputStream bais = new ByteArrayInputStream(result.getZipFile());
File resultsFile = new File(ZIP_FILE);
FileOutputStream os = new FileOutputStream(resultsFile);
try {
ReadableByteChannel src = Channels.newChannel(bais);
FileChannel dest = os.getChannel();
copy(src, dest);

System.out.println("Results written to "

+ resultsFile.getAbsolutePath() + "\n");
}
finally {
os.close();

17
Quick Start Step 4: Walk Through the Sample Code

/**
* Helper method to copy from a readable channel to a writable channel,
* using an in-memory buffer.
*/
private void copy(ReadableByteChannel src, WritableByteChannel dest)
throws IOException
{
// use an in-memory byte buffer
ByteBuffer buffer = ByteBuffer.allocate(8092);
while (src.read(buffer) != -1) {
buffer.flip();
while(buffer.hasRemaining()) {
dest.write(buffer);
}
buffer.clear();
}
}

private void setUnpackaged(RetrieveRequest request) throws Exception

{
// Edit the path, if necessary, if your package.xml file is located elsewhere
File unpackedManifest = new File(MANIFEST_FILE);
System.out.println("Manifest file: " + unpackedManifest.getAbsolutePath());

if (!unpackedManifest.exists() || !unpackedManifest.isFile())
throw new Exception("Should provide a valid retrieve manifest " +
"for unpackaged content. " +
"Looking for " + unpackedManifest.getAbsolutePath());

// Note that we populate the _package object by parsing a manifest file here.
// You could populate the _package based on any source for your
// particular application.
_package p = parsePackage(unpackedManifest);
request.setUnpackaged(p);
}

private _package parsePackage(File file) throws Exception {

try {
InputStream is = new FileInputStream(file);
List<PackageTypeMembers> pd = new ArrayList<PackageTypeMembers>();
DocumentBuilder db =
DocumentBuilderFactory.newInstance().newDocumentBuilder();
Element d = db.parse(is).getDocumentElement();
for (Node c = d.getFirstChild(); c != null; c = c.getNextSibling()) {
if (c instanceof Element) {
Element ce = (Element)c;
//
NodeList namee = ce.getElementsByTagName("name");
if (namee.getLength() == 0) {
// not
continue;
}
String name = namee.item(0).getTextContent();
NodeList m = ce.getElementsByTagName("members");
List<String> members = new ArrayList<String>();
for (int i = 0; i < m.getLength(); i++) {
Node mm = m.item(i);
members.add(mm.getTextContent());
}
PackageTypeMembers pdi = new PackageTypeMembers();
pdi.setName(name);
pdi.setMembers(members.toArray(new String[members.size()]));
pd.add(pdi);

18
Quick Start Step 4: Walk Through the Sample Code

}
}
_package r = new _package();
r.setTypes(pd.toArray(new PackageTypeMembers[pd.size()]));
r.setVersion(API_VERSION + "");
return r;
} catch (ParserConfigurationException pce) {
throw new Exception("Cannot create XML parser", pce);
} catch (IOException ioe) {
throw new Exception(ioe);
} catch (SAXException se) {
throw new Exception(se);
}
}

/**
* Utility method to present options to retrieve or deploy.
* This method prints all the possible sample names to the console
* so that the user can select a particular sample by entering the corresponding
* number of the sample. Once the user enters the sample number, that particular
* sample will be invoked and run.
*/
private void showMenu() {

System.out.println(" 1: Retrieve");
System.out.println(" 2: Deploy");
System.out.println("99: Exit");
System.out.println(" ");
System.out.print("Enter 1 to retrieve, 2 to deploy, or 99 to exit: ");
}

// Time out after a minute

// The LoginFault derives from AxisFault

19
Quick Start Step 4: Walk Through the Sample Code

exCode == ExceptionCode.LOGIN_DURING_RESTRICTED_TIME ||
exCode == ExceptionCode.ORG_LOCKED ||
exCode == ExceptionCode.PASSWORD_LOCKOUT ||
exCode == ExceptionCode.SERVER_UNAVAILABLE ||
exCode == ExceptionCode.TRIAL_EXPIRED ||
exCode == ExceptionCode.UNSUPPORTED_CLIENT) {
System.out.println("Please be sure that you have a valid username " +
"and password.");
} else {
// Write the fault code to the console
System.out.println(ex.getExceptionCode());
// Write the fault message to the console
System.out.println("An unexpected error has occurred." + ex.getMessage());
}
return false;
} catch (Exception ex) {
System.out.println("An unexpected error has occurred: " + ex.getMessage());
ex.printStackTrace();
return false;
}
// Check if the password has expired
if (loginResult.isPasswordExpired()) {
System.out.println("An error has occurred. Your password has expired.");
return false;
}

/** Once the client application has logged in successfully, we use

// return true to indicate that we are logged in, pointed

// at the right url and have our security token in place.
return true;
}

20
Quick Start Step 4: Walk Through the Sample Code

//The sample client application retrieves the user's login credentials.

// Helper function for retrieving user input from the console
String getUserInput(String prompt) {
System.out.print(prompt);
try {
return rdr.readLine();
}
catch (IOException ex) {
return null;
}
}
}

21
Chapter 3
Error Handling

The metadata API calls return error information that your client application can use to identify and resolve runtime errors. The metadata
API provides the following types of error handling:

• Since the metadata API uses the enterprise or partner WSDLs to authenticate, it uses SOAP fault messages defined in those WSDLs
for errors resulting from badly formed messages, failed authentication, or similar problems. Each SOAP fault has an associated
ExceptionCode. For more details, see "Error Handling" in the Force.com Web Services API Developer's Guide.
• For errors with create(), update(), and delete(), see the error status code in the statusCode field in the AsyncResult
object for the associated component. For sample code, see Java Sample Code for CRUD-Based Development on page 8.
• For errors with deploy(), see the problem and success fields in the DeployMessage object for the associated component. For
sample code, see Java Sample Code for File-Based Development on page 12.
• For errors with retrieve(), see the problem field in the RetrieveMessage object for the associated component. For sample code,
see Java Sample Code for File-Based Development on page 12.

Error Handling for Session Expiration

When you sign on via the login() call, a new client session begins and a corresponding unique session ID is generated.
Sessions automatically expire after the amount of time specified in the Security Controls setup area of the Salesforce application
(default two hours). When your session expires, the exception code INVALID_SESSION_ID is returned. If this happens,
you must invoke the login() call again. For more information about login(), see the Force.com Web Services API Developer's
Guide.

22
Chapter 4
CRUD-Based Metadata Development

Use the CRUD-based metadata calls to create, update, or delete setup and configuration components for your organization or application.
These configuration components include custom objects, custom fields, and other configuration metadata. The metadata calls mimic the
behavior in the Salesforce user interface for creating, updating, or deleting components. Whatever rules apply there also apply to these calls.
Note: CRUD (create, read, update, delete) implies that there is a read call, but there is no equivalent read call for
CRUD-based development. If you want to read your metadata, you should use the retrieve() call, described in
File-Based Development on page 4.

Metadata calls are different from the core, synchronous API calls in the following ways:

• Metadata API calls are available in a separate WSDL. To download the WSDL, log into Salesforce, select Setup ➤ Develop ➤ API
and click the Download Metadata WSDL link.
• After logging in, you must send metadata API calls to the metadata API endpoint, which has a different URL than the Web Services
API. Retrieve the metadataServerUrl from the LoginResult returned by your Web Services API login() call. For more
information about the Web Services API, see the Force.com Web Services API Developer's Guide.
• There are three metadata calls with the same name as the corresponding core synchronous calls but with different signatures: create(),
update(), and delete(). There is also a special utility call, checkStatus(), which you use to poll for the completion of the
asynchronous call.
• Metadata calls are asynchronous, which means that the results are not returned in a single call; the API core calls are synchronous; the
results are returned in one call.
• The responses returned are all of type AsyncResult, unlike core API calls, which return different result types.
The following development workflow is common for CRUD-based metadata calls:
1. The logged-in user issues a metadata call, specifying all required fields to be created or updated.
2. Salesforce returns an AsyncResult object for each component you tried to create or update. The AsyncResult object is updated with status
information as the operation moves from a queue to completed or error state.
3. Call checkStatus() in a loop until the status values in AsyncResult indicate that all the create or update operations are completed.
Start with a wait time of one second between iterations of checkStatus() calls, and double the wait time each time you make a
subsequent call.

Note: There are two metadata calls that support declarative or file-based metadata development. For more information,
see Declarative Metadata Development.

checkStatus()
Checks the status of asynchronous metadata calls create(), update(), or delete(), or the declarative metadata calls
deploy() or retrieve().

23
CRUD-Based Metadata Development create()

Syntax

AsyncResult[] = metadatabinding.checkStatus(ID[] ids);

Usage
Use this call to check whether or not an asynchronous metadata call or declarative metadata call has completed.

Sample Code—Java
See Step 4: Walk Through the Sample Code for sample Java code using this call.

Arguments

Name Type Description

ids ID[] Array of one or more IDs. Each ID is returned in an AsyncResult and corresponds to a
component being created, updated, deleted, deployed, or retrieved.

Response
AsyncResult[]

AsyncResult[] = metadatabinding.create(Metadata[] metadata);

Usage
Use this call to add one or more metadata components to your organization’s information.

Permissions
Your client application must be logged in with the "Modify All Data" permission.

Required Fields
Required fields are determined by the metadata components being created. For more information about specific component
types, see Metadata Components on page 62.

24
CRUD-Based Metadata Development AsyncResult

Valid Data Values

You must supply values that are valid for the field’s data type, such as integers (not alphabetic characters) for integer fields. In
your client application, follow the data formatting rules specified for your programming language and development tool (your
development tool will handle the appropriate mapping of data types in SOAP messages).

String Values
When storing values in string fields, the API trims any leading and trailing whitespace. For example, if the value of a label
field is entered as "MyObject ", the value is stored in the database as "MyObject".

Basic Steps for Creating Metadata Components

Use the following process to create metadata components:
1. Design an array and populate it with the components that you want to create.
2. Call create() with the component array passed in as an argument.
3. An AsyncResult object is returned for each component you tried to create. It is updated with status information as the
operation moves from a queue to completed or error state. Call checkStatus() in a loop until the status values in
AsyncResult indicate that all the create operations are completed. Start with a wait time of one second between iterations
of checkStatus() calls, and double the wait time each time you make a subsequent call.

Sample Code—Java
See Step 4: Walk Through the Sample Code for sample Java code using the create() call.

Arguments

Name Type Description

metadata Metadata[]
Array of one or more metadata components.
Limit: 10.
You must submit arrays of only one type of component. For example, you could submit
an array of 10 custom objects or 10 profiles, but not a mix of both types.

Response
AsyncResult[]

See Also:
update()
delete()
checkStatus()

25
CRUD-Based Metadata Development delete()

Use the checkStatus() call against each object to discover when the call is completed for that object. Salesforce updates
each AsyncResult object as the call completes, and errors, if any, are encountered.
Each AsyncResult object has the following properties:

Name Type Description

done boolean Indicates whether the call has completed (true) or not (false).
id ID ID of the component being created, updated, deleted, deployed, or retrieved.
message string Message corresponding to the statusCode field returned, if any.
secondsToWait int Indicates the number of seconds before the call is likely to complete. This is an
estimate only. This field has been deprecated as of version 13.0 and is only provided
for backward compatibility.
state AsyncRequestState The AsyncRequestState object has one of four possible values:
(enumeration of • Queued: This call has not started. It is waiting in a queue.
type string) • InProgress: This call has started, but has not completed yet.
• Completed: This call has been completed.
• Error: An error occurred, see the statusCode for more information.

statusCode StatusCode If an error occurred during the create(), update(), or delete() call, a
(enumeration of status code is returned, and the message corresponding to the status code is returned
type string) in the message field.
For a description of each StatusCode value, see "StatusCode" in the Force.com Web
Services API Developer's Guide.

delete()
Deletes one or more components from your organization’s data. This call can be used to delete any of the objects that extend
Metadata. For more details, see Metadata Components on page 62.

Syntax

AsyncResult[] = metadatabinding.delete(Metadata[] metadata);

Usage
Use this call to delete one or more components from your organization’s data.

Permissions
Your client application must be logged in with the "Modify All Data" permission.

Rules and Guidelines

When deleting components, consider the following rules and guidelines:
• Your client application must be logged in with sufficient access rights to delete individual components within the specified
component. For more information, see "Factors that Affect Data Access" in the Force.com Web Services API Guide.

26
CRUD-Based Metadata Development AsyncResult

• In addition, you might also need permission to access this component’s parent component.
• To ensure referential integrity, this call supports cascading deletions. If you delete a parent component, you delete its
children automatically, as long as each child component can be deleted.
• Unlike some standard objects, all metadata components can be deleted.

Basic Steps for Deleting Metadata Components

Use the following process to delete metadata components:
1. Determine the fullName of each component that you want to delete. See Metadata for more details on the fullName
field. You must delete only components of the same type in a single call.
2. Invoke this call, passing in the array of metadata components with fullName specified.
3. An AsyncResult object is returned for each component you tried to delete. It is updated with status information as the
operation moves from a queue to completed or error state. Call checkStatus() in a loop until the status values in
AsyncResult indicate that all the delete operations are completed. Start with a wait time of one second between iterations
of checkStatus() calls, and double the wait time each time you make a subsequent call.

Sample Code—Java

CustomObject co = new CustomObject();

String name = "MyCustomObject”;
co.setFullName(name + "__c");
AsyncResult[] ars = stub.delete(new Metadata[] { co });

Arguments

Name Type Description

metadata Metadata[]
Array of one or more metadata components. You only need to set the fullName field
in the Metadata object.
Limit: 10.
You must submit arrays of only one type of component. For example, you could submit
an array of 10 custom objects or 10 profiles, but not a mix of both types.

Response
AsyncResult[]

See Also:
create()
update()
checkStatus()

27
CRUD-Based Metadata Development update()

Name Type Description

update()
Updates one or more components in your organization’s data. This call can be used to update any of the objects that extend
Metadata. For more details, see Metadata Components on page 62.

Syntax

AsyncResult[] = metadatabinding.update(UpdateMetadata[] metadata);

Usage
Use this call to update one or more components. This call is analogous to the ALTER TABLE statement in SQL.

Permissions
Your client application must be logged in with the "Modify All Data" permission.

Updateable Objects
Unlike standard objects, all metadata components can be updated.

28
CRUD-Based Metadata Development update()

Required Fields
You must supply values for all the required fields in the component.

Valid Field Values

String Values
When storing values in string fields, the API trims any leading and trailing white space. For example, if the value of a label
field is entered as " MyObject ", the value is stored in the database as "MyObject".

Basic Steps for Updating Metadata Components

Use this process to update metadata components:
1. Invoke this call, passing in an array of metadata components that represent the components you wish to update.
2. An AsyncResult object is returned for each component or field you tried to update. It is updated with status information
as the operation moves from a queue to completed or error state. Use checkStatus() to check on the status values in
AsyncResult.
3. An AsyncResult object is returned for each component you tried to update. It is updated with status information as the
operation moves from a queue to completed or error state. In a loop, call checkStatus() until the status values in
AsyncResult indicate that all the update operations are completed. Start with a wait time of one second between iterations
of checkStatus() calls, and double the wait time each time you make a subsequent call.

Sample Code—Java

CustomObject co = new CustomObject();

String name = "MyCustomObject”;
co.setFullName(name + "__c");
co.setDeploymentStatus(DeploymentStatus.Deployed);
co.setDescription("Created by the Metadata API");
co.setEnableActivities(true);
co.setLabel(name + " Object");
co.setPluralLabel(co.getLabel() + "s");
co.setSharingModel(SharingModel.ReadWrite);

CustomField nf = new CustomField();

nf.setType(FieldType.Text);
nf.setLabel(co.getFullName() + " Name");

co.setNameField(nf);

UpdateMetadata updateMetadata = new UpdateMetadata();

updateMetadata.setMetadata(co);
updateMetadata.setCurrentName(“TheCurrentName”); // co.getFullName();

29
CRUD-Based Metadata Development AsyncResult

AsyncResult[] ars = stub.update(new UpdateMetadata[] { updateMetadata});

Arguments

Name Type Description

metadata UpdateMetadata[] Array of one or more UpdateMetadata data structures that represent
the components you wish to update.
Limit: 10.
You must submit arrays of only one type of component. For example,
you could submit an array of 10 custom objects or 10 profiles, but
not a mix of both types.

UpdateMetadata
One or more UpdateMetadata objects are defined in the metadata argument. This object can be used to update any of the
objects that extend Metadata. For more details, see Metadata Components on page 62. Each UpdateMetadata object has the
following fields:

Field Field Type Description

currentName string The API name of the component or field before the update. For
example, if you wanted to update a CustomObject named Foo, the
value of this field would be Foo_c. This value is supplied because
this call may change the name, and the value here provides mapping.
metadata Metadata Full specification of the component or field you wish to update.

Response
AsyncResult[]

See Also:
create()
delete()
checkStatus()

AsyncResult
Poll the values in this object to determine when an asynchronous metadata call has completed, and whether it was successful
or not. The asynchronous metadata calls create(), update(), and delete() return an array of AsyncResult objects.
Each element in the array corresponds to an element in the array of metadata components passed in the call.
Use the checkStatus() call against each object to discover when the call is completed for that object. Salesforce updates
each AsyncResult object as the call completes, and errors, if any, are encountered.
Each AsyncResult object has the following properties:

30
CRUD-Based Metadata Development AsyncResult

Name Type Description

31
Chapter 5
Declarative Metadata Development

Use the file-based metadata API deploy() and retrieve() calls to facilitate Salesforce application development and deployment.
These two calls allow you to manage applications in your own source-code control system such as CVS or Perforce. You can create text files
that define components, such as custom objects, custom fields, s-controls, Apex code packages, and other Salesforce objects, and then deploy
these artifacts to a Salesforce organization.
The Salesforce supported tools, Force.com IDE and Force.com Migration Tool, use the file-based metadata API calls. Most developers
should use these tools instead of writing code that calls the metadata API directly. However, because the metadata API calls are designed to
manipulate text files, all of the behavior and concepts around the file directory structure, manifests, packaging, and file contents for components
such as custom objects and Apex-related components apply equally to the metadata API, Force.com IDE, and Force.com Migration Tool.
Declarative metadata development has no impact on packaging or the Force.com AppExchange. Packaging is still the mechanism by which
applications can be distributed to others. Declarative metadata development is instead designed for the following tasks:

• Team development of an application in a Developer Edition organization. When development and testing is completed, the application
is then distributed via Force.com AppExchange.
• Development of a custom application (or customization) in a Developer Edition organization or a sandbox. The application or customization
is then deployed into a production organization using the metadata metadata API as opposed to AppExchange packaging.

The existing asynchronous metadata API calls create(), update(), and delete() work with the same structures as the file-based
metadata API calls deploy() and retrieve().
Note that deploy() operates transactionally, so if something in the deployment fails, such as a problem with the code or a test run failure,
the entire transaction fails and your organization will be unchanged.

Working with the Zip File

The deploy() and retrieve() calls deploy and retrieve components in a .zip file. You can work with various metadata
types, such as ApexClass or CustomObject. A component is an instance of a metadata type. The .zip file contains a directory
and set of component files based on the contents being retrieved or deployed. The files retrieved or deployed may be unpackaged
components that reside in your organization (such as standard objects), or packaged components that reside within named
packages.
Note: A .zip file can contain a maximum of 1500 files. If you are working with a large number of components, you
should use the listMetadata() call to identify the subset of files that you want to retrieve or deploy, or you should
retrieve or deploy batches of components in different .zip files.

Every .zip file contains the manifest, a file named package.xml, and a set of directories that contain the components.
The manifest file defines the components you are trying to retrieve or deploy in the .zip file.

32
Declarative Metadata Development Working with the Zip File

The following is a sample package.xml manifest file. You can retrieve an individual component for a metadata type by specifying
its fullName field value in a members element, or you can also retrieve all components of a metadata type, by
using<members>*</members>.

<?xml version="1.0" encoding="UTF-8"?>

<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
<members>MyCustomObject__c</members>
<name>CustomObject</name>
</types>
<types>
<members>*</members>
<name>CustomTab</name>
</types>
<types>
<members>Standard</members>
<name>Profile</name>
</types>
<version>15.0</version>
</Package>

The following elements may be defined in package.xml:

• <fullName> contains the name of the server-side package. If no <fullName> exists, this is a client-side unpackaged
package.
• <types> contains the name of the metadata type (for example, CustomObject) and the named members (for example,
myCustomObject__c), to be retrieved or deployed. There can be multiple <types> elements in a manifest file and there
is one entry for each named component, and one entry for each individual member.
• <members> contains the fullName of the component, for example MyCustomObject__c. The listMetadata()
call is useful to find out the fullName for components of a particular metadata type, if you want to retrieve an individual
component. For many metadata types, you can replace the value in members with the wildcard character * (asterisk)
instead of listing each member separately. Any metadata type that has a value of yes in the * column in the table below
supports use of this wildcard.
• <name> contains the metadata type, for example CustomObject or Profile. There is one name defined for each
metadata type in the directory. Any metadata type that extends Metadata is a valid value. The name entered must match
a metadata type defined in the metadata API WSDL. See Metadata Components on page 62 for a list.
• <version> is the API version number used when deploying or retrieving the .zip file. Currently the valid value is
15.0.
To delete items, use the same procedure but name the manifest file destructiveChanges.xml instead of package.xml.
If you try to delete items that do not exist in an organization, the rest of the deletion will be attempted.
The next sample package.xml manifest file illustrates how to work with custom fields and standard objects, such as accounts.

<?xml version="1.0" encoding="UTF-8"?>

<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
<members>MyCustomObject__c.MyCustomField__c</members>
<name>CustomField</name>
</types>
<types>
<members>Account</members>
<name>CustomObject</name>
</types>
<version>15.0</version>
</Package>

Note how the standard Account object is retrieved by specifying it as a member of a CustomObject type. However,
standard objects cannot be retrieved by wildcard, they must be specified by name.

33
Declarative Metadata Development Working with the Zip File

The MyCustomField custom field in the MyCustomObject custom object is uniquely identified by its full name,
MyCustomObject__c.MyCustomField__c.
Component Folders
The following table lists a descriptive title for the component, the XML name used in the package.xml file for the metadata
type, the folder the component is retrieved into, whether or not the component may be retrieved with the wildcard (*) symbol
in package.xml, and a short description:

Component XML <name> Metadata Folder * Description

Type
Apex class ApexClass classes yes Use to retrieve or deploy an Apex class. For more
information, see ApexClass on page 63.
Apex trigger ApexTrigger triggers yes Use to retrieve or deploy an Apex trigger. For more
information, see ApexTrigger on page 66.
Custom application CustomApplication applications yes Use to retrieve or deploy an application
component. For more information, see
CustomApplication on page 68.
Custom object or CustomObject objects yes Use to retrieve or deploy both custom and standard
standard object objects. Note that standard objects cannot be
retrieved with the wildcard (*) symbol, but must
be explicitly named in package.xml, and only
custom fields (not standard fields) will be included.
For more information, see CustomObject on page
71.
Custom object CustomObjectTranslation objectTranslations yes Use to retrieve or deploy custom objects
translation translations. For more information, see
CustomObjectTranslation on page 95.
Custom field CustomField objects no Custom fields are retrieved or deployed as part of
a custom object file. You must dot-qualify the
object name before the component name.
Individual custom fields cannot be retrieved with
the wildcard (*) symbol, but must be explicitly
named in package.xml, unless their object is named
in the CustomObject section. For more
information, see CustomField on page 74.
Custom label CustomLabel labels yes Use to retrieve or deploy custom labels that can be
localized for use in different languages, countries,
and currencies. For more information, see
CustomLabels on page 69.
Custom page web CustomPageWebLink weblinks yes Use to retrieve or deploy a Web link that is defined
link in a home page component. For more information,
see CustomPageWebLink on page 100.
Custom site CustomSite sites yes Use to retrieve or deploy custom sites. For more
information, see CustomSite on page 103.
Custom tab CustomTab tabs yes Use to retrieve or deploy a custom tab. For more
information, see CustomTab on page 106.

34
Declarative Metadata Development Working with the Zip File

Component XML <name> Metadata Folder * Description

Type
Dashboard Dashboard dashboards no Use to retrieve or deploy dashboards. For more
information, see Dashboard on page 108.
Document Document document no Use to retrieve or deploy a document. For more
information, see Document on page 114.
Email template EmailTemplate email no Use to retrieve or deploy an email template. For
more information, see EmailTemplate on page
115.
Home page HomePageComponent homePageComponents yes Use to retrieve or deploy a home page component.
component For more information, see HomePageComponent
on page 119.
Home page layout HomePageLayout homePageLayouts yes Use to retrieve or deploy a home page layout. For
more information, see HomePageLayout on page
120.
Page layout Layout layouts yes Use to retrieve or deploy a page layout. For more
information, see Layout on page 121.
Letterhead Letterhead letterhead no Use to retrieve or deploy an email letterhead. For
more information, see Letterhead on page 127.
Picklist Picklist objects no Picklists are retrieved or deployed as part of a
custom object file, in a custom field. You must
dot-qualify the object name before the component
name. For more information, see Picklist on page
81.
Portal Portal portals yes Use to retrieve or deploy a portal. For more
information, see Portal on page 131.
Profile Profile profiles yes Use to retrieve or deploy a profile. Note that the
contents of a profile retrieved depends on the
contents of the organization. For example, profiles
will only include field-level security for fields
included in custom objects returned at the same
time as the profiles. For more information, see
Profile on page 133.
Record type RecordType objects yes Record types are retrieved or deployed as part of
a custom object file. You must dot-qualify the
object name before the component name. For more
information, see RecordType on page 84.
Report Report reports no Use to retrieve or deploy a report. For more
information, see Report on page 140.
Report type ReportType reportTypes no Use to retrieve or deploy a custom report type.
Custom report types allow you to build a
framework from which users can create and
customize reports. For more information, see
ReportType on page 154.

35
Declarative Metadata Development deploy()

Component XML <name> Metadata Folder * Description

Type
Scontrol Scontrol scontrols yes Use to retrieve or deploy an s-control. For more
information, see Scontrol on page 157.
Static resource StaticResource staticResources yes Use to retrieve or deploy a static resource. For
more information, see StaticResource on page 159.
Translation Translations translations yes Use to retrieve or deploy translations. For more
workbench information, see Translations on page 160.
Validation rule ValidationRule objects no Validation rules are retrieved or deployed as part
of a custom object file. You must dot-qualify the
object name before the component name. For more
information, see ValidationRule on page 90.
Visualforce ApexComponent components yes Use to retrieve or deploy a Visualforce component.
component For more information, see ApexComponent on
page 64.
Visualforce page ApexPage pages yes Use to retrieve or deploy a Visualforce page. For
more information, see ApexPage on page 65.
Web link WebLink objects no Web links are retrieved or deployed as part of a
custom object file. You must dot-qualify the object
name before the component name. For more
information, see Weblink on page 91.
Workflow Workflow workflows yes A .workflow file is a container for the individual
workflow components associated with an object,
including WorkflowAlert,
WorkflowFieldUpdate,
WorkflowOutboundMessage,WorkflowRule,
and WorkflowTask. For more information, see
Workflow on page 164.

deploy()
Uses file representations of components to create, update, or delete those components in an organization.

Syntax

AsyncResult = metadatabinding.deploy(base64 zipFile, DeployOptions deployOptions)

Usage
Use this call to take file representations of components and deploy them into an organization by creating, updating, or deleting
the components they represent.
Note: A .zip file can contain a maximum of 1500 files. If you are working with a large number of components, you
should use the listMetadata() call to identify the subset of files that you want to deploy, or you should deploy
batches of components in different .zip files.

36
Declarative Metadata Development deploy()

To deploy (create or update) packaged or unpackaged components:

1. Issue a deploy() call to start the asynchronous deployment. An AsyncResult object is returned. If the call is completed,
the done field contains true. Most often, the call is not completed quickly enough to be noted in the first result. If it is
completed, note the value in the id field returned and skip the next step.
2. If the call is not complete , issue a checkStatus() call in a loop using the value in the id field of the AsyncResult
object returned by the deploy() call in the previous step. Check the AsyncResult object which is returned until the done
field contains true. The time taken to complete a deploy() call depends on the size of the zip file being deployed, so
a longer wait time between iterations should be used as the size of the zip file increases.
3. Issue a checkDeployStatus() call to obtain the results of the deploy() call, using the id value returned in the
first step.
To delete items, use the same procedure but name the manifest file destructiveChanges.xml instead of package.xml.
If you try to delete items that do not exist in an organization, the rest of the deletion will be attempted.

Permissions
Your client application must be logged in with the "Modify All Data" permission.

Sample Code—Java
This sample shows how to deploy components in a zip file. See the retrieve() sample code for details on how to retrieve
a zip file.

package com.doc.samples;

import java.io.*;

import java.rmi.RemoteException;
import javax.xml.rpc.ServiceException;

/**
* Deploy a zip file of metadata components.
* Prerequisite: Have a deploy.zip file that includes a package.xml manifest file that
* details the contents of the zip file.
*/
public class DeploySample {
// binding for the Enterprise WSDL used for login() call
private SoapBindingStub binding;
// binding for the metadata WSDL used for create() and checkStatus() calls
private MetadataBindingStub metadatabinding;

static BufferedReader rdr = new BufferedReader(new InputStreamReader(System.in));

private static final String ZIP_FILE = "deploy.zip";

37
Declarative Metadata Development deploy()

// one second in milliseconds

private static final long ONE_SECOND = 1000;
// maximum number of attempts to deploy the zip file
private static final int MAX_NUM_POLL_REQUESTS = 50;

public static void main(String[] args) throws ServiceException, Exception {

DeploySample sample = new DeploySample();
sample.run();
}

private void run() throws ServiceException, Exception {

if (login()) {
getUserInput("SUCCESSFUL LOGIN! Hit the enter key to continue.");
deployZip();
}
}

private void deployZip()

// Wait for the deploy to complete

if (asyncResult.getState() != AsyncRequestState.Completed) {
throw new Exception(asyncResult.getStatusCode() + " msg: " +
asyncResult.getMessage());
}

DeployResult result = metadatabinding.checkDeployStatus(asyncResult.getId());

if (!result.isSuccess()) {
printErrors(result);
throw new Exception("The files were not successfully deployed");
}

System.out.println("The file " + ZIP_FILE + " was successfully deployed");

}

38
Declarative Metadata Development deploy()

// See the retrieve sample for how to retrieve a zip file.

File deployZip = new File(ZIP_FILE);
if (!deployZip.exists() || !deployZip.isFile())
throw new Exception("Cannot find the zip file to deploy. Looking for " +
deployZip.getAbsolutePath());

FileInputStream fos = new FileInputStream(deployZip);

ByteArrayOutputStream bos = new ByteArrayOutputStream();
int readbyte = -1;
while ((readbyte = fos.read()) != -1) {
bos.write(readbyte);
}
fos.close();
bos.close();
return bos.toByteArray();
}

System.out.println(buf.toString());
}

/**
* The login call is used to obtain a token from Salesforce.

39
Declarative Metadata Development deploy()

* This token must be passed to all other calls to provide

* authentication.
*/
private boolean login() throws ServiceException {
String userName = getUserInput("Enter username: ");
String password = getUserInput("Enter password: ");
/** Next, the sample client application initializes the binding stub.
*
* This is our main interface to the API for the Enterprise WSDL.
* The getSoap method takes an optional parameter,
* (a java.net.URL) which is the endpoint.
* For the login call, the parameter always starts with
* http(s)://www.salesforce.com. After logging in, the sample
* client application changes the endpoint to the one specified
* in the returned loginResult object.
*/
binding = (SoapBindingStub) new SforceServiceLocator().getSoap();

// Time out after a minute

// The LoginFault derives from AxisFault

/** Once the client application has logged in successfully, we use

40
Declarative Metadata Development deploy()

*/
metadatabinding = (MetadataBindingStub)
new MetadataServiceLocator().getMetadata();
metadatabinding._setProperty(MetadataBindingStub.ENDPOINT_ADDRESS_PROPERTY,
loginResult.getMetadataServerUrl());

// return true to indicate that we are logged in, pointed

// at the right url and have our security token in place.
return true;
}

//The sample client application retrieves the user's login credentials.

// Helper function for retrieving user input from the console
String getUserInput(String prompt) {
System.out.print(prompt);
try {
return rdr.readLine();
}
catch (IOException ex) {
return null;
}
}

Arguments

Name Type Description

zipFile base64 Base 64-encoded binary data. Client applications must encode the binary data as base64.
deployOptions DeployOptions Encapsulates options for determining which packages or files are deployed.

DeployOptions
The following deployment options can be selected for this call:

41
Declarative Metadata Development deploy()

Name Type Description

allowMissingFiles boolean
Specifies whether a deploy succeeds even if files that are
specified in package.xml but are not in the .zip file
(true or not false).
Do not set this argument for deployment to production
organizations.

autoUpdatePackage boolean
If a file is in the .zip file but not specified in the
package.xml, specifies whether the file should be
automatically added to the package (true or not false).
A retrieve() is automatically issued with the updated
package.xml that includes the .zip file.
Do not set this argument for deployment to production
organizations.

checkOnly boolean
Indicates whether Apex classes and triggers are saved to
the organization as part of the deployment (false) or
not (true). Any errors or messages that would have been
issued are still generated. This parameter is similar to the
Salesforce Ant tool’s checkOnly parameter.

performRetrieve boolean
Indicates whether a retrieve() call is performed
immediately after the deployment (true) or not (false).
Set to true in order to retrieve whatever was just
deployed.

rollbackOnError boolean
Indicates whether any failure causes a complete rollback
(true) or not (false). If false, whatever set of actions
can be performed without errors are performed, and errors
are returned for the remaining actions. This parameter
must be set to true if you are deploying to a production
organization.

runAllTests boolean
If true, all Apex tests defined in the organization are run.
For deployment to a production organization, all tests are
automatically run regardless of this argument. If any of the
tests fail, the entire deployment will roll back.

runTests string[] A list of Apex tests to be run during deployment. Specify

the class name, one name per instance. The class name
may also specify a namespace with a dot. For example, to
run three tests:

<runTests>positive_test</runTests>
<runTests>negative_test</runTests>
<runTests>namespace.third_test</runTests>

singlePackage boolean Indicates whether the specified .zip file is returned and
the top level of the .zip file structure is skipped (true)

42
Declarative Metadata Development checkDeployStatus()

Name Type Description

or not (false). If false, all packages are deployed at
once and the zip file structure includes a top level directory
for the packages.

Response
AsyncResult

See Also:
retrieve()
describeMetadata()
listMetadata()
checkDeployStatus()

checkDeployStatus()
Checks the status of declarative metadata call deploy().

Syntax

DeployResult = metadatabinding.checkDeployStatus(ID id);

Usage
checkDeployStatus is used as part of the process for deploying packaged or unpackaged components to an organization:
1. Issue a deploy() call to start the asynchronous deployment. An AsyncResult object is returned. If the call is completed,
the done field contains true. Most often, the call is not completed quickly enough to be noted in the first result. If it is
completed, note the value in the id field returned and skip the next step.
2. If the call is not complete , issue a checkStatus() call in a loop using the value in the id field of the AsyncResult
object returned by the deploy() call in the previous step. Check the AsyncResult object which is returned until the done
field contains true. The time taken to complete a deploy() call depends on the size of the zip file being deployed, so
a longer wait time between iterations should be used as the size of the zip file increases.
3. Issue a checkDeployStatus() call to obtain the results of the deploy() call, using the id value returned in the
first step.

Sample Code—Java
See the deploy() sample code for sample usage of this call.

Arguments

Name Type Description

id ID ID obtained from an AsyncResult object returned by deploy() or a subsequent
checkDeployStatus() call.

43
Declarative Metadata Development DeployResult

Response
DeployResult

Name Type Description

id ID ID of the component being deployed.
messages DeployMessage[] Contains information about the success or failure of a deploy() call.
retrieveResult RetrieveResult If the performRetrieve parameter was specified for the deploy(), a
retrieve() is performed immediately after the deploy() is completed. This
field contains the results of that retrieval.
runTestResult RunTestsResult If the runAllTests or runTests parameters are set to run tests, this field contains
the results of those tests.
success boolean Indicates whether the deployment was successful (true) or not (false).

Usage
Contains information about the success or failure of a deploy() call.

DeployMessage
Each DeployResult object contains one or more DeployMessage objects. Each DeployMessage object contains information
about the deployment success or failure of a component in the deployment .zip file:

Name Type Description

changed boolean If true, the component was changed as a result of this deployment. If false,
the deployed component was the same as the corresponding component already in
the organization.
columnNumber int Each component is represented by a text file. If an error occurred during deployment,
this field represents the column of the text file where the error occurred.
created boolean If true, the component was created as a result of this deployment. If false, the
component was either deleted or modified as a result of the deployment.
deleted boolean If true, the component was deleted as a result of this deployment. If false, the
component was either new or modified as result of the deployment.
fileName string The name of the file in the .zip file used to deploy this component.

44
Declarative Metadata Development DeployResult

Name Type Description

fullName string Required. The full name of the component.
Inherited from Metadata, this field is not defined in the WSDL for this metadata
type. It must be specified when creating, updating, or deleting. See create() to
see an example of this field specified for a call.

id ID ID of the component being deployed.

lineNumber int Each component is represented by a text file. If an error occurred during deployment,
this field represents the line number of the text file where the error occurred.
problem string If an error occurred, this field contains a description of the problem that caused the
compile to fail.
success boolean Indicates whether the component was successfully deployed (true) or not (false).

RunTestsResult
The call returns information about whether or not the compilation of the specified Apex was successful and if the unit tests
completed successfully.
A RunTestsResult object has the following properties:

Name Type Description

codeCoverage CodeCoverageResult[]
An array of one or more CodeCoverageResult objects that contains the
details of the code coverage for the specified unit tests.

codeCoverageWarnings CodeCoverageWarning[]
An array of one or more code coverage warnings for the test run. The
results include both the total number of lines that could have been
executed, as well as the number, line, and column positions of code that
was not executed.

failures RunTestFailure[]
An array of one or more RunTestFailure objects that contain information
about the unit test failures, if there are any.

numFailures int
The number of failures for the unit tests.

numTestsRun int
The number of unit tests that were run.

successes RunTestSuccess[]
An array of one or more RunTestSuccesses objects that contain
information about successes, if there are any.

totalTime double
The total cumulative time spent running tests. This can be helpful for
performance monitoring.

CodeCoverageResult
The RunTestsResult object contains this object. It contains information about whether or not the compile of the specified
Apex and run of the unit tests was successful.

45
Declarative Metadata Development DeployResult

Name Type Description

dmlInfo CodeLocation[]
For each class or trigger tested, for each portion of code tested, this property
contains the DML statement locations, the number of times the code was
executed, and the total cumulative time spent in these calls. This can be helpful
for performance monitoring.

id ID
The ID of the CodeLocation. The ID is unique within an organization.

locationsNotCovered CodeLocation[]
For each class or trigger tested, if any code is not covered, the line and column
of the code not tested, and the number of times the code was executed.

methodInfo CodeLocation[]
For each class or trigger tested, the method invocation locations, the number
of times the code was executed, and the total cumulative time spent in these
calls. This can be helpful for performance monitoring.

name string
The name of the class covered.

namespace string
The namespace that contained the unit tests, if one is specified.

numLocations int
The number of locations covered.

soqlInfo CodeLocation[]
For each class or trigger tested, the location of SOQL statements in the code,
the number of times this code was executed, and the total cumulative time
spent in these calls. This can be helpful for performance monitoring.

type string
Deprecated. Do not use. Used to specify class or package in early, unsupported
releases.

CodeCoverageWarning
The RunTestsResult object contains this object. It contains information about the Apex class which generated warnings.
This object has the following properties:

Name Type Description

id ID The ID of the CodeLocation. The ID is unique within an organization.
message string
The message of the warning generated.

name string
The namespace that contained the unit tests, if one is specified.

namespace string
The namespace that contained the unit tests, if one is specified.

RunTestFailure
The RunTestsResult object returns information about failures during the unit test run.

46
Declarative Metadata Development DeployResult

This object has the following properties:

Name Type Description

id ID
The ID of the class which generated failures.

message string
The failure message.

methodName string
The name of the method that failed.

name string
The name of the class that failed.

namespace string
The namespace that contained the class, if one was specified.

stackTrace string
The stack trace for the failure.

time double
The time spent running tests for this failed operation. This can be helpful for
performance monitoring.

type string
Deprecated. Do not use. Used to specify class or package in early, unsupported
releases.

RunTestSuccess
The RunTestsResult object returns information about successes during the unit test run.
This object has the following properties:

Name Type Description

id ID
The ID of the class which generated the success.

methodName string
The name of the method that succeeded.

name string
The name of the class that succeeded.

namespace string
The namespace that contained the unit tests, if one is specified.

time double
The time spent running tests for this operation. This can be helpful for
performance monitoring.

CodeLocation
The RunTestsResult object contains this object in a number of fields.
This object has the following properties:

47
Declarative Metadata Development retrieve()

Name Type Description

column int
The column location of the Apex tested.

line int
The line location of the Apex tested.

numExecutions int
The number of times the Apex was executed in the test run.

time double
The total cumulative time spent at this location. This can be helpful for
performance monitoring.

retrieve()
This call retrieves XML file representations of components in an organization.

Syntax

AsyncResult = metadatabinding.retrieve(RetrieveRequest retrieveRequest)

Usage
Use this call to retrieve file representations of components in an organization.
Note: A .zip file can contain a maximum of 1500 files. If you are working with a large number of components, you
should use the listMetadata() call to identify the subset of files that you want to retrieve, or you should retrieve
batches of components in different .zip files.

To retrieve packaged or unpackaged components:

1. Issue a retrieve() call to start the asynchronous retrieval. An AsyncResult object is returned. If the call is completed,
the done field contains true. Most often, the call is not completed quickly enough to be noted in the result. If it is
completed, note the value in the id field returned and skip the next step.
2. If the call is not complete, issue a checkStatus() call in a loop using the value in the id field of the AsyncResult object
returned by the retrieve() call in the previous step. Check the AsyncResult object returned, until the done field
contains true. The time taken to complete a retrieve() call depends on the size of the zip file being deployed, so a
longer wait time between iterations should be used as the size of the zip file increases.
3. Issue a checkRetrieveStatus() call to obtain the results of the retrieve() call, using the id value returned in
the first step.

Permissions
Your client application must be logged in with the "Modify All Data" permission.

Sample Code—Java
This sample shows how to retrieve components into a zip file. See the deploy() sample code for details on how to deploy
a zip file.

48
Declarative Metadata Development retrieve()

Note: This sample was created using Apache Axis. The WSDL2Java utility generates a _package class, even though
the metadata type is defined as Package in the Metadata WSDL. Other SOAP clients may generate a different
name for the _package class.

package com.doc.samples;

import java.io.*;
import java.util.*;
import java.nio.ByteBuffer;
import java.nio.channels.Channels;
import java.nio.channels.FileChannel;
import java.nio.channels.ReadableByteChannel;
import java.nio.channels.WritableByteChannel;

import java.rmi.RemoteException;
import javax.xml.rpc.ServiceException;

import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.ParserConfigurationException;

import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.xml.sax.SAXException;

import com.sforce.soap.enterprise.LoginResult;
import com.sforce.soap.enterprise.SessionHeader;
import com.sforce.soap.enterprise.SforceServiceLocator;
import com.sforce.soap.enterprise.SoapBindingStub;
import com.sforce.soap.enterprise.fault.ExceptionCode;
import com.sforce.soap.enterprise.fault.LoginFault;

import com.sforce.soap._2006._04.metadata.MetadataBindingStub;
import com.sforce.soap._2006._04.metadata.MetadataServiceLocator;
import com.sforce.soap._2006._04.metadata.AsyncResult;
import com.sforce.soap._2006._04.metadata.RetrieveRequest;
import com.sforce.soap._2006._04.metadata.AsyncRequestState;
import com.sforce.soap._2006._04.metadata.RetrieveResult;
import com.sforce.soap._2006._04.metadata.RetrieveMessage;
// Note that Axis generates a _package class, even though it is defined as Package
// in the WSDL. Other SOAP clients may generate a different name for the _package class.
import com.sforce.soap._2006._04.metadata._package;
import com.sforce.soap._2006._04.metadata.PackageTypeMembers;

public class RetrieveSample {

// binding for the Enterprise WSDL used for login() call
private SoapBindingStub binding;
// binding for the metadata WSDL used for create() and checkStatus() calls
private MetadataBindingStub metadatabinding;

static BufferedReader rdr = new BufferedReader(new InputStreamReader(System.in));

// one second in milliseconds

private static final long ONE_SECOND = 1000;
// maximum number of attempts to retrieve the results
private static final int MAX_NUM_POLL_REQUESTS = 50;

// manifest file that controls which components get retrieved

private static final String MANIFEST_FILE = "package.xml";

private static final double API_VERSION = 15.0;

public static void main(String[] args) throws ServiceException, Exception {

RetrieveSample sample = new RetrieveSample();

49
Declarative Metadata Development retrieve()

sample.run();
}

private void run() throws ServiceException, Exception {

if (login()) {
getUserInput("SUCCESSFUL LOGIN! Hit the enter key to continue.");
retrieveZip();
}
}

private void retrieveZip() throws RemoteException, Exception

{
RetrieveRequest retrieveRequest = new RetrieveRequest();
retrieveRequest.setApiVersion(API_VERSION);
setUnpackaged(retrieveRequest);

AsyncResult asyncResult = metadatabinding.retrieve(retrieveRequest);

if (asyncResult.getState() != AsyncRequestState.Completed) {
throw new Exception(asyncResult.getStatusCode() + " msg: " +
asyncResult.getMessage());
}

RetrieveResult result = metadatabinding.checkRetrieveStatus(asyncResult.getId());

// Print out any warning messages

// Write the zip to the file system

System.out.println("Writing results to zip file");
ByteArrayInputStream bais = new ByteArrayInputStream(result.getZipFile());
File resultsFile = new File("retrieveResults.zip");
FileOutputStream os = new FileOutputStream(resultsFile);
try {
ReadableByteChannel src = Channels.newChannel(bais);
FileChannel dest = os.getChannel();
copy(src, dest);

System.out.println("Results written to " + resultsFile.getAbsolutePath());

}
finally {
os.close();

50
Declarative Metadata Development retrieve()

private void setUnpackaged(RetrieveRequest request) throws Exception

private _package parsePackage(File file) throws Exception {

51
Declarative Metadata Development retrieve()

// Time out after a minute

// The LoginFault derives from AxisFault

52
Declarative Metadata Development retrieve()

System.out.println("An unexpected error has occurred: " + ex.getMessage());

ex.printStackTrace();
return false;
}
// Check if the password has expired
if (loginResult.isPasswordExpired()) {
System.out.println("An error has occurred. Your password has expired.");
return false;
}

/** Once the client application has logged in successfully, we use

// return true to indicate that we are logged in, pointed

// at the right url and have our security token in place.
return true;
}

//The sample client application retrieves the user's login credentials.

// Helper function for retrieving user input from the console
String getUserInput(String prompt) {
System.out.print(prompt);
try {
return rdr.readLine();
}
catch (IOException ex) {
return null;
}
}

53
Declarative Metadata Development checkRetrieveStatus()

Arguments

Name Type Description

retrieveRequest RetrieveRequest Encapsulates options for determining which packages or files are retrieved.

Response
AsyncResult

See Also:
deploy()
describeMetadata()
listMetadata()
RetrieveResult

checkRetrieveStatus()
Checks the status of declarative metadata call retrieve() and returns the zip file contents.

Syntax

RetrieveResult = metadatabinding.checkRetrieveStatus(ID id);

Usage
checkRetrieveStatus is part of the procedure for retrieving metadata components from an organization. It is used
together with the checkStatus call which indicates when the asynchronous retrieve call has completed. Once
checkStatus indicates that the call is completed, call checkRetrieveStatus to get the zip file contents:
1. Issue a retrieve() call to start the asynchronous retrieval. An AsyncResult object is returned. If the call is completed,
the done field contains true. Most often, the call is not completed quickly enough to be noted in the result. If it is
completed, note the value in the id field returned and skip the next step.
2. If the call is not complete, issue a checkStatus() call in a loop using the value in the id field of the AsyncResult object
returned by the retrieve() call in the previous step. Check the AsyncResult object returned, until the done field
contains true. The time taken to complete a retrieve() call depends on the size of the zip file being deployed, so a
longer wait time between iterations should be used as the size of the zip file increases.
3. Issue a checkRetrieveStatus() call to obtain the results of the retrieve() call, using the id value returned in
the first step.

Sample Code—Java
See the retrieve() sample code for sample usage of this call.

54
Declarative Metadata Development RetrieveRequest

Arguments

Name Type Description

id ID ID obtained from a RetrieveResult object returned by a retrieve() call or a subsequent
AsyncResult object returned by a checkStatus() call.

Response
RetrieveResult

Name Type Description

apiVersion double Required. The SOAP version for the retrieve request.
packageNames string One or more package names to be retrieved. If you are
retrieving only unpackaged components, do not specify a
name here. You can retrieve packaged and unpackaged
components in the same retrieve.
singlePackage boolean Specifies whether only a single package is being retrieved
(true) or not (false). If false, then more than one
package is being retrieved.
specificFiles string One or more file names to be retrieved. If a value is
specified for this property, packageNames must be set
to null and singlePackage must be set to true.
unpackaged Package A list of components to retrieve that are not in a package.

Package
This extension of Metadata is specified in a RetrieveRequest as part of a retrieve() call. Use it to specify metadata
components to be retrieved.

Name Type Description

apiAccessLevel APIAccessLevel (enumeration Package components have access via dynamic Apex and
of type string) the API to standard and custom objects in the organization
where they are installed. Administrators who install
packages may wish to restrict this access after installation
for improved security. The valid values are:
• Unrestricted—Package components have the same API
access to standard objects as the user who is logged in
when the component sends a request to the API.

55
Declarative Metadata Development RetrieveRequest

Name Type Description

• Restricted—The administrator can select which
standard objects the components can access. Further,
the components in restricted packages can only access
custom objects in the current package if the user profile
provides access to them.
For more information, see "About API and Dynamic Apex
Access in Packages" in the Salesforce online help.

description string A short description of the package.

fullName string The package developer name used as a unique identifier
for API access. The fullName can only contain characters,
letters, and the underscore (_) character, must start with
a letter, and cannot end with an underscore or contain two
consecutive underscore characters. This field is inherited
from the Metadata component.
namespacePrefix string The namespace of the developer organization where the
package was created.
objectPermissions ProfileObjectPermissions[] Indicates which objects are accessible to the package, and
the kind of access available (create, read, update, delete).
setupWeblink string The weblink used to describe package installation.
types PackageTypeMembers[] A PackageTypeMembers object for each type of
component being retrieved.
version string Required. The version of the component type.

PackageTypeMembers
This object is specified in a Package component as part of a retrieve() call. Each PackageTypeMembers contains the
following arguments:

Name Type Description

members string
One or more named components, or the wildcard character
(*) to retrieve all custom metadata components of the type
specified in the <name> element. To retrieve a standard
object, specify it by name. For example
<members>Account</members> will retrieve the
standard Account object.

name string
The type of metadata component to be retrieved. For
example <name>CustomObject</name> will retrieve
one or more custom objects as specified in the
<members> element.

56
Declarative Metadata Development RetrieveResult

RetrieveResult
The metadata call retrieve() returns a RetrieveResult object, which contains information about the success or failure of
the associated retrieve() call.
Each RetrieveResult object has the following fields:

Name Type Description

fileProperties FileProperties[] Contains information about the properties of each component in the .zip file,
and the manifest file package.xml. One object per component is returned.
id ID ID of the component being retrieved.
messages RetrieveMessage[] Contains information about the success or failure of the retrieve() call.
zipFile base64Binary The zip file returned by the retrieve request. Base 64-encoded binary data. Prior
to making an API call, client applications must encode the binary attachment data
as base64. Upon receiving a response, client applications must decode the base64
data to binary. This conversion is usually handled for you by a SOAP client.

Name Type Description

createdById string Required. ID of the user who created the file.
createdByName string Required. Name of the user who created the file.
createdDate dateTime Required. Date and time when the file was created.
fileName string Required. Name of the file.
fullName string Required. The file developer name used as a unique identifier for API
access. The value is based on the fileName but the characters allowed
are more restrictive. The fullName can only contain characters, letters,
and the underscore (_) character, must start with a letter, and cannot end
with an underscore or contain two consecutive underscore characters.
id string Required. ID of the file.
lastModifiedById string Required. ID of the user who last modified the file.
lastModifiedByName string Required. Name of the user who last modified the file.
lastModifiedDate dateTime Required. Date and time that the file was last modified.

57
Declarative Metadata Development describeMetadata()

Name Type Description

manageableState ManageableState, Indicates the manageable state of the specified component:
(enumeration of type • released
string) • installed
• beta
• unmanaged
• deleted
For more information about states of manageability for components in
Force.com AppExchange packages, see the Salesforce online help.

namespacePrefix string If any, the namespace prefix of the component.

type string Required. The component type. The type should match a component
name, such as CustomObject, CustomField, or Scontrol.

RetrieveMessage
RetrieveResult returns this object, which contains information about the success or failure of the retrieve() call. One
object per problem is returned:

Name Type Description

fileName string The name of the file in the retrieved .zip file where a problem occurred.
problem string A description of the problem that occurred.

describeMetadata()
This call retrieves the metadata which describes your organization. This information includes Apex classes and triggers, custom
objects, custom fields on standard objects, tab sets that define an app, and many other components.

Syntax

DescribeMetadataResult[] = metadatabinding.describeMetadata(double apiVersion);

Arguments

Name Type Description

apiVersion double The API version for which you want metadata; for example 14.0.

Permissions
Your client application must be logged in with the "Modify All Data" permission.

58
Declarative Metadata Development DescribeMetadataResult

Sample Code—Java

private void describeMetadata()

throws Exception
{
try {
double apiVersion = 14.0;
// Assuming that the SOAP binding has already been established.
DescribeMetadataResult res = metadatabinding.describeMetadata(apiVersion);
StringBuffer sb = new StringBuffer();
if (res != null && res.getMetadataObjects().length > 0) {
for (DescribeMetadataObject obj : res.getMetadataObjects()) {
sb.append("***************************************************\n");
sb.append("XMLName: " + obj.getXmlName() + "\n");
sb.append("DirName: " + obj.getDirectoryName() + "\n");
sb.append("Suffix: " + obj.getSuffix() + "\n");
sb.append("***************************************************\n");
}
} else {
sb.append("Failed to obtain metadata types.");
}
System.out.println(sb.toString());
}
catch (Exception ex) {
System.out.println("\nFailed to describe metadata, error message was: \n"
+ ex.getMessage());
throw ex;
}
}

Response
DescribeMetadataResult

See Also:
deploy()
retrieve()
listMetadata()

DescribeMetadataResult
The call describeMetadata() returns information about the organization that is useful for developers working with
declarative metadata.
Each DescribeMetadataResult object has the following properties:

Name Type Description

metadataObjects DescribeMetadataObject[] One or more metadata components and their attributes.
organizationNamespace string The namespace of the organization. Specify only for Developer Edition
organizations that can contain a managed package. The managed package
has a namespace specified when it is created.
partialSaveAllowed boolean Indicates whether rollbackOnError is allowed (true) or not (false).
This value is always :
• false in production organizations.
• the opposite of testRequired.

59
Declarative Metadata Development listMetadata()

Name Type Description

testRequired boolean Indicates whether tests are required (true) or not (false).
This value is always the opposite of partialSaveAllowed.

DescribeMetadataObject
This object is returned as part of the DescribeMetadataResult. Each DescribeMetadataObject has the following properties:

Name Type Description

childXmlNames string[] List of child sub-components for this component.
directoryName string The name of the directory in the .zip file that contains this component.
inFolder boolean Indicates whether the component is in a folder (true) or not (false). For
example, documents, email templates and reports are stored in folders.
metaFile boolean Indicates whether the component requires an accompanying metadata file. For
example, documents, classes, and s-controls are components that require an
additional metadata file.
suffix string The file suffix for this component.
xmlName string The name of the root element in the metadata file for this component. This name
also appears in the Packages > types > name field in the manifest file
package.xml.

listMetadata()
This call retrieves property information about metadata components in your organization. Data is returned for the components
that match the criteria specified in the queries parameter. The queries array can contain up to three ListMetadataQuery
queries for each call. This call supports every component: both top-level, such as CustomObject and ApexClass, and child
types, such as CustomField and RecordType.

Syntax

FileProperties[] = metadatabinding.listMetadata(ListMetadataQuery[] queries);

Usage
This call is useful when you want to identify individual components in package.xml for a retrieve() call or if you want a
high-level view of particular metadata types in your organization. For example, you could use this call to return a list of names
of all the CustomObject or Layout components in your organization, and use this information to make a subsequent
retrieve() call to return a subset of these components. For more information about working with package.xml, see
Declarative Metadata Development on page 32.
Note: This is a synchronous call so the results are returned in one call. This differs from asynchronous calls, such as
retrieve(), where at least one subsequent call is needed to get the results.

60
Declarative Metadata Development ListMetadataQuery

Permissions
Your client application must be logged in with the "Modify All Data" permission.

Sample Code—Java
The sample code below lists information about your custom objects. The code assumes that the SOAP binding has already
been established.

private void listMetadata()

throws Exception
{
try {
String component = "CustomObject";
String optionalFolder = null;
ListMetadataQuery query = new ListMetadataQuery(optionalFolder, component);

// Assuming that the SOAP binding has already been established.

FileProperties[] lmr = metadatabinding.listMetadata(
new ListMetadataQuery[] {query});
if (lmr != null) {
for (FileProperties n : lmr) {
System.out.println("Component fullName: " + n.getFullName());
System.out.println("Component type: " + n.getType());
}
}
}
catch (Exception ex) {
System.out.println("\nFailed to list metadata, error message was: \n"
+ ex.getMessage());
throw ex;
}

Response
FileProperties

See Also:
deploy()
retrieve()
describeMetadata()

ListMetadataQuery
The ListMetadataQuery parameter specified in a listMetadata() call consists of the following properties:

Name Type Description

folder string The folder associated with the component. This field is
required for components that use folders, such as
Dashboard, Document, EmailTemplate, or Report.
type string Required. The component type. The type should match
a component name, such as CustomObject, CustomField,
or Scontrol.

61
Chapter 6
Metadata Components

Metadata components are not based on sObjects, as objects in the API are. Instead, they are based on metadata types, such as ApexClass and
CustomObject, which extend Metadata. A component is an instance of a metadata type.
Metadata components can be manipulated by asynchronous metadata API calls or declarative (or file-based) metadata API calls.
Most of the components can be accessed using Force.com IDE. Exceptions are noted in the description of the object.

Component Field Data Types

Each component field has a specific field type. These field types can correspond to other components defined in the WSDL,
or primitive data types, like string, that are commonly used in strongly typed programming languages.
These field data types are used in the SOAP messages that are exchanged between your client application and the API. When
writing your client application, follow the data typing rules defined for your programming language and development
environment. Your development tool handles the mapping of typed data in your programming language with these SOAP
data types.
For more information about primitive data types, see the Force.com Web Services API Developers Guide.

Enumeration Fields
Some component fields have a data type that is an enumeration. An enumeration is the API equivalent of a picklist. The valid
values of the field are restricted to a strict set of possible values, all having the same data type. These values are listed in the
field description column for each enumeration field. See sortBy for an example of an enumeration field of type string. The
XML below shows a sample definition of an enumeration of type string in the WSDL.

<xsd:simpleType name="DashboardComponentFilter">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="RowLabelAscending"/>
<xsd:enumeration value="RowLabelDescending"/>
<xsd:enumeration value="RowValueAscending"/>
<xsd:enumeration value="RowValueDescending"/>
</xsd:restriction>
</xsd:simpleType>

Supported Calls
All of the metadata types are supported by the main calls, unless it is stated otherwise in the individual component sections.
The main metadata API calls are create(), delete(), update(), deploy(), retrieve(), listMetadata(),

62
Metadata Components ApexClass

and describeMetadata(). All other calls, such as checkStatus(), are considered utility calls as they are used in
conjunction with one of the main calls.

ApexClass
Represents an Apex class. An Apex class is a template or blueprint from which Apex objects are created. Classes consist of
other classes, user-defined methods, variables, exception types, and static initialization code. For more information, see the
Apex Language Reference. This metadata type extends the MetadataWithContent component and shares its fields.

Supported Calls
deploy(), retrieve(), describeMetadata(), listMetadata()
Note: This metadata type is not supported by the create(), delete(), and update() calls.

Declarative Metadata File Suffix and Directory Location

The file suffix is .cls for the class file. The accompanying metadata file is named ClassName-meta.xml.
Apex classes are stored in the classes folder in the corresponding package directory.

Version
Apex classes are available in API version 10.0 and later.

Fields
This metadata type contains the following fields:

Field Name Field Type Description

apiVersion double
The API version for this class. Every class has an API version specified at
creation.

content base64 The Apex class definition. Base 64-encoded binary data. Prior to making
an API call, client applications must encode the binary attachment data as
base64. Upon receiving a response, client applications must decode the
base64 data to binary. This conversion is usually handled for you by a
SOAP client. This field is inherited from the MetadataWithContent
component.
fullName string The Apex class name. The name can only contain characters, letters, and
the underscore (_) character, must start with a letter, and cannot end with
an underscore or contain two consecutive underscore characters. This field
is inherited from the Metadata component.
status ApexCodeUnitStatus
The current status of the Apex class. The following string values are valid:
(enumeration of type string)
• Active - The class is active.
• Deleted - The class is marked for deletion. This is useful for managed
packages, because it allows a class to be deleted when a managed
package is updated.

63
Metadata Components ApexComponent

Field Name Field Type Description

Note: ApexCodeUnitStatus includes an Inactive option, but
it is only supported for ApexTrigger; it is not supported for
ApexClass.

Declarative Metadata Sample Definition

The following sample creates the MyhelloWorld.cls class, and the corresponding MyHelloWorld.cls-meta.xml
metadata file.
MyHelloWorld.cls file:

public class MyHelloWorld {

// This method updates the Hello field on a list
// of accounts.
public static void addHelloWorld(Account[] accs){
for (Account a:accs){
if (a.Hello__c != 'World')
a.Hello__c = 'World';
}
}
}

MyHelloWorld.cls-meta.xml:

<?xml version="1.0" encoding="UTF-8"?>

Declarative Metadata File Suffix and Directory Location

The file suffix is .component for the page file. The accompanying metadata file is named ComponentName-meta.xml.
Visualforce components are stored in the components folder in the corresponding package directory.

Version
Visualforce components are available in API version 12.0 and later.

Fields
This metadata type contains the following fields:

64
Metadata Components ApexPage

Field Name Field Type Description

content base64Binary The component content. Base 64-encoded binary data. Prior to making
an API call, client applications must encode the binary attachment data as
base64. Upon receiving a response, client applications must decode the
base64 data to binary. This conversion is usually handled for you by a
SOAP client. This field is inherited from the MetadataWithContent
component.
description string A description of what the component does.
fullName string The component developer name used as a unique identifier for API access.
The fullName can only contain characters, letters, and the underscore (_)
character, must start with a letter, and cannot end with an underscore or
contain two consecutive underscore characters. This field is inherited from
the Metadata component.
label string Required. The label for this component.

Declarative Metadata File Suffix and Directory Location

The file suffix is .page for the page file. The accompanying metadata file is named PageName-meta.xml.
Visualforce pages are stored in the pages folder in the corresponding package directory.

Version
Visualforce pages are available in API version 11.0 and later.

Fields
This metadata type contains the following fields:

Field Name Field Type Description

apiVersion double Required. The API version for this page. Every page has an API version
specified at creation. This is a new field in API version 13.0.
content base64Binary The page content. Base 64-encoded binary data. Prior to making an API
call, client applications must encode the binary attachment data as base64.
Upon receiving a response, client applications must decode the base64 data
to binary. This conversion is usually handled for you by a SOAP client.
This field is inherited from the MetadataWithContent component.

65
Metadata Components ApexTrigger

Field Name Field Type Description

description string A description of what the page does.
fullName string The page developer name used as a unique identifier for API access. The
fullName can only contain characters, letters, and the underscore (_)
character, must start with a letter, and cannot end with an underscore or
contain two consecutive underscore characters. This field is inherited from
the Metadata component.
label string Required. The label for this page.

Declarative Metadata Sample Definition

The following sample creates the MyPage.page page, and the corresponding MyPage.page-meta.xml metadata file.
SampleApexPage.page file:

<apex:page>
<h1>Congratulations</h1>
This is your new Page.
</apex:page>

SampleApexPage.page-meta.xml:

<?xml version="1.0" encoding="UTF-8"?>

<ApexPage xmlns="http://soap.sforce.com/2006/04/metadata">
<description>This is a sample Visualforce page.</description>
<label>SampleApexPage</label>
</ApexPage>

Declarative Metadata File Suffix and Directory Location

The file suffix is .trigger for the s-control file. The accompanying metadata file is named TriggerName-meta.xml.

66
Metadata Components ApexTrigger

Apex triggers are stored in the triggers folder in the corresponding package directory.

Version
Triggers are available in API version 10.0 and later.

Fields
This metadata type contains the following fields:

Field Name Field Type Description

apiVersion double Required. The API version for this trigger. Every trigger has an API version
specified at creation.
content base64 The Apex trigger definition. This field is inherited from the
MetadataWithContent component.
fullName string The Apex trigger name. The name can only contain characters, letters,
and the underscore (_) character, must start with a letter, and cannot end
with an underscore or contain two consecutive underscore characters. This
field is inherited from the Metadata component.
status ApexCodeUnitStatus Required. The current status of the Apex trigger. The following string
(enumeration of type string) values are valid:
• Active - The trigger is active.
• Inactive - The trigger is inactive, but not deleted.
• Deleted - The trigger is marked for deletion. This is useful for
managed packages, because it allows a trigger to be deleted when a
managed package is updated.

Declarative Metadata Sample Definition

The following sample creates the MyhelloWorld.trigger trigger, and the corresponding MyHelloWorld.trigger-meta.xm
metadata file.
MyHelloWorld.trigger file:

Sample not yet available.

MyHelloWorld.trigger-meta.xml:

<?xml version="1.0" encoding="UTF-8"?>

File Suffix and Directory Location

File suffix: .app
Folder: applications
Note: Retrieving a component of this metadata type in a project makes the component appear in the Profile component
as well.

Version
Custom applications are available in API version 10.0 and later.

Fields
This metadata type contains the following fields:

Field Name Field Type Description

defaultLandingPad string The fullName of a standard tab or custom tab that opens when
this application is selected.
description string The optional description text of the application.
fullName string The internal name of the application, based on the label, but with
white spaces and special characters escaped out for validity. The
fullName can only contain characters, letters, and the underscore
(_) character, must start with a letter, and cannot end with an
underscore or contain two consecutive underscore characters. This
field is inherited from the Metadata component.
label string Required. The name of the application.
logo string The optional reference to the image document for the application.
tab string[] The list of tabs included in this application. In API version 12.0,
the fullName for built-in tabs like Home, Account, and Reports,
is the name of the tab (Home, for example). In API version 13.0
and later, built-in tabs are prefixed with std- For example, to
reference the Account tab you would use std-Account.

Declarative Metadata Sample Definition

The following is the definition of a custom application:

<?xml version="1.0" encoding="UTF-8"?>

<CustomApplication xmlns="http://soap.sforce.com/2006/04/metadata">
<description>App to manage Myriad Publishing</description>
<logo>MyriadFolder/Myriad_Logo.jpg</logo>
<tab>Campaign</tab>

68
Metadata Components CustomDataType

<tab>Lead</tab>
<tab>Account</tab>
<tab>Contact</tab>
<tab>Myriad Publications</tab>
<tab>Document</tab>
<tab>report</tab>
</CustomApplication>

Declarative Metadata File Suffix and Directory Location

Master custom label values are stored in the CustomLabels.labels file. Translations are stored in a file with a name format of
Translation-localeCode.translation, where localeCode is the locale code of the translation language. The supported locale
codes are listed in Language on page 160.
Custom label translations are stored in the labels folder in the corresponding package directory.

Version
CustomLabels components are available in API version 14.0 and later.

Fields

Field Field Type Description

fullName string Required. The name of the custom label bundle.
Inherited from Metadata, this field is not defined in the
WSDL for this metadata type. It must be specified when
creating, updating, or deleting. See create() to see an
example of this field specified for a call.

labels CustomLabel[] A list of custom labels.

69
Metadata Components CustomLabels

CustomLabel
This metadata type represents a custom label. It extends the Metadata metadata type and inherits its fullName field.

Field Field Type Description

categories string A comma-separated list of categories for the label. This
field can be used in filter criteria when creating custom label
list views. Maximum of 255 characters.
fullName string Required. The name of the custom label.
Inherited from Metadata, this field is not defined in the
WSDL for this metadata type. It must be specified when
creating, updating, or deleting. See create() to see an
example of this field specified for a call.

language string Required. The language of the translated custom label.

protected boolean Required. Indicates whether this component is protected
(true) or not (false). Protected components cannot be
linked to or referenced by components created in the
installing organization.
shortDescription string Required. An easily recognizable term to identify this
custom label. This description is used in merge fields.
value string Required. The translated custom label. Maximum of 1000
characters.

Declarative Metadata Sample Definition

A sample XML definition of a custom label component is shown below.

<?xml version="1.0" encoding="UTF-8"?>

<CustomLabels xmlns="http://soap.sforce.com/2006/04/metadata">
<labels>
<fullName>quoteManual</fullName>
<label>This is a manual quote.</label>
<language>en_US</language>
<protected>false</protected>
<shortDescription>Manual Quote</shortDescription>
</labels>
<labels>
<fullName>quoteAuto</fullName>
<label>This is an automatically generated quote.</label>
<language>en_US</language>
<protected>false</protected>
<shortDescription>Automatic Quote</shortDescription>
</labels>
</CustomLabels>

Declarative Metadata File Suffix and Directory Location

Custom object names are automatically appended with __c. The file suffix is .object for the custom object (or standard object)
file.
Custom and standard objects are stored in the objects folder in the corresponding package directory.
Note: Retrieving a component of this metadata type in a project makes the component appear in the Profile component
as well.

Version
Custom objects are available in API version 10.0 and later.

Fields
Unless otherwise noted, all fields are creatable, filterable, and nillable.

Field Name Field Type Description

customHelp string The s-control that contains the help content if this custom
object has customized help content. This is a new field
in API version 14.0.
deploymentStatus DeploymentStatus Indicates the deployment status of the custom object.
(enumeration of type string)
description string A description of the object. Maximum of 1000 characters.
enableActivities boolean Indicates whether the custom object is enabled for
activities (true) or not (false).
enableDivisions boolean Indicates whether the custom object is enabled for
divisions (true) or not (false). For more information
about the Division object, see the Force.com Web Services
API Developer's Guide.
enableEnhancedLookup boolean Indicates whether the custom object is enabled for
enhanced lookups (true) or not (false). Enhanced

71
Metadata Components CustomObject

Field Name Field Type Description

lookups provide an updated lookup dialog interface that
gives users the ability to filter, sort, and page through
search results as well as customize search result columns.
For more information about enhanced lookups, see
"Enabling Enhanced Lookups" in the Salesforce online
help.
enableHistory boolean Indicates whether the custom object is enabled for audit
history (true) or not (false).
enableReports boolean Indicates whether the custom object is enabled for reports
(true) or not (false).
fields CustomField[] Represents one or more fields in the object.
fullName string Inherited from Metadata, this field is not defined in the
WSDL for this metadata type. It must be specified when
creating, updating, or deleting. See create() to see an
example of this field specified for a call.
This value cannot be null.

gender Gender
Gender of the name to support translation for languages
that indicate gender in nouns. Valid values are:
• Neuter
• Masculine
• Feminine

household boolean This field supports relationship groups, a feature available

only with the Salesforce for Wealth Management. For
more information, see "About Salesforce for Wealth
Management" in the Salesforce online help.
label string Label that represents the object throughout the Salesforce
user interface.
listViews ListView[] Represents one or more list views associated with the
object.
nameField CustomField Required. The field that this object's name is stored in.
Every custom object must have a name, usually a string
or autonumber.
Identifier for the custom object record. This name appears
in page layouts, related lists, lookup dialogs, search results,
and key lists on tab home pages. By default, this field is
added to the custom object page layout as a required field.
Every custom object must have a name, usually a string
or autonumber.

pluralLabel string Plural version of the label value.

recordTypes RecordType[] An array of one or more record types defined for this
object.

72
Metadata Components CustomObject

Field Name Field Type Description

searchLayouts SearchLayouts The Search Layouts related list information for a custom
object.
sharingModel SharingModel Indicates the sharing model for this custom object. Valid
values are:
• Private
• Read
• ReadWrite

sharingReasons SharingReason[] The reasons why the custom object is being shared.
sharingRecalculations SharingRecalculation[] A list of custom sharing recalculations associated with
the custom object.
startsWith StartsWith (enumeration of Indicates whether the name starts with a vowel,
type string) consonant, or is a special character. This is used for
languages where words need different treatment
depending on the first character. Valid values are listed
in StartsWith on page 95.
validationRules ValidationRule[] An array of one or more validation rules on this object.
webLinks Weblink[] An array of one or more weblinks defined for the object.

Declarative Metadata Additional Components

CustomObject definitions may include additional components which are defined in the custom object for declarative metadata.
The following components are defined in the CustomObject:
• CustomField
• ListView
• RecordType
• SearchLayouts
• SharingReason
• SharingRecalculation
• ValidationRule
• Weblink

Declarative Metadata Sample Definition

<?xml version="1.0" encoding="UTF-8"?>

<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
<deploymentStatus>Deployed</deploymentStatus>
<description>just a test object with one field for eclipse ide testing</description>
<fields>
<fullName>Comments__c</fullName>
<description>add your comments about this object here</description>
<inlineHelpText>This field contains comments made about this object</inlineHelpText>

<label>Comments</label>
<length>32000</length>
<type>LongTextArea</type>
<visibleLines>30</visibleLines>
</fields>
<label>MyFirstObject</label>

73
Metadata Components CustomField

<nameField>
<label>MyFirstObject Name</label>
<type>Text</type>
</nameField>
<pluralLabel>MyFirstObjects</pluralLabel>
<sharingModel>ReadWrite</sharingModel>
</CustomObject>

See Also:
CustomField
Metadata
Picklist
SearchLayouts
Weblink
CustomObjectTranslation
ListView

CustomField
Represents the metadata associated with a custom field. Use this metadata type to create, update, or delete custom field
definitions. It extends the Metadata metadata type and inherits its fullName field.
You must specify the full name whenever you create or update a custom field. For example, a custom field on a custom object:

MyCustomObject__c.MyCustomField__c

Another example, a custom field on a standard object:

Account.MyAcctCustomField__c

Declarative Metadata File Suffix and Directory Location

Custom fields are defined as part of the custom object or standard object definition. See CustomObject for more information.
Note: Retrieving a component of this metadata type in a project makes the component appear in the Profile component
as well.

Retrieving Custom Fields on Custom or Standard Objects

When you retrieve a custom or standard object, you return everything associated with the object. However, you can also retrieve
only the custom fields for an object by explicitly naming the object and fields in package.xml. The following definition in
package.xml will create the files objects/MyCustomObject__c.object and
objects/Account.object__c.object, each containing one custom field definition.

<types>
<members>MyCustomObject__c.MyCustomField__c</members>
<members>Account.MyCustomAccountField__c</members>
<name>CustomField</name>
</types>

Version
Custom fields are available in API version 10.0 and later.

74
Metadata Components CustomField

Fields
Unless otherwise noted, all fields are creatable, filterable, and nillable.

Field Name Field Type Description

caseSensitive boolean
Indicates whether the field is case sensitive (true) or not
(false).

defaultValue string
If specified, represents the default value of the field.

description string
Description of the field.

displayFormat string
The display format.

externalId boolean
Indicates whether the field is an external ID field (true)
or not (false).

formula string
If specified, represents a formula on the field.

formulaTreatBlankAs TreatBlanksAs
Indicates how to treat blanks in a formula. Valid values are
(enumeration of type
BlankAsBlank and BlankAsZero.
string)
fullName string Inherited from Metadata, this field is not defined in the
WSDL for this metadata type. It must be specified when
creating, updating, or deleting. See create() to see an
example of this field specified for a call.
This value cannot be null.

indexed boolean Indicates if the field is indexed. If this field is unique or

the externalId is set true, the isIndexed value is set
to true. This field has been deprecated as of version 14.0
and is only provided for backward compatibility.
inlineHelpText string Represents the content of field-level help. For more
information, see "Defining Field-Level Help" in the
Salesforce online help.
label string Required. Label for the field.
length int Length of the field.
maskChar EncryptedFieldMaskChar For encrypted fields, specifies the character to be used as
(enumeration of type a mask. Valid values are enumerated in
string) EncryptedFieldMaskChar.
For more information on encrypted fields, see "About
Encrypted Custom Fields" in the Salesforce online help.

maskType EncryptedFieldMaskType For encrypted text fields, specifies the format of the masked
(enumeration of type and unmasked characters in the field. Valid values are
string) enumerated in EncryptedFieldMaskType For more
information on encrypted fields, see "About Encrypted
Custom Fields" in the Salesforce online help.

75
Metadata Components CustomField

Field Name Field Type Description

picklist Picklist If specified, the field is a picklist, and this field enumerates
the picklist values and labels.
populateExistingRows boolean Indicates whether existing rows will be populated (true)
or not (false).
precision int Indicates the precision for number values.
referenceTo string If specified, indicates a reference this field has to another
object.
relationshipLabel string Label for the relationship.
relationshipName string If specified, indicates the value for one-to-many
relationships. For example, in the object MyObject that
had a relationship to YourObject, the relationship name
might be YourObjects.
relationshipOrder int This field is valid for all master-detail relationships, but
the value is only non-zero for junction objects. A junction
object has two master-detail relationships, and is analogous
to an association table in a many-to-many relationship.
Junction objects must define one parent object as primary
(0), the other as secondary (1). The definition of primary
or secondary affects delete behavior and inheritance of look
and feel, and record ownership for junction objects. For
more information, see the Salesforce online help.
0 or 1 are the only valid values, and 0 is always the value
for objects that are not junction objects.

required boolean Indicates whether the field requires a value on creation

(true) or not (false).
scale int Indicates the scale for the field.
startingNumber int If specified, indicates the starting number for the field.
summarizedField string Represents the field on the detail row that is being
summarized. This field cannot be null unless the
summaryOperation value is count.

summaryFilterItems FilterItem[] Represents the set of filter conditions for this field if it is
a summary field. This field will be summed on the child
if the filter conditions are met.
summaryForeignKey string Represents the master-detail field on the child that defines
the relationship between the parent and the child.
summaryOperation SummaryOperations Represents the sum operation to be performed. Valid values
(enumeration of type are enumerated in SummaryOperations.
string)
trackHistory boolean Indicates whether history tracking is enabled for the field
(true) or not (false). For more information, see
"Tracking Field History" in the Salesforce online help.

76
Metadata Components CustomField

Field Name Field Type Description

trueValueIndexed boolean This is only relevant for a checkbox field. If set, true values
are built into the index. This field has been deprecated as
of version 14.0 and is only provided for backward
compatibility.
type FieldType Required. Indicates the field type for the field. Valid values
are enumerated in FieldType.
unique boolean Indicates whether the field is unique (true) or not
(false).
visibleLines int Indicates the number of lines displayed for the field.
writeRequiresMasterRead boolean Sets the minimum sharing access level required on the
master record to create, edit, or delete child records. This
field applies only to master-detail or junction object custom
field types.
• true - Allows users with "Read" access to the master
record permission to create, edit, or delete child records.
This setting makes sharing less restrictive.
• false - Allows users with "Read/Write" access to the
master record permission to create, edit, or delete child
records. This setting is more restrictive than true,
and is the default value.
For junction objects, the most restrictive access from the
two parents is enforced. For example, if you set to true
on both master-detail fields, but users have "Read" access
to one master record and "Read/Write" access to the other
master record, users won't be able to create, edit, or delete
child records.

Custom fields use additional data types. For more information, see Metadata Field Types on page 94.

EncryptedFieldMaskChar
This field type is used in maskChar. It is a string with two valid values: asterisk or X. For more information on encrypted
fields, see About Encrypted Custom Fields in the Salesforce online help.

EncryptedFieldMaskType
This field type is used in maskType. Valid values are:
all
All characters in the field are hidden. This option is equivalent to the Mask All Characters option in Salesforce.

creditCard
The first 12 characters are hidden and the last four display. This option is equivalent to the Credit Card Number
option in Salesforce.

ssn
The first five characters are hidden and the last four display. This option is equivalent to the Social Security Number
option in Salesforce.

77
Metadata Components CustomField

lastFour
All characters are hidden but the last four display. This option is equivalent to the Last Four Characters Clear
option in Salesforce.

sin
All characters are hidden but the last four display. This option is equivalent to the Social Insurance Number option
in Salesforce.

nino
All characters are hidden. Salesforce automatically inserts spaces after each pair of characters if the field contains nine
characters. This option is equivalent to the National Insurance Number option in Salesforce.

For more information on encrypted fields, see About Encrypted Custom Fields in the Salesforce online help.

FilterItem
FilterItem is used in summaryFilterItems. It contains the following properties:

Field Field Type Description

field string
Represents the field specified in the filter.

operation FilterOperation
Represents the filter operation for this filter item. Valid values
(enumeration of
are enumerated in FilterOperation.
type string)
value string
Represents the value of the filter item being operated upon, for
example, if the filter is my_number_field__c > 1, the
value of value is 1.

FilterOperation
This is an enumeration of type string that lists different filter operations. Valid values are:
• equals
• notEqual
• lessThan
• greaterThan
• lessOrEqual
• greaterOrEqual
• contains
• notContain
• startsWith
• includes
• excludes

SummaryOperations
Represents the type of a summaryOperation. Valid values are:
• Count
• Min

78
Metadata Components ListView

• Max
• Sum

Java Sample
The following Java sample illustrates how to specify a picklist and set of values:

Picklist picklist = new Picklist();

picklist.setPicklistValues(new PicklistValue[]
{ new PicklistValue("Hot", false), PicklistValue("Not hot", true) });
picklist.setSorted(false);

Declarative Metadata Sample Definition

<?xml version="1.0" encoding="UTF-8"?>

<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
....
<fields>
<fullName>Comments__c</fullName>
<description>add your comments about this object here</description>
<inlineHelpText>This field contains comments made about this object</inlineHelpText>

<label>Comments</label>
<length>32000</length>
<type>LongTextArea</type>
<visibleLines>30</visibleLines>
</fields>
....
</CustomObject>

See Also:
CustomObject
Picklist
Metadata

ListView
List views allow you to see a filtered list of custom objects. For more information, see "Creating Custom List Views" in the
Salesforce online help. It extends the Metadata metadata type and inherits its fullName field.
Note: The ListView component only supports list views for custom objects. It does not support list views for standard
objects, such as accounts or contacts.

Declarative Metadata File Suffix and Directory Location

List views are stored within a custom object. For more details, see CustomObject on page 71.

Version
ListView components are available in API version 14.0 and later.

79
Metadata Components ListView

Fields

Field Field Type Description

booleanFilter string This field represents an Advanced Option for a filter.
Advanced Options in filters allow you to build up filtering
conditions that use a mixture of AND and OR boolean
operators across multiple filter line items. For example, (1
AND 2) OR 3 finds records that match both the first two
filter line items or the third. For more information, see
"Working with Advanced Filter Conditions" in the
Salesforce online help.
columns string[] The list of fields in the list view. The field name relative to
the custom object name, for example MyCustomField__c,
is specified for each custom field.
filterScope FilterScope (enumeration of Required. This field indicates whether you are filtering by
type string) owner or viewing all records.
filters ListViewFilter[] The list of filter line items.
fullName string Required. Inherited from Metadata, this field is not defined
in the WSDL for this metadata type. It must be specified
when creating, updating, or deleting. See create() to
see an example of this field specified for a call.
label string Required. The list view name.
queue string The name of a queue. Objects are sometimes assigned to a
queue so that the users who have access to the queue can
monitor and manage them. When you create a queue, a
corresponding list view is automatically created. For more
information, see "Setting Up Queues" in the Salesforce
online help.

ListViewFilter
ListViewFilter represents a filter line item.

Field Field Type Description

filter string Required. Represents the field specified in the filter.
operation FilterOperation (enumeration Required. The operation used by the filter, such as equals.
of type string) The valid values are listed in FilterOperation.
value string
Represents the value of the filter item being operated upon,
for example, if the filter is my_number_field__c >
1, the value of value is 1.

FilterScope
This is an enumeration of type string that represents the filtering criteria for the records. The valid values are listed in the table
below:

80
Metadata Components Picklist

Enumeration Value Description

Everything All records, for example All Opportunities.
Mine Records owned by the user running the list view, for example My Opportunities.
Queue Records assigned to a queue.

Declarative Metadata Sample Definition

A sample XML definition of a list view in a custom object is shown below.

<?xml version="1.0" encoding="UTF-8"?>

<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
. . .
<listViews>
<fullName>All_Mileages</fullName>
<filterScope>all</filterScope>
<label>All Mileages</label>
</listViews>
<listViews>
<fullName>My_Mileages</fullName>
<booleanFilter>1 AND 2</booleanFilter>
<columns>NAME</columns>
<columns>CREATED_DATE</columns>
<filterScope>mine</filterScope>
<filters>
<field>NAME</field>
<operation>equals</operation>
<value>Eric Bristow</value>
</filters>
<filters>
<field>City__c</field>
<operation>equals</operation>
<value>Paris</value>
</filters>
<label>My Mileages</label>
</listViews>
. . .
</CustomObject>

Declarative Metadata File Suffix and Directory Location

Picklist definitions are included in the custom object and field with which they are associated.

81
Metadata Components Picklist

Fields
Picklist contains the following fields:

Field Name Field Type Description

controllingField string The fullName of the controlling field if this is a dependent picklist.
A dependent picklist works in conjunction with a controlling picklist
or checkbox to filter the available options. The value chosen in the
controlling field affects the values available in the dependent field.
This field is available in API version 14.0 and later.
picklistValues PicklistValue[]
Required. Represents a set of values for a picklist.

sorted boolean
Required. Indicates whether values should be sorted (true), or
not (false).

PicklistValue
This metadata type defines a value in the picklist and specifies whether this value is the default value. It extends the Metadata
metadata type and inherits its fullName field.

Field Name Field Type Description

controllingFieldValues string[] A list of values in the controlling field that are linked to this picklist
value. The controlling field can be a checkbox or a picklist. This
field is available in API version 14.0 and later. The values in the
list depend on the field type:
• Checkbox: checked or unchecked.
• Picklist: The fullName of the picklist value in the
controlling field.

fullName string Character value for this picklist.

default boolean Required. Indicates whether this value is the default picklist value
in the specified picklist (true), or not (false).

Java Sample
The following sample uses a picklist. For a complete sample of using a picklist with record types and profiles, see Profile on
page 133.

// Create a picklist
Picklist expenseStatus = new Picklist();
PicklistValue unsubmitted = new PicklistValue();
unsubmitted.setFullName("Unsubmitted");
PicklistValue submitted = new PicklistValue();
submitted.setFullName("Submitted");
PicklistValue approved = new PicklistValue();
approved.setFullName("Approved");
PicklistValue rejected = new PicklistValue();
rejected.setFullName("Rejected");
expenseStatus.setPicklistValues(new PicklistValue[] {unsubmitted, submitted, approved,
rejected});

CustomField expenseStatusField = new CustomField();

82
Metadata Components Picklist

expenseStatusField.setFullName("ExpenseReport__c.ExpenseStatus__c");
expenseStatusField.setLabel("Expense Report Status");
expenseStatusField.setType(FieldType.Picklist);
expenseStatusField.setPicklist(expenseStatus);
create(expenseStatusField);

Declarative Metadata Sample Definition

The following sample shows usage for picklists, including dependent picklists, in a custom object. The isAmerican__c
checkbox controls the list of manufacturers shown in the manufacturer__c picklist. The manufacturer__c checkbox in
turn controls the list of models shown in the model__c picklist.

<?xml version="1.0" encoding="UTF-8"?>

<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
<deploymentStatus>Deployed</deploymentStatus>
<enableActivities>true</enableActivities>
<fields>
<fullName>isAmerican__c</fullName>
<defaultValue>false</defaultValue>
<label>American Only</label>
<type>Checkbox</type>
</fields>
<fields>
<fullName>manufacturer__c</fullName>
<label>Manufacturer</label>
<picklist>
<controllingField>isAmerican__c</controllingField>
<picklistValues>
<fullName>Chrysler</fullName>
<controllingFieldValues>checked</controllingFieldValues>
<default>false</default>
</picklistValues>
<picklistValues>
<fullName>Ford</fullName>
<controllingFieldValues>checked</controllingFieldValues>
<default>false</default>
</picklistValues>
<picklistValues>
<fullName>Honda</fullName>
<controllingFieldValues>unchecked</controllingFieldValues>
<default>false</default>
</picklistValues>
<picklistValues>
<fullName>Toyota</fullName>
<controllingFieldValues>unchecked</controllingFieldValues>
<default>false</default>
</picklistValues>
<sorted>false</sorted>
</picklist>
<type>Picklist</type>
</fields>
<fields>
<fullName>model__c</fullName>
<label>Model</label>
<picklist>
<controllingField>manufacturer__c</controllingField>
<picklistValues>
<fullName>Mustang</fullName>
<controllingFieldValues>Ford</controllingFieldValues>
<default>false</default>
</picklistValues>
<picklistValues>
<fullName>Taurus</fullName>
<controllingFieldValues>Ford</controllingFieldValues>
<default>false</default>
</picklistValues>

83
Metadata Components RecordType

<picklistValues>
<fullName>PT Cruiser</fullName>
<controllingFieldValues>Chrysler</controllingFieldValues>
<default>false</default>
</picklistValues>
<picklistValues>
<fullName>Pacifica</fullName>
<controllingFieldValues>Chrysler</controllingFieldValues>
<default>false</default>
</picklistValues>
<picklistValues>
<fullName>Accord</fullName>
<controllingFieldValues>Honda</controllingFieldValues>
<default>false</default>
</picklistValues>
<picklistValues>
<fullName>Civic</fullName>
<controllingFieldValues>Honda</controllingFieldValues>
<default>false</default>
</picklistValues>
<picklistValues>
<fullName>Prius</fullName>
<controllingFieldValues>Toyota</controllingFieldValues>
<default>false</default>
</picklistValues>
<picklistValues>
<fullName>Camry</fullName>
<controllingFieldValues>Toyota</controllingFieldValues>
<default>false</default>
</picklistValues>
<sorted>false</sorted>
</picklist>
<type>Picklist</type>
</fields>
....
</CustomObject>

RecordType
Represents the metadata associated with a record type. Record types allow you to offer different business processes, picklist
values, and page layouts to different users based on their profiles. For more information, see "Managing Record Types" in the
Salesforce online help. Use this metadata type to create, update, or delete record type definitions for a custom object. It extends
the Metadata metadata type and inherits its fullName field.
Note: Retrieving a component of this metadata type in a project makes the component appear in the Profile component
as well.

Version
Record types are available in API version 12.0 and later.

Fields

Field Field Type Description

active boolean Required. Indicates whether or not the record type is active.
description string Record type description. Maximum of 255 characters.

84
Metadata Components RecordType

Field Field Type Description

fullName string Record type name. The fullName can only contain characters, letters,
and the underscore (_) character, must start with a letter, and cannot
end with an underscore or contain two consecutive underscore
characters. If this field contained characters before version 14.0 that
are no longer allowed, the characters were stripped out of this field,
and the previous value of the field was saved in the label field.
Inherited from the Metadata component, this field is not defined
in the WSDL for this component. It must be specified when
creating, updating, or deleting. See create() to see an example
of this field specified for a call.
This value cannot be null.

label string Required. Descriptive label for the record type. The list of characters
allowed in the fullName field has been reduced for versions 14.0
and later. This field contains the value contained in the fullName
field before version 14.0.
picklistValues RecordTypePicklistValue[] Represents a set of values for a picklist.

RecordTypePicklistValue
RecordTypePicklistValue represents the combination of picklists and valid values that define a record type:

Field Name Field Type Description

picklist string Required. The name of the picklist.
values PicklistValue One or more of the picklist values in the picklist. Each value defined
is available in the record type that contains this component.

Java Sample
The following sample uses two record types. For the complete sample the includes profiles and picklists, see Profile on page
133.

// Employees and managers have different access to the state of the expense sheet
RecordType edit = new RecordType();
edit.setFullName("ExpenseReport__c.Edit");
RecordTypePicklistValue editStatuses = new RecordTypePicklistValue();
editStatuses.setPicklist("ExpenseStatus__c");
editStatuses.setValues(new PicklistValue[] {unsubmitted, submitted});
edit.setPicklistValues(new RecordTypePicklistValue[] {editStatuses});
create(edit);

RecordType approve = new RecordType();

approve.setFullName("ExpenseReport__c.Approve");
RecordTypePicklistValue approveStatuses = new RecordTypePicklistValue();
approveStatuses.setPicklist("ExpenseStatus__c");
approveStatuses.setValues(new PicklistValue[] {approved, rejected});
approve.setPicklistValues(new RecordTypePicklistValue[] {approveStatuses});
create(approve);

85
Metadata Components SearchLayouts

Declarative Metadata Sample Definition

The definition of a record type in a custom object is shown below:

<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
. . .
<recordTypes>
<fullName>My First Recordtype</fullName>
</recordTypes>
. . .
</CustomObject>

SearchLayouts
Represents the metadata associated with the Search Layouts related list for a custom object. You can customize which custom
object fields display for users in search results, in lookup dialogs, and in the key lists on custom tab home pages. For more
information, see "Customizing Search Layouts for Custom Objects" in the Salesforce online help.

Version
Search layouts are available in API version 14.0 and later.

Fields

Field Field Type Description

customTabListAdditionalFields string[] The list of fields displayed in the Recent Custom
Object Name list view on a custom tab associated with
the custom object. The name field is mandatory and is
always displayed as the first column header, so it is not
included in this list; all additional fields are included.
The field name relative to the custom object name, for
example MyCustomField__c, is specified for each
custom field.
excludedStandardButtons string[] The list of standard buttons excluded from the search
layout.
listViewButtons string[] The list of buttons available in list views for the custom
object.
This field is equivalent to the Buttons Displayed value
in the Custom Object Name List View in the
Search Layouts related list on the custom object detail
page in the Salesforce user interface. For more
information, see "Lookup Dialog Search" in the
Salesforce online help.

lookupDialogsAdditionalFields string[] The list of fields displayed in a lookup dialog for the
custom object. The name field is mandatory and is always
displayed as the first column header, so it is not included
in this list; all additional fields are included. The field
name relative to the custom object name, for example
MyCustomField__c, is specified for each custom field.

86
Metadata Components SearchLayouts

Field Field Type Description

Salesforce objects often include one or more lookup fields
that allow users to associate two records together in a
relationship. For example, a contact record includes an
Account lookup field that represents the relationship
between the contact and the organization with which
the contact is associated. A lookup search dialog helps
you search for the record associated with the one being
edited. Lookup filter fields allow you to filter your lookup
search by a customized list of fields in the custom object.
This field is equivalent to the Lookup Dialogs in the
Search Layouts related list on the custom object detail
page in the application user interface. For more
information, see "Lookup Dialog Search" in the
Salesforce online help.

lookupFilterFields string[] The list of fields that can be used to filter enhanced
lookups for the custom object. Enhanced lookups are
optionally enabled by your administrator. The field name
relative to the custom object name, for example
MyCustomField__c, is specified for each custom field.

This field is equivalent to the Lookup Filter Fields

in the Search Layouts related list on the custom object
detail page in the application user interface. For more
information, see "Lookup Dialog Search" in the
Salesforce online help.

lookupPhoneDialogsAdditionalFields string[] The list of phone-related fields displayed in a lookup

dialog for the custom object. The name field is
mandatory and is always displayed as the first column
header, so it is not included in this list; all additional
fields are included. The field name relative to the custom
object name, for example MyCustomField__c, is
specified for each custom field.
This list enables integration of the fields with a
SoftPhone dial pad. For more information, see "About
SoftPhones" in the Salesforce online help.
This field is equivalent to the Lookup Phone Dialogs
in the Search Layouts related list on the custom object
detail page in the application user interface.

searchFilterFields string[] The list of fields that can be used to filter a search for
the custom object. The field name relative to the custom
object name, for example MyCustomField__c, is
specified for each custom field.
This field is equivalent to the Search Filter Fields
in the Search Layouts related list on the custom object
detail page in the application user interface.

87
Metadata Components SharingReason

Field Field Type Description

searchResultsAdditionalFields string[] The list of fields displayed in a search result for the
custom object. The name field is mandatory and is always
displayed as the first column header, so it is not included
in this list; all additional fields are included. The field
name relative to the custom object name, for example
MyCustomField__c, is specified for each custom field.

This field is equivalent to the Search Results in the

Search Layouts related list on the custom object detail
page in the application user interface.

searchResultsCustomButtons string[] The list of custom buttons available in a search result

for the custom object. The actions associated with the
buttons can be applied to any of the records returned in
the search result.

Declarative Metadata Sample Definition

A sample definition of search layouts in a custom object is shown below.

<?xml version="1.0" encoding="UTF-8"?>

<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
. . .
<searchLayouts>
<listViewButtons>New</listViewButtons>
<listViewButtons>Accept</listViewButtons>
<listViewButtons>ChangeOwner</listViewButtons>
<lookupDialogsAdditionalFields>firstQuote__c</lookupDialogsAdditionalFields>
<lookupDialogsAdditionalFields>finalQuote__c</lookupDialogsAdditionalFields>
<searchResultsAdditionalFields>CREATEDBY_USER</searchResultsAdditionalFields>
</searchLayouts>
. . .
</CustomObject>

Field Field Type Description

fullName string Required. Sharing reason name. The __c suffix is appended to
custom sharing reasons.
Inherited from Metadata, this field is not defined in the WSDL for
this metadata type. It must be specified when creating, updating,
or deleting. See create() to see an example of this field specified
for a call.

label string Required. Descriptive label for the sharing reason. Maximum of 40
characters.

Declarative Metadata Sample Definition

The definition of a sharing reason in a custom object:

<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
. . .
<sharingReasons>
<fullName>recruiter__c</fullName>
<label>Recruiter</label>
</sharingReasons>
. . .
</CustomObject>

SharingRecalculation
Developers can write Apex classes that recalculate the Apex managed sharing for a specific custom object. For more information,
see "Recalculating Apex Managed Sharing" in the Salesforce online help.

Version
Sharing recalculations are available in API version 14.0 and later.

Fields

Field Field Type Description

className string Required. The Apex class that recalculates the Apex sharing for a
custom object. This class must implement the
Database.Batchable interface.

Declarative Metadata Sample Definition

The definition of a sharing recalculation in a custom object:

<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
. . .
<sharingRecalculations>
<className>RecruiterRecalculation</className>
</sharingRecalculations>

89
Metadata Components ValidationRule

. . .
</CustomObject>

ValidationRule
Represents a validation rule, which is used to verify that the data a user enters in a record is valid and can be saved. A validation
rule contains a formula or expression that evaluates the data in one or more fields and returns a value of true or false.
Validation rules also include an error message that your client application can display to the user when the rule returns a value
of true due to invalid data. It extends the Metadata metadata type and inherits its fullName field.

Version
Validation rules are available in API version 12.0 and later.

Fields

Field Name Field Type Description

active boolean Required. Indicates whether this validation rule is active, (true),
or not active (false).
description string A description of the validation rule.
errorConditionFormula string Required. The validation formula, as documented in the validation
formula page. See Defining Validation Rules in the Salesforce online
help.
errorDisplayField string The fully specified name of a field in the application. If a value is
supplied in this field, the value in errorMessage appears next
to the specified field. If you do not specify a value, the error message
appears at the top of the page.
errorMessage string Required. The message that appears if the validation rule fails. The
message must be 255 characters or less.
fullName string
The internal name of the validation rule, with white spaces and
special characters escaped for validity. The name can only contain
characters, letters, and the underscore (_) character, must start with
a letter, and cannot end with an underscore or contain two
consecutive underscore characters.
Inherited from the Metadata component, this field is not defined
in the WSDL for this component. It must be specified when
creating, updating, or deleting. See create() to see an example
of this field specified for a call.

Declarative Metadata Sample Definition

A sample XML definition of a validation rule in a custom object is shown below.

<?xml version="1.0" encoding="UTF-8"?>

<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
<deploymentStatus>Deployed</deploymentStatus>
<fields>
<fullName>Mommy_Cat__c</fullName>
<label>Mommy Cat</label>

90
Metadata Components Weblink

<referenceTo>Cat__c</referenceTo>
<relationshipName>Cats</relationshipName>
<type>Lookup</type>
</fields>
<label>Cat</label>
<nameField>
<label>Cat Name</label>
<type>Text</type>
</nameField>
<pluralLabel>Cats</pluralLabel>
<sharingModel>ReadWrite</sharingModel>
<validationRules>
<fullName>CatsRule</fullName>
<active>true</active>
<errorConditionFormula>OR(Name = 'Milo',Name =
'Moop')</errorConditionFormula>
<validationMessage>Name must be that of one of my cats</validationMessage>
</validationRules>
</CustomObject>

Weblink
Represents a Weblink defined in a custom object. It extends the Metadata metadata type and inherits its fullName field.

Version
Weblinks are available in API version 12.0 and later.

Fields
The Weblink definition contains the following fields.

Field Name Field Type Description

availability WebLinkAvailability Required. Indicates whether the Weblink is only available online
(enumeration of type string) (online, or if it is also available offline (offline).
description string A description of the Weblink.
displayType WebLinkDisplayType Represents how this Weblink is rendered.
(enumeration of type string)
Valid values:
• link for a hyperlink
• button for a button
• massAction for a button attached to a related list

fullName string The name of the weblink with white spaces and special characters
escaped for validity. The name can only contain characters, letters,
and the underscore (_) character, must start with a letter, and cannot
end with an underscore or contain two consecutive underscore
characters.
Inherited from the Metadata component, this field is not defined
in the WSDL for this component. It must be specified when creating,
updating, or deleting. See create() to see an example of this field
specified for a call.

91
Metadata Components Weblink

Field Name Field Type Description

hasMenubar boolean If the openType is newWindow, whether to show the browser
menu bar for the window (true or not (false). Otherwise this
field should not be specified.
hasScrollbars boolean If the openType is newWindow, whether to show the scroll bars
for the window (true) or not (false). Otherwise this field should
not be specified.
hasToolbar boolean If the openType is newWindow, whether to show the browser
toolbar for the window (true) or not (false). Otherwise this field
should not be specified.
height int Height in pixels of the window opened by this Weblink. Required
if the openType is newWindow, otherwise should not be specified
isResizable boolean If the openType is newWindow, whether to allow resizing of the
window (true) or not (false). Otherwise this field should not
be specified.
linkType WebLinkType (enumeration Required. Represents whether the content of this Weblink is
of type string) specified by a URL, an sControl, a JavaScript code block, or a
Visualforce page.
Valid values:
• url
• sControl
• javascript
• page

masterLabel string The master label for the Weblink.

openType WebLinkWindowType Required. When this button is clicked, specifies the window style
(enumeration of type string) that will be used to display the content.
Valid values:
• newWindow
• sidebar
• noSidebar
• replace
• onClickJavaScript

page string If the value of linkType is page, this field represents the
Visualforce page; otherwise, this field should not be specified.
position WebLinkPosition If the openType is newWindow, how the new window should be
(enumeration of type string) displayed. Otherwise this field should not be specified.
Valid values:
• fullScreen
• none
• topLeft

92
Metadata Components Weblink

Field Name Field Type Description

protected boolean Required. Indicates whether this sub-component is protected (true)
or not (false). Protected sub-components cannot be linked to or
referenced by components or sub-components created in the
installing organization.
requireRowSelection boolean If the openType is massAction, whether to require individual
row selection to execute the action for this button (true) or not
(false). Otherwise this field should not be specified.
scontrol string If the value of linkType is sControl, this field represents the
name of the sControl; otherwise, this field should not be specified.
showsLocation boolean If the openType is newWindow, whether or not to show the
browser location bar for the window; otherwise this field should not
be specified.
showsStatus boolean If the openType is newWindow, whether or not to show the
browser status bar for the window. Otherwise, this field should not
be specified.
url string
If the value of linkType is url, this is the URL value. If the value
of linkType is javascript, this is the JavaScript content. If the
value neither of these, the this field should not be specified.
Content must be escaped in a manner consistent with XML parsing
rules.

width int Width in pixels of the window opened by this Weblink.

Required if the openType is newWindow, otherwise should not be
specified.

Java Sample

Weblink weblink = new Weblink();

weblink.setFullName("googleButton");
weblink.setUrl("http://www.google.com");
weblink.setAvailability(WebLinkAvailability.online);
weblink.setLinktype(WebLinkType.url);
weblink.setOpentype(WebLinkWindowType.newWindow);
weblink.setHeight(600);
weblink.setWidth(600);
weblink.setShowsLocation(false);
weblink.setHasScrollbars(true);
weblink.setHasToolbar(false);
weblink.setHasMenubar(false);
weblink.setShowsStatus(false);
weblink.setIsResizable(true);
weblink.setPosition(WebLinkPosition.none);
weblink.setMasterLabel("google");
weblink.setDisplayType(WebLinkDisplayType.link);
weblink.setRequireRowSelection(true);

93
Metadata Components Metadata Field Types

Declarative Metadata Sample Definition

The following is the definition of a Weblink in a custom object. For related samples, see HomePageComponent on page 120
and HomePageLayout on page 121.

<?xml version="1.0" encoding="UTF-8"?>

<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
....
<webLinks>
<fullName>detailPageButton</fullName>
<availability>online</availability>
<displayType>button</displayType>
<hasScrollbars>true</hasScrollbars>
<height>600</height>
<isResizable>true</isResizable>
<linkType>url</linkType>
<masterLabel>detailPageButon</masterLabel>
<openType>newWindow</openType>
<position>none</position>
<protected>false</protected>
<url>http://google.com</url>
</webLinks>
....
</CustomObject>

See Also:
HomePageComponent
HomePageLayout
CustomPageWebLink

Metadata Field Types

These field types extend the field types described in the Force.com Web Services API Developer's Guide.

Field Type Objects What the Field Contains

CustomField Custom object Represents a custom field.
Custom field

DeploymentStatus Custom object

A string which represents the deployment status of a custom object or field. Valid values
Custom field are:
• InDevelopment
• Deployed

FieldType Custom field Indicates the type of a custom field. Valid values are:
• AutoNumber
• Lookup
• MasterDetail
• Checkbox
• Currency
• Date
• DateTime
• Email

94
Metadata Components CustomObjectTranslation

Field Type Objects What the Field Contains

• EncryptedText
• Number
• Percent
• Phone
• Picklist
• MultiselectPicklist
• Summary
• Text
• TextArea
• LongTextArea
• Summary
• Url

Gender Custom object

Gender of the name to support translation for languages that indicate gender in nouns.
Valid values are:
• Neuter
• Masculine
• Feminine

Picklist Custom field Represents a picklist, a set of labels and values that can be selected from a picklist.
SharingModel Custom object Represents the sharing model for the custom object or custom field. Valid values are:
Custom field • Private
• Read
• ReadWrite

StartsWith Custom object Indicates whether the name starts with a vowel, consonant, or is a special character.
This is used for languages where words need different treatment depending on the first
Custom field
character. Valid values are:
• Consonant
• Vowel
• Special

TreatBlanksAs Custom field Indicates how blanks should be treated. Valid values are:
• BlankAsBlank
• BlankAsZero

CustomObjectTranslation
This metadata type allows you to translate custom objects for a variety of languages. It extends the Metadata metadata type
and inherits its fullName field. The ability to translate component labels is part of the Translation Workbench. For more
information, see "Setting Up Translation Workbench" in the Salesforce online help.

95
Metadata Components CustomObjectTranslation

Declarative Metadata File Suffix and Directory Location

Translations are stored in a file with a format of customObjectName__c-lang.objectTranslation, where
customObjectName__c is the custom object name, and lang is the translation language. A sample file name for German
translations is myCustomObject__c-de.objectTranslation.
Custom object translations are stored in the objectTranslations folder in the corresponding package directory.

Version
CustomObjectTranslation components are available in API version 14.0 and later.

Fields

Field Field Type Description

caseValues ObjectNameCaseValue[] Different combinations of the custom object with the
definite and indefinite articles, and for the singular and
plural cases.
fields CustomFieldTranslation[] A list of translations for the custom fields associated with
the custom object.
fullName string The name of the custom object and the translation language
with a format of customObjectName-lang, where
customObjectName is the custom object name, and lang
is the translation language.
Inherited from Metadata, this field is not defined in the
WSDL for this metadata type. It must be specified when
creating, updating, or deleting. See create() to see an
example of this field specified for a call.

gender Gender
Gender of the name to support translation for languages
that indicate gender in nouns. Valid values are:
• Neuter
• Masculine
• Feminine

layouts LayoutTranslation[] A list of page layout translations.

nameFieldLabel string The label for the name field. Maximum of 765 characters.
recordTypes RecordTypeTranslation[] A list of record type translations.
sharingReasons SharingReasonTranslation[] A list of sharing reason translations.
startsWith StartsWith (enumeration of Indicates whether the name starts with a vowel, consonant,
type string) or is a special character. This is used for languages where
words need different treatment depending on the first
character. Valid values are listed in StartsWith on page 95.
validationRules ValidationRuleTranslation[] A list of validation rule translations.
webLinks WebLinkTranslation[] A list of web link translations.

96
Metadata Components CustomObjectTranslation

CustomFieldTranslation
CustomFieldTranslation contains details for a custom field translation. For more details, see CustomField on page 74.

Field Field Type Description

description string Translation for the custom field description.
help string Translation for the text that displays in the field-level help
hover text for this field.
label string Translation for the label. Maximum of 765 characters.
name string Required. The name of the field relative to the custom
object; for example, MyField__c.
picklistValues PicklistValueTranslation[] List of translations for picklist values. See PicklistValue on
page 82 for more details.
relationshipLabel string Translation for a lookup relationship label. A lookup
relationship allows a field to be associated with another
field. The relationship field allows users to select an option
from a list of values defined by the other field. Maximum
of 765 characters.

LayoutTranslation
LayoutTranslation contains details for a page layout translation. For more details, see Fields on page 122.

Field Field Type Description

layout string Required. The layout name.
sections LayoutSectionTranslation[] An array of layout section translations.

LayoutSectionTranslation
LayoutSectionTranslation contains details for a page layout section translation. For more details, see LayoutSection on page
123.

Field Field Type Description

label string Required. Translation for the label. Maximum of 765
characters.
section string Required. The section name.

ObjectNameCaseValue
ObjectNameCaseValue supports multiple cases and definitions of the custom object name to allow usage in various grammatical
contexts.

Field Field Type Description

article Article (enumeration of type English has two types of articles: definite (the) and
string) indefinite (a, an). The usage of these articles depends
mainly on whether you are referring to any member of a

97
Metadata Components CustomObjectTranslation

Field Field Type Description

group, or to a specific member of a group. The valid values
are:
• Definite
• Indefinite
• None

caseType CaseType (enumeration of The case of the custom object name. The valid values are:
type string) • Ablative
• Accusative
• Adessive
• Allative
• Causalfinal
• Dative
• Delative
• Distributive
• Elative
• Essive
• Essiveformal
• Genitive
• Illative
• Inessive
• Instrumental
• Locative
• Nominative
• Objective
• Partitive
• Prepositional
• Subjective
• Sublative
• Superessive
• Termanative
• Translative
• Vocative

plural boolean Indicates whether the value field is plural (true) or

singular (false).
possessive Possessive (enumeration of The possessive case of a language is a grammatical case used
type string) to indicate a relationship of possession.The valid values are:
• First
• None
• Second

value string Required. The value or label in this grammatical context.

98
Metadata Components CustomObjectTranslation

PicklistValueTranslation
PicklistValueTranslation contains details for a picklist value translation. For more details, see Picklist on page 81.

Field Field Type Description

masterLabel string Required. The picklist value defined on the setup page in
the application is your master label. The master label is
displayed wherever a translated label is not available.
translation string Required. Translation for the value.

RecordTypeTranslation
RecordTypeTranslation contains details for a record type name translation. For more details, see RecordType on page 84.

Field Field Type Description

label string Required. Translation for the label. Maximum of 765
characters.
name string Required. The record type name.

SharingReasonTranslation
SharingReasonTranslation contains details for a sharing reason translation. For more details, see SharingReason on page 88.

Field Field Type Description

label string Required. Translation for the sharing reason.
name string Required. The sharing reason name.

ValidationRuleTranslation
ValidationRuleTranslation contains details for a validation rule translation. For more details, see ValidationRule on page 90.

Field Field Type Description

errorMessage string Required. Translation for the error message associated with
the validation rule failure.
name string Required. The validation rule name.

WebLinkTranslation
WebLinkTranslation contains details for a web link translation. For more details, see Weblink on page 91.

Field Field Type Description

label string Required. Translation for the web link label. Maximum of
765 characters.
name string Required. The web link name.

99
Metadata Components CustomPageWebLink

Declarative Metadata Sample Definition

A sample XML definition of a custom object translation is shown below.

<?xml version="1.0" encoding="UTF-8"?>

<CustomObjectTranslation xmlns="http://soap.sforce.com/2006/04/metadata">
<fields>
<fullName>Description__c</fullName>
<label>description</label>
</fields>
<gender>Feminine</gender>
<nameFieldLabel>citation</nameFieldLabel>
<objectNames>
<article>None</article>
<value>description</value>
</objectNames>
<objectNames>
<article>Indefinite</article>
<value>une description</value>
</objectNames>
<objectNames>
<article>Definite</article>
<value>la description</value>
</objectNames>
<objectNames>
<article>None</article>
<plural>true</plural>
<value>descriptions </value>
</objectNames>
<objectNames>
<article>Definite</article>
<plural>true</plural>
<value>les descriptions</value>
</objectNames>
<startsWith>Consonant</startsWith>
</CustomObjectTranslation>

Declarative Metadata File Suffix and Directory Location

There is one file per web link definition, stored in the weblinks folder in the corresponding package directory. The file suffix
is .weblink.

Version
CustomPageWebLinks are available in API version 13.0 and later.

100
Metadata Components CustomPageWebLink

Fields
The CustomPageWebLink definition has the following fields:

Field Name Field Type Description

fullName string The name used as a unique identifier for API access. The fullName
can only contain characters, letters, and the underscore (_) character,
must start with a letter, and cannot end with an underscore or contain
two consecutive underscore characters.
hasMenubar boolean If the openType is newWindow, whether to show the browser
menu bar for the window (true or not (false). Otherwise this
field should not be specified.
hasScrollbars boolean If the openType is newWindow, whether to show the scroll bars
for the window (true) or not (false). Otherwise this field should
not be specified.
hasToolbar boolean If the openType is newWindow, whether to show the browser
toolbar for the window (true) or not (false). Otherwise this field
should not be specified.
height int Height in pixels of the window opened by this Weblink. Required
if the openType is newWindow, otherwise should not be specified
isResizable boolean If the openType is newWindow, whether to allow resizing of the
window (true) or not (false). Otherwise this field should not
be specified.
linkType WebLinkType (enumeration Required. Represents whether the content of this Weblink is
of type string) specified by a URL, an sControl, or by a JavaScript code block.
Valid values:
• url
• sControl
• javascript
• page

masterLabel string The master label for the Weblink.

openType WebLinkWindowType Required. When this button is clicked, specifies the window style
(enumeration of type string) that will be used to display the content.
Valid values:

101
Metadata Components CustomPageWebLink

Field Name Field Type Description

• newWindow
• sidebar
• noSidebar
• replace
• onClickJavaScript

protected boolean Required. Indicates whether this component is protected (true) or

not (false). Protected components cannot be linked to or
referenced by components created in the installing organization.
requireRowSelection boolean If the openType is massAction, whether to require individual
row selection to execute the action for this button (true) or not
(false). Otherwise this field should not be specified.
scontrol string If the value of linkType is sControl, this field represents the
name of the sControl; otherwise, this field should not be specified.
showsLocation boolean If the openType is newWindow, whether or not to show the
browser location bar for the window; otherwise this field should not
be specified.
showsStatus boolean If the openType is newWindow, whether or not to show the
browser status bar for the window. Otherwise, this field should not
be specified.
url string
If the value of linkType is url, this is the URL value. If the value
of linkType is javascript, this is the JavaScript content. If the
value neither of these, the this field should not be specified.
Content must be escaped in a manner consistent with XML parsing
rules.

width int Width in pixels of the window opened by this Weblink.

Required if the openType is newWindow, otherwise should not be
specified.

Java Sample

Weblink weblink = new Weblink();

weblink.setFullName("googleButton");
weblink.setUrl("http://www.google.com");
weblink.setAvailability(WebLinkAvailability.online);

102
Metadata Components CustomSite

weblink.setLinktype(WebLinkType.url);
weblink.setOpentype(WebLinkWindowType.newWindow);
weblink.setHeight(600);
weblink.setWidth(600);
weblink.setShowsLocation(false);
weblink.setHasScrollbars(true);
weblink.setHasToolbar(false);
weblink.setHasMenubar(false);
weblink.setShowsStatus(false);
weblink.setIsResizable(true);
weblink.setPosition(WebLinkPosition.none);
weblink.setMasterLabel("google");
weblink.setDisplayType(WebLinkDisplayType.link);
weblink.setRequireRowSelection(true);

Declarative Metadata Sample Definition

The following is the definition of a Weblink. For related samples, see HomePageComponent on page 120 and HomePageLayout
on page 121.

<?xml version="1.0" encoding="UTF-8"?>

<CustomPageWebLink xmlns="http://soap.sforce.com/2006/04/metadata">
<availability>online</availability>
<displayType>button</displayType>
<hasMenubar>false</hasMenubar>
<hasScrollbars>true</hasScrollbars>
<hasToolbar>false</hasToolbar>
<height>600</height>
<isResizable>true</isResizable>
<linkType>url</linkType>
<masterLabel>detailPageButon</masterLabel>
<openType>newWindow</openType>
<position>none</position>
<protected>false</protected>
<showsLocation>false</showsLocation>
<showsStatus>false</showsStatus>
<url>http://google.com</url>
</CustomPageWebLink>

See Also:
HomePageComponent
HomePageLayout
Weblink

CustomSite
Force.com Sites enables you to create public websites and applications that are directly integrated with your Salesforce
organization—without requiring users to log in with a username and password. For more information, see "About Force.com
Sites" in the Salesforce online help.
Note: CustomSite does not support syndication feeds at this time.

103
Metadata Components CustomSite

Declarative Metadata File Suffix and Directory Location

Force.com CustomSite components are stored in the sites directory of the corresponding package directory. The file name
matches the site name, and the extension is .site.

Version
Force.com CustomSite components are available in API version 14.0 and later.

Fields

Field Field Type Description

active boolean Required. Determines whether or not the site is active.
allowHomePage boolean Determines whether or not the standard home page is visible
to public users. This is a new field in API version 15.0.
allowStandardIdeasPages boolean Determines whether or not the standard Salesforce CRM
Ideas pages are visible to public users. This is a new field in
API version 15.0.
allowStandardLookups boolean Determines whether or not the standard lookup pages are
visible to public users. This is a new field in API version
15.0.
allowStandardSearch boolean Determines whether or not the standard search pages are
visible to public users. This is a new field in API version
15.0.
authorizationRequiredPage string The name of the Visualforce page to be displayed when the
guest user tries to access a page for which they are not
authorized.
bandwidthExceededPage string The name of the Visualforce page to be displayed when the
site has exceeded its bandwidth quota.
changePasswordPage string The name of the Visualforce page to be displayed when the
portal user attempts to change his or her password.
customWebAddress string The custom top-level domain name associated with the site.
description string The site description.
fileNotFoundPage string The name of the Visualforce page to be displayed when the
guest user tries to access a non-existent page.
genericErrorPage string The name of the Visualforce page to be displayed for errors
not otherwise specified.
guestProfile string Read only. The name of the profile associated with the guest
user.
inMaintenancePage string The name of the Visualforce page to be displayed when the
site is down for maintenance
inactiveIndexPage string The name of the Visualforce page set as the inactive site
home page.
indexPage string The name of the Visualforce page set as the active site home
page.

104
Metadata Components CustomSite

Field Field Type Description

masterLabel string The name of the site label in the Salesforce user interface.
portal string The name of the portal associated with this site for login
access.
requireInsecurePortalAccess string Required. Determines whether to override your
organization's security settings and exclusively use HTTP
when logging in to the associated portal from your site.
robotsTxtPage string The name of the Visualforce page to be displayed for the
robots.txt file used by web crawlers
siteAdmin string The username of the site administrator.
siteTemplate string The name of the Visualforce page to be used as the site
template.
subdomain string Required. Read only. The custom subdomain prefix for the
site. For example, if your site URL is
mycompany.force.com/partners, mycompany.force.com is
the subdomain.
urlPathPrefix string The first part of the path on the site's URL that
distinguishes this site from other sites. For example, if your
site URL is mycompany.force.com/partners, partners is the
urlPathPrefix.

Declarative Metadata Sample Definition

A sample XML definition of a site is shown below.

<?xml version="1.0" encoding="UTF-8"?>

<CustomSite xmlns="http://soap.sforce.com/2006/04/metadata">
<active>false</active>
<authorizationRequiredPage>Unauthorized</authorizationRequiredPage>
<bandwidthExceededPage>BandwidthExceeded</bandwidthExceededPage>
<changePasswordPage>ChangePassword</changePasswordPage>
<customWebAddress>partners.myco.org</customWebAddress >
<fileNotFoundPage>FileNotFound</fileNotFoundPage>
<genericErrorPage>Exception</genericErrorPage>
<inMaintenancePage>InMaintenance</inMaintenancePage>
<indexPage>IdeasHome</indexPage>
<masterLabel>customSite</masterLabel>
<requireInsecurePortalAccess>true</requireInsecurePortalAccess>
<siteAdmin>admin@myco.org </siteAdmin>
<siteTemplate>SiteTemplate</siteTemplate>
<subdomain>myco</subdomain>
<urlPathPrefix>partners</urlPathPrefix>
</CustomSite>

File Suffix and Directory Location

The file suffix is .tab. There is one file for each tab, stored in the tabs folder in the corresponding package directory.
Note: Retrieving a component of this metadata type in a project makes the component appear in the Profile component
as well.

Version
Tabs are available in API version 10.0 and later.

Fields
This metadata type contains the following fields:

Field Name Field Type Description

customObject boolean Indicates whether this tab is for a custom object (true) or not
(false). If set to true, the name of the tab matches the name
of the custom object.
Only one of these fields should have a value set:
• customObject
• page
• scontrol
• url

description string The optional description text for the tab.

frameHeight int The height, in pixels of the tab frame. Required for s-control and
page tabs.
fullName string The name of the tab. The value of this field depends on the type
of tab, and the API version.
• For custom object tabs, the fullName is the developer-assigned
name of the custom object (MyCustomObject__c, for example).
For custom object tabs, this name must be the same as the
custom object name, and customObject should be set to true.
• For Web tabs, the fullName is the developer-assigned name
of the tab (MyWebTab, for example).
The fullName can only contain characters, letters, and the
underscore (_) character, must start with a letter, and cannot end
with an underscore or contain two consecutive underscore characters.
This field is inherited from the Metadata component.

106
Metadata Components CustomTab

Field Name Field Type Description

hasSidebar boolean Indicates if the tab displays the sidebar panel.
icon string The optional reference to the image document for the tab if the tab
is not using one of the standard tab styles. This is a new field in
API version 14.0.
label string This is the label of the tab, for Web tabs only.
mobileReady boolean Required. Indicates if the custom tab is available for Mobile Edition
(true) or not (false).
motif string Required. The tab style for the color scheme and icon for the custom
tab. For example, "'Custom70: Handsaw," is the handsaw icon.
page string The name of the Visualforce page to display in this tab.
Only one of these fields should have a value set:
• customObject
• page
• scontrol
• url

scontrol string The name of the s-control to display in this tab.

Only one of these fields should have a value set:
• customObject
• page
• scontrol
• url

splashPageLink string The custom link used as the introductory splash page when users
click the tab. References a HomePageComponent.
url string The URL for the external web-page to embed in this tab.
Only one of these fields should have a value set:
• customObject
• page
• scontrol
• url

urlEncodingKey Encoding The default encoding setting is Unicode: UTF-8. Change it if you
(enumeration of are passing information to a URL that requires data in a different
type string) format. This option is available when the value URL is selected in
the tab type.

Declarative Metadata Sample Definition

The following is the definition of a tab:

<?xml version="1.0" encoding="UTF-8"?>

<CustomTab xmlns="http://soap.sforce.com/2006/04/metadata">
<description>Myriad Publishing</description>
<frameHeight>600</frameHeight>

107
Metadata Components Dashboard

<mobileReady>true</mobileReady>
<motif>Custom53: Bell</motif>
<url>http://www.myriadpubs.com</url>
<urlEncodingKey>UTF-8</urlEncodingKey>
</CustomTab>

Declarative Metadata File Suffix and Directory Location

Dashboards are stored in the dashboards directory of the corresponding package directory. The file name matches the dashboard
title and the extension is .dashboard.

Version
Dashboard components are available in API version 14.0 and later.

Fields

Field Field Type Description

backgroundEndColor string Required. A dashboard can have a gradient color change
on its charts. This field defines the second color for the
gradient and backgroundStartColor defines the first
color. If you prefer your background to be all one color or
do not want a gradient color change, select the same color
for this field and backgroundStartColor. The color is
in hexadecimal format; for example #FF6600.
backgroundFadeDirection ChartBackgroundDirection Required. The direction of the gradient color change,
(enumeration of type string) defined by the backgroundStartColor and
backgroundEndColor fields. The valid values are:
• diagonal
• leftToRight
• topToBottom

backgroundStartColor string Required. The starting color for the gradient color change
on the dashboard's charts. See backgroundEndColor for
more information. The color is in hexadecimal format; for
example #FF6600.
description string Description for the dashboard. Maximum of 255 characters.
fullName string Inherited from Metadata, this field is not defined in the
WSDL for this metadata type. It must be specified when

108
Metadata Components Dashboard

Field Field Type Description

creating, updating, or deleting. See create() to see an
example of this field specified for a call.
This field specifies the folder and dashboard title; for
example folderSales/California.

leftSection DashboardComponentSection Required. The left section or column of the dashboard.

middleSection DashboardComponentSection The middle section or column of the dashboard.
rightSection DashboardComponentSection Required. The right section or column of the dashboard.
runningUser string The username of the user whose role and sharing settings
are used to determine the data shown in the dashboard.
When you deploy a dashboard and the value in this field is
not defined or does not correspond to a valid user, the field
is populated with the username of the user performing the
deployment.
Regardless of their security settings, all users viewing a
dashboard see exactly the same data, because dashboards
are always run using the security settings of a particular user.
Tip: To avoid inappropriate exposure of sensitive
data, save the dashboard to a folder that is visible
only to appropriate users.

textColor string Required. Color of the text on each chart in the dashboard.
The color is in hexadecimal format; for example #FF6600.
title string Required. The dashboard title.
titleColor string Required. Color of the titles on each dashboard component.
The color is in hexadecimal format; for example #FF6600.
titleSize int Required. Size of characters in title text. For example, a
value of 12 indicates 12pt text.

DashboardComponentSection
DashboardComponentSection represents one of the sections or columns in a dashboard.

Field Field Type Description

columnSize DashboardComponentSize Required. The size of the column in the dashboard. See
(enumeration of type string) DashboardComponentSize for details on valid values.
components DashboardComponent[] The list of DashboardComponent objects in the dashboard
column.

DashboardComponentSize
DashboardComponentSize is an enumeration of type string that lists different size categories. The valid values are listed in
the table below:

109
Metadata Components Dashboard

Enumeration Value Description

medium Medium component size.
narrow Smallest component size.
wide Largest component size.

DashboardComponent
A dashboard consists of a group of different components or elements that display data. Each component can use a custom
report or a custom s-control as their data source to display corporate metrics or key performance indicators. You can create
several dashboard components and display them all in one dashboard aligned in up to three columns.

Field Field Type Description

chartAxisRange ChartRangeType A manual or automatic axis range for bar or line charts. The
(enumeration of type string) valid values are:
• auto
• manual

chartAxisRangeMax double The maximum axis range to be displayed. This only applies
to bar and line charts in which the manual axis range is
selected for the chartAxisRange field.
chartAxisRangeMin double The minimum axis range to be displayed. This only applies
to bar and line charts in which the manual axis range is
selected for the chartAxisRange field.
componentType DashboardComponentType Required. Dashboard component type. The valid values
(enumeration of type string) are:
• Bar
• BarGrouped
• BarStacked
• BarStacked100
• Column
• ColumnGrouped
• ColumnStacked
• ColumnStacked100
• gauge
• Line
• lineCumulative
• LineGrouped
• lineGroupedCumulative
• Metric
• Pie
• Scontrol
• Table

displayUnits ChartUnits (enumeration of Chart Units. The valid values are:

type string) • Auto
• Integer

110
Metadata Components Dashboard

Field Field Type Description

• Hundreds
• Thousands
• Millions
• Billions
• Trillions

drillDownUrl string If the component is a chart, you can embed a URL other
than the source report to allow users to click the dashboard
component and drill down to another dashboard, report,
record detail page, or another system that uses a web
interface.
footer string Footer displayed at the bottom of the dashboard component.
Maximum of 255 characters.
gaugeMax double The maximum value on a gauge. A gauge is used to see how
far you are from reaching a goal. It looks like a speedometer
in a car.
gaugeMin double The minimum value on a gauge.
header string Header displayed at the top of the dashboard component.
Maximum of 80 characters.
indicatorBreakpoint1 double The value that separates the indicatorLowColor from
the indicatorMiddleColor on the dashboard.
indicatorBreakpoint2 double The value that separates the indicatorMiddleColor
from the indicatorHighColor on the dashboard.
indicatorHighColor string The color representing a high number range on the gauge.
indicatorLowColor string The color representing a low number range on the gauge.
indicatorMiddleColor string The color representing a medium number range on the
gauge.
legendPosition ChartLegendPosition
The location of the legend with respect to the chart. The
(enumeration of type string)
valid values are:
• LEGEND_NONE
• LEGEND_RIGHT
• LEGEND_BOTTOM

maxValuesDisplayed int The maximum number of elements to include in the

top-level grouping of the horizontal axis of a horizontal
chart, vertical axis of a vertical chart, or selected axis of a
stacked bar chart. For example, if you want to list only your
top five salespeople, create an opportunity report that lists
total opportunity amounts by owner and enter 5 in this
field.
metricLabel string Descriptive label for the metric. This is relevant if metric
is the value of the componentType field.

111
Metadata Components Dashboard

Field Field Type Description

report string Name of the report associated with the component.
scontrol string S-control associated with component if scontrol is the
value of the componentType field. For more information,
see "Defining Custom S-Controls" in the Salesforce online
help.
scontrolHeightInPixels int Display height of the s-control.
sortBy DashboardComponentFilter Sort option for the dashboard component. The valid values
(enumeration of type string) are:
• RowLabelAscending
• RowLabelDescending
• RowValueAscending
• RowValueDescending

title string The title of the dashboard component. Maximum of 40

characters.

Declarative Metadata Sample Definition

A sample XML definition of a dashboard is shown below. The file name matches the dashboard title and the extension is
.dashboard.

<?xml version="1.0" encoding="UTF-8"?>

<Dashboard xmlns="http://soap.sforce.com/2006/04/metadata">
<backgroundEndColor>#FFFFFF</backgroundEndColor>
<backgroundFadeDirection>diagonal</backgroundFadeDirection>
<backgroundStartColor>#FFFFFF</backgroundStartColor>
<leftColumnSize>medium</leftColumnSize>
<leftComponents>
<chartAxisRange>auto</chartAxisRange>
<componentType>column</componentType>
<report>reportFolder/TPS_Report</report>
<displayUnits>auto</displayUnits>
<footer>chart</footer>
<header>chart</header>
<maxValuesDisplayed>5</maxValuesDisplayed>
<sortBy>rowLabelAscending</sortBy>
<title>chart</title>
</leftComponents>
<leftComponents>
<chartAxisRange>manual</chartAxisRange>
<chartAxisRangeMax>100.0</chartAxisRangeMax>
<chartAxisRangeMin>0.0</chartAxisRangeMin>
<componentType>column</componentType>
<report>reportFolder/TPS_Report</report>
<displayUnits>auto</displayUnits>
<footer>chart manual</footer>
<header>chart manual</header>
<maxValuesDisplayed>5</maxValuesDisplayed>
<sortBy>rowLabelAscending</sortBy>
<title>chart manual</title>
</leftComponents>
<leftComponents>
<componentType>scontrol</componentType>
<footer>scontrol</footer>
<header>scontrol</header>
<scontrol>helloSControl</scontrol>

112
Metadata Components Dashboard

<scontrolHeightInPixels>300</scontrolHeightInPixels>
</leftComponents>
<middleColumnSize>medium</middleColumnSize>
<middleComponents>
<componentType>scontrol</componentType>
<footer>scontrol</footer>
<header>scontrol</header>
<scontrol>helloSControl</scontrol>
<scontrolHeightInPixels>300</scontrolHeightInPixels>
</middleComponents>
<rightColumnSize>medium</rightColumnSize>
<rightComponents>
<componentType>scontrol</componentType>
<footer>scontrol</footer>
<header>scontrol</header>
<scontrol>helloSControl</scontrol>
<scontrolHeightInPixels>300</scontrolHeightInPixels>
</rightComponents>
<rightComponents>
<componentType>table</componentType>
<report>reportFolder/TPS_Report</report>
<footer>table</footer>
<header>table</header>
<indicatorBreakpoint1>20.0</indicatorBreakpoint1>
<indicatorBreakpoint2>30.0</indicatorBreakpoint2>
<indicatorHighColor>#54C254</indicatorHighColor>
<indicatorLowColor>#C25454</indicatorLowColor>
<indicatorMiddleColor>#C2C254</indicatorMiddleColor>
<title>table</title>
</rightComponents>
<rightComponents>
<componentType>metric</componentType>
<report>reportFolder/TPS_Report</report>
<drillDownUrl>http://plywood.com</drillDownUrl>
<footer>metric</footer>
<header>metric</header>
<indicatorBreakpoint1>5.0</indicatorBreakpoint1>
<indicatorBreakpoint2>500.0</indicatorBreakpoint2>
<indicatorHighColor>#54C254</indicatorHighColor>
<indicatorLowColor>#C25454</indicatorLowColor>
<indicatorMiddleColor>#C2C254</indicatorMiddleColor>
<metricLabel>metriclabel</metricLabel>
</rightComponents>
<rightComponents>
<componentType>gauge</componentType>
<report>reportFolder/TPS_Report</report>
<footer>gauge</footer>
<gaugeMax>30.0</gaugeMax>
<gaugeMin>0.0</gaugeMin>
<header>gauge</header>
<indicatorBreakpoint1>10.0</indicatorBreakpoint1>
<indicatorBreakpoint2>20.0</indicatorBreakpoint2>
<indicatorHighColor>#54C254</indicatorHighColor>
<indicatorLowColor>#C25454</indicatorLowColor>
<indicatorMiddleColor>#C2C254</indicatorMiddleColor>
<title>gauge</title>
</rightComponents>
<runningUser>user@salesforcecustomer.com</runningUser>
<textColor>#000000</textColor>
<title>My Dashboard</title>
<titleColor>#000000</titleColor>

113
Metadata Components Document

Field Name Field Type Description

content base64 Content of the document. Base 64-encoded binary data. Prior to
making an API call, client applications must encode the binary
attachment data as base64. Upon receiving a response, client
applications must decode the base64 data to binary. This conversion
is usually handled for you by a SOAP client. This field is inherited
from the MetadataWithContent component.
description string A description of the document. Enter a description to distinguish
this document from others.
fullName string The name of the document including its file extension. The
fullName can only contain characters, letters, and the underscore
(_) character, must start with a letter, and cannot end with an
underscore or contain two consecutive underscore characters. If this
field contained characters before version 14.0 that are no longer
allowed, the characters were stripped out of this field, and the
previous value of the field was saved in the name field. This field
is inherited from the Metadata component.
internalUseOnly boolean Required. Indicates whether the document is confidential (true)
or not (false). This field and public are mutually exclusive; you
cannot set both to true.
keywords string Contains one or more words that describe the document. A check
for matches to words in this field is performed when doing a search.
name string The list of characters allowed in the fullName field has been
reduced for versions 14.0 and later. This field contains the value
contained in the fullName field before version 14.0. This field is

114
Metadata Components EmailTemplate

Field Name Field Type Description

only populated if the value of the fullName field contained
characters that are no longer accepted in that field.
public boolean Required. Indicates whether the document is an image available
for HTML email templates and does not require a Salesforce
username and password to view in an email (true) or not (false).
If the images will be used as a custom app logo or custom tab icon,
both of which require a Salesforce username and password to view,
set this field to false. This field and internalUseOnly are
mutually exclusive; you cannot set both to true.

Declarative Metadata Sample Definition

The following is the definition of a document :

<?xml version="1.0" encoding="UTF-8"?>

<Document xmlns="http://soap.sforce.com/2006/04/metadata">
<internalUseOnly>false</internalUseOnly>
<name>Q2 Campaign Analysis</name>
<public>false</public>
<description>Analyze Q2 campaign effectiveness</description>
</Document>

For a sample of using a document within a folder, see Folder on page 118.

File Suffix and Directory Location

The file suffix is .email for the template file. The accompanying metadata file is named EmailTemplateName-meta.xml.
EmailTemplate components are stored in the email folder in the corresponding package directory.

Version
Email templates are available in API version 12.0 and later.

Fields
This metadata type contains the following fields:

115
Metadata Components EmailTemplate

Field Name Field Type Description

attachedDocuments string[] A list of references to documents in your organization. These documents
are included as attachments in the email template. Each document is
referenced by its path, for example MyFolder/MyDocument.txt.
attachments Attachment[] A list of attachments for the email template.
available boolean Required. Indicates whether this template is offered to users when sending
an email (true) or not (false).
content base64Binary Content of the email template. Base 64-encoded binary data. Prior to
making an API call, client applications must encode the binary attachment
data as base64. Upon receiving a response, client applications must decode
the base64 data to binary. This conversion is usually handled for you by a
SOAP client. This field contains:
• Binary content of the email body if type is set to text
• HTML email content if type is set to html
• HTML body if type is set to custom
• Visualforce body if type is set to visualforce
This field is inherited from the MetadataWithContent component.

description string The email template description. This can be useful to describe the reason
for creating the template.
encodingKey Encoding (enumeration Required. The default encoding setting is Unicode: UTF-8. Change it if
of type string) your template requires data in a different format.
Valid values include:
• UTF-8
• ISO-8859-1
• Shift_JIS
• ISO-2022-JP
• EUC-JP
• ks_c_5601-1987
• ks_c_5601-1987
• Big5
• GB2312

fullName string The email template developer name used as a unique identifier for API
access. The fullName can only contain characters, letters, and the
underscore (_) character, must start with a letter, and cannot end with an
underscore or contain two consecutive underscore characters. If this field
contained characters before version 14.0 that are no longer allowed, the
characters were stripped out of this field, and the previous value of the field
was saved in the name field. This field is inherited from the Metadata
component.
letterhead string The letterhead name associated with this email template. Only available
when type is set to html.
name string Required. Email template name. The list of characters allowed in the
fullName field has been reduced for versions 14.0 and later. This field
contains the value contained in the fullName field before version 14.0.

116
Metadata Components EmailTemplate

Field Name Field Type Description

style EmailTemplateStyle Required. The style of the template. This field is only available when type
(enumeration of type is set to html.
string)
Valid style values include:
• none
• freeForm
• formalLetter
• promotionRight
• promotionLeft
• newsletter
• products

subject string The email subject.

textOnly string The text of the email body if type is set to html or custom.
type EmailTemplateType Required. The email template type.
(enumeration of type
The valid values are:
string)
• text -all users can create or change text email templates.
• html - administrators and users with the "Edit HTML Templates"
permission can create HTML email templates based on a letterhead.
• custom - administrators and users with the "Edit HTML Templates"
permission can create custom HTML email templates without using
a letterhead. You must either know HTML or obtain the HTML code
to insert in your email template.
• visualforce - administrators and users with the "Customize
Application" permission can create email templates using Visualforce.

Attachment
Attachment represents an email attachment.

Field Field Type Description

content base64Binary Required. The attachment content. Base 64-encoded binary
data. Prior to making an API call, client applications must
encode the binary attachment data as base64. Upon receiving
a response, client applications must decode the base64 data
to binary. This conversion is usually handled for you by a
SOAP client.
name string Required. The attachment file name.

Declarative Metadata Sample Definition

A sample XML definition of an template is shown below.

<?xml version="1.0" encoding="UTF-8"?>

<EmailTemplate xmlns="http://soap.sforce.com/2006/04/metadata">
<available>true</available>
<description>Sample Email Template</description>

117
Metadata Components Folder

<encodingKey>ISO-8859-1</encodingKey>
<name>Sample Email Template</name>
<style>none</style>
<subject>Sample email subject</subject>
<textOnly>Your case has been resolved.</textOnly>
<type>custom</type>
</EmailTemplate>

File Suffix and Directory Location

Folders are stored in the document directory of the corresponding package directory. Folders do not have a text file
representation--they are containers for documents. A metadata file accompanies each folder, named FolderName.xls-meta.xml.

Version
Folders are available in API version 11.0 and later.

Fields
This metadata type contains the following fields:

Field Name Field Type Description

accessType FolderAccessTypes Required. The type of access for this folder. Valid values include:
(enumeration of • Shared. This folder is accessible only the specified set of users.
type string) • Public. This folder is accessible by all users.
• Hidden. This folder is hidden from all users.

fullName string The internal name of the folder, based on the name, but with white
spaces and special characters escaped out for validity.
name string Required. The name of the document folder.

118
Metadata Components HomePageComponent

Field Name Field Type Description

publicFolderAccess PublicFolderAccess If Public is the value for accessType, this field indicates the
(enumeration of type of access all users will have to the contents of the folder. Valid
type string) values include:
• ReadOnly. All users can read the contents of the folder, but
no user can change the contents.
• ReadWrite. All users can read or change the contents of the
folder.

Declarative Metadata Sample Definition

The following is the definition of a document folder that contains a document:

<?xml version="1.0" encoding="UTF-8"?>

<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<fullName>basic</fullName>
<types>
<members>sampleFolder</members>
<members>sampleFolder/TestDocument.txt</members>
<name>Document</name>
</types>
<version>11</version>
</Package>

Declarative Metadata File Suffix and Directory Location

The file suffix for home page components is .homePageComponent and components are stored in the homepagecomponents
directory of the corresponding package directory.

Version
Home page components are available in API version 12.0 and later.

HomePageComponent
This metadata type represents the valid values that define a home page component:

Field Name Field Type Description

body string If this is an HTML page component, this is the body of the HTML.

119
Metadata Components HomePageLayout

Field Name Field Type Description

fullName string The name can only contain characters, letters, and the underscore
(_) character, must start with a letter, and cannot end with an
underscore or contain two consecutive underscore characters.
Inherited from the Metadata component, this field is not defined
in the WSDL for this component. It must be specified when
creating, updating, or deleting. See create() to see an example
of this field specified for a call.

links string[] If the pageComponentType is links, then zero or more names

of custom page links can be specified.
• ObjectWebLink
• CustomPageWebLink

pageComponentType PageComponentType Required. Valid values are the following:

(enumeration of type • links
string) • htmlArea
• imageOrNote

width PageComponentWidth This field is only available for HTML components, and indicates
(enumeration of type whether this is a narrow or wide home page component. Valid values
string) are the following:
• narrowComponents
• wideComponents

Declarative Metadata Sample Definition

The following is the definition of a home page component. See HomePageLayout on page 121 and Weblink on page 94 for
related samples.

<?xml version="1.0" encoding="UTF-8"?>

<HomePageComponent xmlns="http://soap.sforce.com/2006/04/metadata">
<width>wideComponents</width>
<links>google</links>
<pageComponentType>links</pageComponentType>
</HomePageComponent>

File Suffix and Directory Location

Home page layouts are stored in the homePageLayouts directory of the corresponding package directory. The extension is
.homePageLayout.

Version
Home page components are available in API version 12.0 and later. It extends the Metadata metadata type and inherits its
fullName field.

Fields
This metadata type represents the valid values that define a home page layout:

Field Name Field Type Description

narrowComponents string[] The list of elements in the narrow column on the left side of the
home page.
wideComponents string[] The list of elements in the wide column on the right side of the
home page.

Declarative Metadata Sample Definition

The following is the definition of a home page layout. See HomePageComponent on page 120 and Weblink on page 94 for
related samples.

<?xml version="1.0" encoding="UTF-8"?>

<HomePageLayout xmlns="http://soap.sforce.com/2006/04/metadata">
<narrowComponents>google</narrowComponents>
</HomePageLayout>

File Suffix and Directory Location

Layouts are stored in the layouts directory of the corresponding package directory. The extension is .layout.
Note: Retrieving a component of this metadata type in a project makes the component appear in the Profile component
as well.

Version
Layouts are available in API version 13.0 and later.

Fields
This metadata type represents the valid values that define a page layout:

Field Name Field Type Description

customButtons string[] The custom buttons for this layout. Each button is a reference
to a Weblink on the same object. For example, a ButtonLink
refers to a Weblink on the same standard or custom object
named 'ButtonLink'.
emailDefault boolean Only relevant if showEmailCheckbox is set; indicates the
default value of that checkbox.
excludeButtons string[] List of standard buttons to exclude from this layout. For
example,
<excludeButtons>Delete</excludeButtons>, will
exclude the "Delete" button from this layout.
fullName string If this is an HTML page component, this is the body of the
HTML. For case close layouts you must prefix the component
name with CaseClose-. For example, a layout named
MyLayout must be named CaseClose-MyLayout if it is
a case close layout.
headers LayoutHeader[] Layout headers are currently only used for tagging, and only
(enumeration of appear in the UI if tagging is enabled. For more information,
type string) see "About Tagging" in the Salesforce online help. Valid string
values are:
• PersonalTagging—tag is private to user.
• PublicTagging—tag can be viewed by any other user
who can access the record.

layoutSections LayoutSection[] The main sections of the layout containing fields, s-controls,
and custom links. The order here determines the layout order.

122
Metadata Components Layout

Field Name Field Type Description

miniLayout MiniLayout A mini layout is used in the mini view of a record in the
console, hover details, and event overlays.
multilineLayoutFields string[] Fields for the special multiline layout fields which appear in
OpportunityProduct layouts and OrderProduct layouts. These
are otherwise the similar to miniLayoutFields.
relatedLists RelatedListItem[] The related lists for the layout, listed in the order they appear
in the UI..
relatedObjects string[] The list of related objects that appears in the mini view of the
console. In database terms, these are foreign key fields on the
object for the layout. For more information, see "Choosing
Related Objects for the Mini Console View" in the Salesforce
online help.
runAssignmentRulesDefault boolean Only relevant if showRunAssignmentRulesCheckbox is set;
indicates the default value of that checkbox.
showEmailCheckbox boolean Only allowed on Case, CaseClose, and Task layouts. If set, a
checkbox appears to show email.
showRunAssignmentRulesCheckbox boolean Only allowed on Lead and Case objects. If set, a checkbox
appears on the page to show assignment rules.
showSolutionSection boolean Only allowed on CaseClose layout. If set, the built-in solution
information section shows up on the page.

MiniLayout
A mini layout is used in the mini view of a record in the console, hover details, and event overlays.

Field Name Field Type Description

fields string[] The fields for the mini-layout, listed in the order they appear in the
UI. Fields that appear here must appear in the main layout.
relatedLists RelatedListItem[] The mini related list, listed in the order they appear in the UI. You
cannot set sorting on mini related lists. Fields that appear here must
appear in the main layout.

LayoutSection
LayoutSection represents a section of a page layout, such as the Custom Links section.

Field Name Field Type Description

customLabel boolean Indicates if this section's label is custom or standard (built-in).
Custom labels can be any text, but must be translated. Standard
labels have a predefined set of valid values, for example 'System
Information', which are automatically translated.
detailHeading boolean Controls if this section appears in the detail page. In the UI, this
setting corresponds to the checkbox in the section details dialog.
editHeading boolean Controls if this section appears in the edit page.

123
Metadata Components Layout

Field Name Field Type Description

label string The label; either standard or custom, based on the customLabel
flag.
layoutColumns LayoutColumn[] The columns of the layout, depending on the style. There may be
1, 2, or 3 columns, ordered left to right.
style LayoutSectionStyle The style of the layout:
(enumeration of type • TwoColumnsTopToBottom - Two columns, tab goes top to
string) bottom
• TwoColumnsLeftToRight - Two columns, tab goes left to
right
• OneColumn - One column
• CustomLinks - Contains custom links only

LayoutColumn
LayoutColumn represents the items in a column within a layout section.

Field Name Field Type Description

layoutItems LayoutItem[] The individual items within a column (ordered from top to bottom).
reserved string This field is reserved for Salesforce. The field resolves an issue with
some SOAP libraries. Any value entered in the field is ignored.

LayoutItem
LayoutItem represents the valid values that define a layout item. An item must have only one of the following set: customLink,
field, scontrol, page.

Field Name Field Type Description

behavior UiBehavior Determines the field behavior. Valid string values:
(enumeration of type • Edit - The layout field can be edited but is not required
string) • Required - The layout field can be edited and is required
• Readonly - The layout field is read-only

customLink string The customLink reference. This is only allowed inside a

CustomLink layoutSection.

emptySpace boolean Controls if this layout item is a blank space.

field string The field name reference, relative to the layout object, for example
Description or MyField__c.
height int For s-control and pages only, the height in pixels.
page string Reference to a Visualforce page.
scontrol string Reference to an s-control.
showLabel boolean For s-control and pages only, whether or not to show the label.
showScrollbars boolean For s-control and pages only, whether or not to show scrollbars.

124
Metadata Components Layout

Field Name Field Type Description

width string For s-control and pages only, the width in pixels or percent. Pixel
values are simply the number of pixels, for example, 500. Percentage
values must include the percent sign, for example, 20%.

RelatedListItem
RelatedListItem represents a related list in a page layout.

Field Name Field Type Description

customButtons string[] A list of custom buttons used in the related list. For more
information, see "Defining Custom Buttons and Links" in the
Salesforce online help.
excludeButtons string[] A list of excluded related-list buttons.
fields string[] A list of fields displayed in the related list.
relatedList string Required. The name of the related list.
sortField string The name of the field that is used for sorting.
sortOrder SortOrder If the sortField is set, the sortOrder field determines the sort
(enumeration of type order.
string) • Asc - sort in ascending order
• Desc - sort in descending order

Declarative Metadata Sample Definition

The following is the definition of a page layout:

<?xml version="1.0" encoding="UTF-8"?>

<Layout xmlns="http://soap.sforce.com/2006/04/metadata">
<customButtons>ButtonLink</customButtons>
<layoutSections>
<editHeading>true</editHeading>
<label>Information</label>
<layoutColumns>
<layoutItems>
<behavior>Required</behavior>
<field>Name</field>
</layoutItems>
<layoutItems>
<height>180</height>
<scontrol>LayoutSControl</scontrol>
<showLabel>true</showLabel>
<showScrollbars>true</showScrollbars>
<width>50%</width>
</layoutItems>
</layoutColumns>
<layoutColumns>
<layoutItems>
<behavior>Edit</behavior>
<field>OwnerId</field>
</layoutItems>
<layoutItems>
<behavior>Edit</behavior>
<field>CurrencyIsoCode</field>

125
Metadata Components Layout

</layoutItems>
</layoutColumns>
<style>TwoColumnsTopToBottom</style>
</layoutSections>
<layoutSections>
<editHeading>true</editHeading>
<label>System Information</label>
<layoutColumns>
<layoutItems>
<behavior>Readonly</behavior>
<field>CreatedById</field>
</layoutItems>
<layoutItems>
<behavior>Readonly</behavior>
<field>Alpha1__c</field>
</layoutItems>
</layoutColumns>
<layoutColumns>
<layoutItems>
<behavior>Readonly</behavior>
<field>LastModifiedById</field>
</layoutItems>
<layoutItems>
<behavior>Edit</behavior>
<field>TextArea__c</field>
</layoutItems>
</layoutColumns>
<style>TwoColumnsTopToBottom</style>
</layoutSections>
<layoutSections>
<customLabel>true</customLabel>
<detailHeading>true</detailHeading>
<label>Custom Links</label>
<layoutColumns>
<layoutItems>
<customLink>CustomWebLink</customLink>
</layoutItems>
</layoutColumns>
<style>CustomLinks</style>
</layoutSections>
<miniLayoutFields>Name</miniLayoutFields>
<miniLayoutFields>OwnerId</miniLayoutFields>
<miniLayoutFields>CurrencyIsoCode</miniLayoutFields>
<miniLayoutFields>Alpha1__c</miniLayoutFields>
<miniLayoutFields>TextArea__c</miniLayoutFields>
<miniRelatedLists>
<relatedList>RelatedNoteList</relatedList>
</miniRelatedLists>
<relatedLists>
<fields>StepStatus</fields>
<fields>CreatedDate</fields>
<fields>OriginalActor</fields>
<fields>Actor</fields>
<fields>Comments</fields>
<fields>Actor.Alias</fields>
<fields>OriginalActor.Alias</fields>
<relatedList>RelatedProcessHistoryList</relatedList>
</relatedLists>
<relatedLists>
<relatedList>RelatedNoteList</relatedList>
</relatedLists>
</Layout>

126
Metadata Components Letterhead

Letterhead
Represents formatting options for the letterhead in an email template. Letterheads define the look and feel of your HTML
email templates. Your HTML email templates can inherit the logo, color, and text settings from a letterhead. For more
information, see "Creating Letterheads" in the Salesforce online help. It extends the Metadata metadata type and inherits its
fullName field.

File Suffix and Directory Location

The file suffix for letterheads is .letter and components are stored in the letterhead directory of the corresponding package
directory.

Version
Letterheads are available in API version 12.0 and later.

Fields
With the exception of logo, and horizontal and vertical alignment, all of these fields are required.

Field Name Field Type Description

available boolean
Required. Indicates whether this letterhead can be used
(true) or not (false), for example, in an email
template.

backgroundColor string
Required. The background color, in hexadecimal, for
example #FF6600.

bodyColor string
Required. The body color in hexadecimal.

bottomLine LetterheadLine (enumeration of type

Required. The style for the bottom line. Valid style
string)
values include:
• color. The color of the line in hexadecimal, as a
string value.
• height. The height of the line, as an int value.

description string
Text description of how this letterhead differs from
other letterheads.

fullName string
The internal name of the letterhead, based on the name,
but with white spaces and special characters escaped out
for validity.

footer LetterheadHeaderFooter
Required. The style for the footer.

header LetterheadHeaderFooter
Required. The style for the header.

127
Metadata Components Letterhead

Field Name Field Type Description

middleLine LetterheadLine
Required. The style for the middle border line in your
letterhead. Valid style values include:
• color. The color of the line in hexadecimal, as a
string value.
• height. The height of the line, as an int value.

name string Required. The name of the letterhead.

topLine LetterheadLine
Required. The style for the top horizontal line below
the header. Valid style values include:
• color. The color of the line in hexadecimal, as a
string value.
• height. The height of the line, as an int value.

LetterheadHeaderFooter
LetterheadHeaderFooter represents the properties of a header or footer.

Field Field Type Description

backgroundColor string Required. The background color of the header or footer in
hexadecimal format.
height DashboardComponent[] Required. The height of the header or footer.
horizontalAlignment LetterheadHorizontalAlignment The horizontal alignment of the header or footer. Valid
(enumeration of type string) values are:
• None
• Left
• Center
• Right

logo string The logo which is a reference to a document, for example

MyFolder/MyDocument.gif.
verticalAlignment LetterheadVerticalAlignment The vertical alignment of the header or footer. Valid values
(enumeration of type string) are:
• None
• Top
• Middle
• Bottom

LetterheadLine
LetterheadLine represents the properties of a line.

Field Field Type Description

color string Required. The color of the line in hexadecimal format.

128
Metadata Components Metadata

Field Field Type Description

height int Required. The height of the line.

Declarative Metadata Sample Definition

<?xml version="1.0" encoding="UTF-8"?>

<Letterhead xmlns="http://soap.sforce.com/2006/04/metadata">
<available>true</available>
<backgroundColor>#CCCCCC</backgroundColor>
<bodyColor>#33FF33</bodyColor>
<bottomLine>
<color>#3333FF</color>
<height>5</height>
</bottomLine>
<description>INITIAL</description>
<footer>
<backgroundColor>#FFFFFF</backgroundColor>
<height>100</height>
<horizontalAlignment>Left</horizontalAlignment>
<verticalAlignment>Top</verticalAlignment>
</footer>
<header>
<backgroundColor>#FFFFFF</backgroundColor>
<height>100</height>
<horizontalAlignment>Left</horizontalAlignment>
<verticalAlignment>Top</verticalAlignment>
</header>
<middleLine>
<color>#AAAAFF</color>
<height>5</height>
</middleLine>
<name>SimpleLetterheadLabel</name>
<topLine>
<color>#FF99FF</color>
<height>5</height>
</topLine>
</Letterhead>

Metadata
This is the base class for all metadata types. You cannot edit this object. A component is an instance of a metadata type.
Metadata is analogous to sObject, which represents all standard objects. Metadata represents all components and fields in the
metadata API. Instead of identifying each component with an ID, each custom object or custom field has a unique fullName,
which must be distinct from standard object names, as it must be when you create custom objects or custom fields in the
Salesforce user interface.

Version
Metadata components are available in API version 10.0 and later.

129
Metadata Components MetadataWithContent

Fields

Field Name Field Type Description

fullName string Required. The name of the component. If a field, the name must
specify the parent object, for example Account.FirstName.
The __c suffix must be appended to custom object names and
custom field names when you are setting the fullName. For
example, a custom field in a custom object could have a fullName
of MyCustomObject__c.MyCustomField__c.

See Also:
CustomObject
CustomField
MetadataWithContent

MetadataWithContent
This is the base type for all metadata types that contain content, such as documents or email templates. It extends Metadata.
You cannot edit this object.

Version
MetadataWithContent components are available in API version 14.0 and later.

Fields

Field Name Field Type Description

content base64Binary Base 64-encoded binary data. Prior to making an API call, client
applications must encode the binary attachment data as base64.
Upon receiving a response, client applications must decode the
base64 data to binary. This conversion is usually handled for you
by a SOAP client.
fullName string Required. The name of the component. The fullName can only
contain characters, letters, and the underscore (_) character, must
start with a letter, and cannot end with an underscore or contain
two consecutive underscore characters.
Inherited from the Metadata component, this field is not defined
in the WSDL for this component. It must be specified when
creating, updating, or deleting. See create() to see an example
of this field specified for a call.

Declarative Metadata File Suffix and Directory Location

Force.com Portal components are stored in the portals directory of the corresponding package directory. The file name matches
the portal name, and the extension is .portal.

Version
Force.com Portal components are available in API version 15.0 and later.

Fields

Field Field Type Description

active boolean Required. Denotes whether this portal is active.
admin string The full name of the user designated to administer the
portal.
defaultLanguage string The default language for HTML messages for the portal.
Use the abbreviation for the language, for example, en_US
for United States English.
description string The portal description.
emailSenderAddress string Required. The email address used when sending emails
using templates configured from the portal (for example,
for resetting the password).
emailSenderName string Required. The name to display when sending emails using
templates configured from the portal (for example, for
resetting the password).
enableSelfCloseCase boolean For the Customer Portal, allows portal users to close their
own cases.
footerDocument string The file to be used as the footer for this portal.
forgotPassTemplate string The email template to use when a user clicks the Forgot
Password link.
fullName string Required. The name of the portal.
Inherited from Metadata, this field is not defined in the
WSDL for this metadata type. It must be specified when
creating, updating, or deleting. See create() to see an
example of this field specified for a call.

headerDocument string The file to be used as the header for this portal.
isSelfRegistrationActivated boolean Determines whether self-registration is active or not for
this portal.

131
Metadata Components Portal

Field Field Type Description

loginHeaderDocument string The file to be used as the header for this portal's login page.
logoDocument string The file to be used as the logo for this portal.
logoutUrl string The URL that the user should be redirected to on logout.
newCommentTemplate string The email template to be used for auto-notifications on
new case comments.
newPassTemplate string The email template to be used for auto-notifications on
password reset.
newUserTemplate string The email template to be used for auto-notifications on
new user creation.
ownerNotifyTemplate string The email template to be used for auto-notifications on
owner change.
selfRegNewUserUrl string The URL of the self-registration page.
selfRegUserDefaultProfile string The default profile for self-registered users.
selfRegUserDefaultRole PortalRoles (enumeration of The default role for self-registered users. The valid values
type string) are:
• Executive
• Manager
• User
• PersonAccount

selfRegUserTemplate string The email template to be used for auto-notifications on

self-registration.
showActionConfirmation boolean Determines whether or not confirmation messages are
displayed for actions in the portal.
stylesheetDocument string The Document object to be used as the CSS stylesheet for
this portal.
type PortalType (enumeration of Required. The type for this portal. The valid values are:
type string) • CustomerSuccess
• Partner

Declarative Metadata Sample Definition

A sample XML definition of a portal is shown below.

<?xml version="1.0" encoding="UTF-8"?>

<Portal xmlns="http://soap.sforce.com/2006/04/metadata">
<active>true</active>
<description>Customer Portal</description>
<emailSenderName>rguest@albany.com</emailSenderName>
<enableSelfCloseCase>false</enableSelfCloseCase>
<forgotPassTemplate>unfiled$public/ChangePwdEmail</forgotPassTemplate>
<isSelfRegistrationActivated>false</isSelfRegistrationActivated>
<newPassTemplate>unfiled$public/ChangePwdEmail</newPassTemplate>
<newUserTemplate>unfiled$public/NewUserEmail</newUserTemplate>
<selfRegUserTemplate>unfiled$public/SelfRegUserEmail</selfRegUserTemplate>

132
Metadata Components Profile

<showActionConfirmation>false</showActionConfirmation>
<type>CustomerSuccess</type>
</Portal>

Declarative Metadata File Suffix and Directory Location

The file suffix is .profile. There is one file for each profile, stored in the profiles folder in the corresponding package directory.

Version
Profiles are available in API version 10.0 and later.

Fields
The contents of a profile returned by the metadata API depends on the contents requested in the RetrieveRequest message.
For example, profiles only include field-level security for fields included in custom objects returned in the same RetrieveRequest
as the profiles. The profile definition contains the following fields:

Field Name Field Type Description

applicationVisibilities ProfileApplicationVisibility[] Indicates which applications are visible to users assigned to this
profile.
classAccesses ProfileApexClassAccess[] Indicates which top-level Apex classes have methods that users
assigned to this profile can execute.
fieldLevelSecurities ProfileFieldLevelSecurity[] Indicates which fields are visible to a user assigned to this profile.
fullName string The name can only contain characters, letters, and the underscore
(_) character, must start with a letter, and cannot end with an
underscore or contain two consecutive underscore characters.
Inherited from the Metadata component, this field is not defined
in the WSDL for this component. It must be specified when creating,
updating, or deleting. See create() to see an example of this field
specified for a call.

layoutAssignments ProfileLayoutAssignments[] Indicates which layout to use for this profile.

objectPermissions ProfileObjectPermissions[] Indicates which objects are accessible to a user assigned to this profile,
and the kind of access available (create, read, update, delete).
pageAccesses ProfileApexPageAccess[] Indicates which custom Visualforce controllers or controller
extensions applied to a Visualforce page have methods that users
assigned to this profile can execute.

133
Metadata Components Profile

Field Name Field Type Description

recordTypeVisibilities ProfileRecordTypeVisibility[] Indicates the visibility of record types for users assigned to this
profile.
tabVisibilities ProfileTabVisibility[] Indicates which record types are visible to a user assigned to this
profile, and therefore which tabs within an application are visible.

ProfileApplicationVisibility
ProfileApplicationVisibility represents an application that is visible to a user assigned to this profile:

Field Name Field Type Description

application string Required. The name of the application.
default boolean Required. Indicates whether the application is the default application
(true) or not (false). Only one application per profile can be
set to true.
visible boolean Required. Indicates whether this application is visible to users
assigned to this profile (true) or not (false).

ProfileApexClassAccess
ProfileApexClassAccess determines which top-level Apex classes have methods that users assigned to this profile can execute.
For more information, see "Setting Apex Class Security" in the Salesforce online help.

Field Name Field Type Description

apexClass string Required. The Apex class name.
enabled boolean Required. Indicates whether users assigned to this profile can execute
methods in the top-level class (true) or not (false).

ProfileFieldLevelSecurity
ProfileFieldLevelSecurity represents the field level security for users assigned to a profile:

Field Name Field Type Description

editable boolean Required. Indicates whether this field is editable (true) or not
(false).
field string Required. Indicates the name of the field.
hidden boolean Indicates whether this field is hidden (true) or not (false).

ProfileLayoutAssignments
ProfileLayoutAssignments determines which layout to use for a profile and a given entity:

Field Name Field Type Description

layout string Required. Indicates the layout for this particular entity.

134
Metadata Components Profile

Field Name Field Type Description

recordType string This field is optional. If the recordType of the record matches a
layout assignment rule, it will use the specified layout.

ProfileObjectPermissions
ProfileObjectPermissions represents the field level security for objects whose permissions are altered by this profile:

Field Name Field Type Description

allowCreate boolean Indicates whether the object referenced by the object field can be
created by the users assigned to this profile (true) or not (false).
This field is named revokeCreate before version 14.0 and the
logic is reversed. The field name change and the update from true
to false and vice versa is automatically handled between versions
and does not require any manual editing of existing XML
component files. The field name change and the update from true
to false and vice versa is automatically handled between versions
and does not require any manual editing of existing XML
component files.

allowDelete boolean Indicates whether the object referenced by the object field can be
deleted by the users assigned to this profile (true) or not (false).
This field is named revokeDelete before version 14.0 and the
logic is reversed. The field name change and the update from true
to false and vice versa is automatically handled between versions
and does not require any manual editing of existing XML
component files.

allowEdit boolean Indicates whether the object referenced by the object field can be
edited by the users assigned to this profile (true) or not (false).
This field is named revokeEdit before version 14.0 and the logic
is reversed. The field name change and the update from true to
false and vice versa is automatically handled between versions
and does not require any manual editing of existing XML
component files.

allowRead boolean Indicates whether the object referenced by the object field can be
seen by the users assigned to this profile (true) or not (false).
This field is named revokeRead before version 14.0 and the logic
is reversed. The field name change and the update from true to
false and vice versa is automatically handled between versions
and does not require any manual editing of existing XML
component files.

modifyAllRecords boolean Indicates whether the object referenced by the object field can be
read, edited, or deleted by the users assigned to this profile (true)
or not (false), regardless of the sharing settings for the object.
This is equivalent to the "Modify All Data" user permission limited
to the individual object level. This is a new field in API version
15.0.

135
Metadata Components Profile

Field Name Field Type Description

object string Required. The name of the object whose permissions are altered by
this profile, for example, MyCustomObject__c.
viewAllRecords boolean Indicates whether the object referenced by the object field can be
read by the users assigned to this profile (true) or not (false),
regardless of the sharing settings for the object. This includes private
records (records with no parent object). This is equivalent to the
"View All Data" user permission limited to the individual object
level. This is a new field in API version 15.0.

ProfileApexPageAccess
ProfileApexPageAccess determines which custom Visualforce controllers or controller extensions applied to a Visualforce page
have methods that users assigned to this profile can execute. For more information, see "Setting Apex Class Security" in the
Salesforce online help.

Field Name Field Type Description

apexPage string Required. The Visualforce page name.
enabled boolean Required. Indicates whether users assigned to this profile can execute
methods in the custom controller or controller extension applied to
the page (true) or not (false).

ProfileRecordTypeVisibility
ProfileRecordTypeVisibility represents the visibility of record types for this profile. Record types allow you to offer different
business processes, picklist values, and page layouts to different users based on their profiles. For more information, see
"Managing Record Types" in the Salesforce online help.

Field Name Field Type Description

default boolean Required. Indicates whether the record type is the default for this
pair of profile and object (true) or not (false). Only one default
is allowed per object.
personAccountDefault boolean Indicates whether the record type is the default person account
record type for this pair of profile and object (true) or not
(false). Only one person account record type default is allowed
per object. This field is only relevant for record types for account or
contact objects.
A person account is an individual consumer with whom you do
business, such as a financial services client, an online shopper, or a
vacation traveler. Person accounts are applicable to organizations
that operate on a business-to-consumer model as opposed to a
business-to-business model.
For more information about person accounts, see "What is a Person
Account?" in the Salesforce online help. Person accounts are not
enabled by default in Salesforce. To request person accounts, contact
salesforce.com.

136
Metadata Components Profile

Field Name Field Type Description

recordType string Required. The record type name, for example
Account.MyRecordType.
visible boolean Required. Indicates whether this record type is visible to users
assigned to this profile (true) or not (false).

ProfileTabVisibility
ProfileTabVisibility represents the visibility of tabs for this profile:

Field Name Field Type Description

tab string Required. The name of the tab.
visibility TabVisibility Required. Indicates the visibility of the tab.

TabVisibility
TabVisibility represents the tab customizations for users assigned to this profile:

Field Name Field Type Description

visibility TabVisibility Indicates the visibility of the tab:
(enumeration of type • Hidden
string) • DefaultOff
• DefaultOn
For more about tab visibility, see Creating and Editing Profiles in
the Salesforce online help.

Java Sample
The following sample uses picklists, profiles, and record types:

// Create an expense report record, tab and application...

CustomObject expenseRecord = new CustomObject();
expenseRecord.setFullName("ExpenseReport__c");
expenseRecord.setLabel("Expense Report");
expenseRecord.setPluralLabel("Expense Reports");

expenseRecord.setDeploymentStatus(DeploymentStatus.Deployed);
expenseRecord.setSharingModel(SharingModel.ReadWrite);

CustomField nameField = new CustomField();

nameField.setType(FieldType.AutoNumber);
nameField.setLabel("Expense Report Number");
nameField.setDisplayFormat("ER-{0000}");
expenseRecord.setNameField(nameField);

create(expenseRecord);

Picklist expenseStatus = new Picklist();

PicklistValue unsubmitted = new PicklistValue();
unsubmitted.setFullName("Unsubmitted");
PicklistValue submitted = new PicklistValue();
submitted.setFullName("Submitted");

137
Metadata Components Profile

PicklistValue approved = new PicklistValue();

approved.setFullName("Approved");
PicklistValue rejected = new PicklistValue();
rejected.setFullName("Rejected");
expenseStatus.setPicklistValues(new PicklistValue[] {unsubmitted, submitted, approved,
rejected});

CustomField expenseStatusField = new CustomField();

CustomTab expenseTab = new CustomTab();

expenseTab.setFullName("ExpenseReport__c");
expenseTab.setMotif("Custom70: Handsaw");
expenseTab.setCustomObject(true);
create(expenseTab);

CustomApplication application = new CustomApplication();

application.setFullName("ExpenseForce");
application.setTab(new String[] {expenseTab.getFullName()});
create(application);

// Employees and managers have the same app visibility...

ProfileApplicationVisibility appVisibility = new ProfileApplicationVisibility();
appVisibility.setApplication("ExpenseForce");
appVisibility.setVisible(true);

Profile employee = new Profile();

employee.setFullName("Employee");
employee.setApplicationVisibilities(new ProfileApplicationVisibility[] {appVisibility});
create(employee);

Profile manager = new Profile();

manager.setFullName("Manager");
manager.setApplicationVisibilities(new ProfileApplicationVisibility[] {appVisibility});
create(manager);

// But employees and managers have different access to the state of the expense sheet
RecordType edit = new RecordType();
edit.setFullName("ExpenseReport__c.Edit");
RecordTypePicklistValue editStatuses = new RecordTypePicklistValue();
editStatuses.setPicklist("ExpenseStatus__c");
editStatuses.setValues(new PicklistValue[] {unsubmitted, submitted});
edit.setPicklistValues(new RecordTypePicklistValue[] {editStatuses});
create(edit);

RecordType approve = new RecordType();

Declarative Metadata Sample Definition

The following is the definition of the standard profile in an organization with one custom object, TestWeblinks__c and
one record type, My First Recordtype:

<?xml version="1.0" encoding="UTF-8"?>

<Profile xmlns="http://soap.sforce.com/2006/04/metadata">
<applicationVisibilities>
<application>Myriad Publishing</application>

138
Metadata Components Profile

<default>false</default>
<visible>true</visible>
</applicationVisibilities>
<objectPermissions>
<object>TestWeblinks__c</object>
</objectPermissions>
<recordTypeVisibilities>
<default>true</default>
<recordType>TestWeblinks__c.My First Recordtype</recordType>
<visible>true</visible>
</recordTypeVisibilities>
<tabVisibilities>
<tab>Myriad Publications</tab>
<visibility>DefaultOn</visibility>
</tabVisibilities>
</Profile>

Usage
When you use the retrieve() call to get information about profiles in your organization, the returned .profile files only
include security settings for the other metadata types referenced in the retrieve request. For example, the package.xml file
below contains a types element that matches all custom objects, so the returned profiles contain object and field permissions
for all custom objects in your organization, but do not include permissions for standard objects, such as Account, and standard
fields.

<?xml version="1.0" encoding="UTF-8"?>

<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
<members>*</members>
<name>CustomObject</name>
</types>
<types>
<members>*</members>
<name>Profile</name>
</types>
<version>15.0</version>
</Package>

The wildcard “*” on CustomObject does not match standard objects and this helps to avoid making unintended, high-impact
profile changes. If you create a few custom objects in a Developer Edition organization, retrieve() the information, and
subsequently deploy() the custom objects to your production organization, the profile and field-level security for all your
standard objects, such as Account, and standard fields are not overwritten unless you explicitly create separate types elements
for the standard objects or fields. For more information about profiles, see "User Permissions on Profiles" in the Salesforce
online help.
The metadata API intentionally makes it somewhat difficult to include standard fields in retrieve() calls in order to
prevent unexpected profile changes. However, you can still retrieve and deploy profile permissions for custom and standard
fields in standard objects, such as Account.
The next package.xml file allows you to return profile permissions for Account standard and custom fields. Note how the
standard Account object is defined in a types element by specifying it as a member of a CustomObject type.

<?xml version="1.0" encoding="UTF-8"?>

<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
<members>Account</members>
<name>CustomObject</name>
</types>
<types>
<members>*</members>
<name>Profile</name>
</types>

139
Metadata Components Report

The final package.xml file allows you to return profile permissions for the MyCustomField__c custom field in the Account
object.

<?xml version="1.0" encoding="UTF-8"?>

<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
<members>Account.MyCustomField__c</members>
<name>CustomField</name>
</types>
<types>
<members>*</members>
<name>Profile</name>
</types>
<version>15.0</version>
</Package>

Report
Represents a custom report. It extends the Metadata metadata type and inherits its fullName field. This metadata type only
supports custom reports; standard reports are not supported. For more information, see "What Is a Report?" in the Salesforce
online help.

Declarative Metadata File Suffix and Directory Location

Reports are stored in the reports directory of the corresponding package directory. The file name matches the report title and
the extension is .report.

Version
Report components are available in API version 14.0 and later.

Fields
The following information assumes that you are familiar with creating and running reports. For more information on these
fields, see "Creating a Custom Report" in the Salesforce online help.

Field Field Type Description

aggregates ReportAggregate[] List that defines custom summary formulas
for summary and matrix reports.
chart ReportChart Defines a chart for summary and matrix
reports .
colorRanges ReportColorRange[] List that specifies conditional highlighting
for report summary data.
columns ReportColumn[] List that specifies the fields displayed in the
report. Fields appear in the report in the same
order as they appear in the metadata API file.
currency CurrencyIsoCode (enumeration of type When using multiple currencies, some reports
string) allow you to display converted amounts by

140
Metadata Components Report

Field Field Type Description

selecting the appropriate column to display.
For example, in opportunity reports, you can
include the Amount (converted) column on
the report. This field is an enumeration of
type string that defines the currency in which
to display converted amounts. Valid values:
Must be one of the valid alphabetic,
three-letter currency ISO codes defined by
the ISO 4217 standard, such as USD, GBP,
or JPY.
description string Specifies a general description, which is
displayed with the report name. Maximum
characters: 255 characters.
filter ReportFilter Limits report results to records with specific
data. For example, you can limit report results
to opportunities for which the amount is
greater than $1,000:
<filters>
<column>AMOUNT</column>

<operator>greaterThan</operator>

For more information, see "Entering Filter

Criteria" in the Salesforce online help.

format ReportFormat (enumeration of type string) Defines the report format. For example,
Tabular for a simple data list without
subtotals.
fullName string The report unique developer name used as
an identifier for API access. The fullName
can only contain characters, letters, and the
underscore (_) character, must start with a
letter, and cannot end with an underscore or
contain two consecutive underscore
characters. This field is inherited from the
Metadata component.
groupingsAcross ReportGrouping[] List that defines the fields by which you want
to group and subtotal data across a matrix
report (row headings). When grouping by a
date field, you can further group the data by
a specific time period such as days, weeks, or
months. Maximum: 2 fields.
groupingsDown ReportGrouping[] For Summary and Matrix reports: List that
defines the fields by which you want to group
and subtotal. For summary reports, choosing
more than one sort field allows you to subsort
your data. For matrix reports, specifies

141
Metadata Components Report

Field Field Type Description

summary fields for column headings. When
grouping by a date field, you can further
group the data by a specific time period such
as days, weeks, or months. Maximum for
matrix reports: 2. Maximum for summary
reports: 3
name string Required. The report name. for example,
Opportunity Pipeline
params ReportParam[] List that specifies settings specific to each
report type, in particular options that let you
filter a report to obtain useful subsets. For
example, the Activities report type lets you
specify whether you want to see open or
closed activities or both and whether you
want to see tasks or events or both. Valid
values depend on the report type.
reportType string Required. Defines the type of data in the
report. For example, Opportunity to
create a report of opportunities data.
rowLimit int Defines the maximum number of rows that
can be returned for the report.
scope string Defines the scope of data on which you run
the report. For example, whether you want
to run the report against all opportunities,
opportunities you own, or opportunities your
team owns. Valid values depend on the
reportType. For example, for Accounts
reports:
• MyAccounts
• MyTeamsAccounts
• AllAccounts

showDetails boolean false shows a collapsed view of the report

with only the headings, subtotals, and total.
Default: true
sortColumn string Specifies the field on which to sort data in
the report. Use sortOrder to specify the
sort order.
sortOrder SortOrder (enumeration of type string) Specifies the sort order. Use sortColumn to
specify the field on which to sort.
timeFrameFilter ReportTimeFrameFilter Limits report results to records within a
specified time frame.

142
Metadata Components Report

ReportAggregate
ReportAggregate defines custom summary formulas on summary or matrix reports. For more information on these fields, see
"Building Custom Summary Formulas" in the Salesforce online help.

Field Field Type Description

acrossGroupingContext string Defines the row grouping level at which you want your
custom summary formula to be displayed. This is a new
field in API version 15.0.
calculatedFormula string Required. The custom summary formula. For example,
AMOUNT:SUM + OPP_QUANTITY:SUM
datatype CustomFieldDatatypes Required. Specifies the data type for formatting and display
(enumeration of type string) of the custom summary formula results.
description string The custom summary formula description. Maximum: 255
characters.
developerName string Required. The internal development name of the custom
summary formula, for example, FORMULA1. This is used
to reference custom summary formulas from other report
components, including conditional highlighting.
downGroupingContext string Defines the column grouping level at which you want your
custom summary formula to be displayed. This is a new
field in API version 15.0.
isActive boolean Required. true displays the formula result in the report.
false does not display the result in the report.
masterLabel string Required. The custom summary formula label (name).
scale int The formula result is calculated to the specified number of
decimal places. Valid values 0 through 18.

ReportGrouping
ReportGrouping defines how to group and subtotal data for summary and matrix reports.

Field Field Type Description

dateGranularity UserDateGranularity When grouping by a date field, the time period by which
(enumeration of type string) to group.
field string Required. The field by which you want to summarize data.
For example, CAMPAIGN_SOURCE
sortOrder SortOrder Required. Whether to sort data in ascending or descending
alphabetical and numerical order.

SortOrder
An enumeration of type string that defines the order in which data is sorted in the report fields. Valid values:

143
Metadata Components Report

Field Description
Asc Sorts data in ascending alphabetical and numerical order.
Desc Sorts data in descending alphabetical and numerical order.

UserDateGranularity
An enumeration of type string that defines the time period by which to group data. Valid values:

Enumeration Value Description

None No grouping by date
Day By day
Week By week
Month By month
Quarter By quarter
Year By year
FiscalQuarter By fiscal quarter. You can set the fiscal year for your organization. See "Setting the Fiscal
Year" in the Salesforce online help.
FiscalYear By fiscal year
MonthInYear By calendar month in year
DayInMonth By calendar day in month
FiscalPeriod When custom fiscal years are enabled: By fiscal period
FiscalWeek When custom fiscal years are enabled: By fiscal week

ReportSummaryType
An enumeration of type string that defines how report fields are summarized. Valid values:

Enumeration Value Description

Sum Total
Average Average
Maximum Largest value
Minimum Smallest value
None The field is not summarized.

ReportColorRange
ReportColorRange defines conditional highlighting for report summary data.

144
Metadata Components Report

Field Field Type Description

aggregate ReportSummaryType Required. Defines how the field specified in columnName
(enumeration of type string) is summarized. For example, Sum
columnName string Required. Specifies the field whose value ranges are
represented by colors.
highBreakpoint double Required. Specifies the number that separates the mid color
from the high color.
highColor string Required. Specifies the color (in HTML format) to
represent data that falls into the high number range. This
color spans from the highBreakpoint value.
lowBreakpoint double Required. Specifies the number that separates the low color
from the mid color.
lowColor string Required. Specifies a color (in HTML format) to represent
data that falls into the low value range, below the
lowBreakpoint value.
midColor string Required. Specifies a color (in HTML format) to represent
data that falls into the mid value range.

ReportColumn
ReportColumn defines how fields (columns) are displayed in the report.

Field Field Type Description

aggregateTypes ReportSummaryType[] List that defines if and how each report field is summarized.
(enumeration of type string)
field string Required. The field name. For example, AGE or
OPPORTUNITY_NAME

ReportFilter
ReportFilter limits the report results by filtering data on specified fields.

Field Field Type Description

booleanFilter string Specifies advanced filter conditions. For more information
on advanced filter conditions, see "Working with Advanced
Filter Conditions" in the Salesforce online help.
criteriaItems ReportFilterItem The criteria by which you want to filter report data.
language Language (enumeration of This field is an enumeration of type string that defines the
type string) language used when a report filters against a picklist value
using the operators contains or startsWith. For a
list of valid language values, see Translations.

ReportFilterItem
ReportFilterItem limits the report results by filtering data on specified fields.

145
Metadata Components Report

Field Field Type Description

column string Required. The field on which you want to filter data. For
example, AMOUNT
operator FilterOperation (enumeration Required. An enumeration of type string that defines the
of type string) operator used to filter the data, for example,
greaterThan. For valid values, see FilterOperation.
value string The value by which you want to filter the data, for example,
1000. Note that the metadata API filter condition values
do not always match those that you enter in the report
wizard. For example, in the metadata API dates are always
converted to the US date format and values entered in a
non-US English language may be converted to a standard
US English equivalent.

ReportFormat
An enumeration of type string that defines the report format. Valid values:

Enumeration Value Description

Matrix Summarizes data in a grid. Use to compare related totals.
Summary Lists, sorts, and subtotals data.
Tabular Lists data with no sorting or subtotals.

ReportParam
ReportParam represents settings specific to a report type, especially options that let you filter a report to certain useful subsets.

Field Field Type Description

name string Required. Specifies a specific reportType setting.
value string Required. The setting value.

CustomFieldDatatypes
An enumeration of type string that specifies the data type for formatting and display of custom summary formula results. Valid
values:

Enumeration Value
Number

Percent

Currency

ReportChart
ReportChart represents charts on summary and matrix reports.

146
Metadata Components Report

Field Field Type Description

backgroundColor1 string Specifies the beginning color (in HTML format) for a
gradient color background.
backgroundColor2 string Specifies the end color (in HTML format) for a gradient
color background.
backgroundFadeDir ChartBackgroundDirection Specifies the direction for a gradient color background. Use
(enumeration of type string) with backgroundColor1 to specify the beginning color
and backgroundColor2 to specify the end color for the
gradient design. Use white for both if you do not want a
background design. Valid values:
• diagonal
• leftToRight
• topToBottom

chartType ChartType (enumeration of Required. Specifies the chart type. Available chart types
type string) depend on the report type.
groupingColumn string Specifies the field by which to group data. This data is
displayed on the X-axis for vertical column charts and on
the Y-axis for horizontal bar charts.
legendPosition ChartLegendPosition Required.
(enumeration of type string)
The location of the legend with respect to the chart. The
valid values are:
• LEGEND_NONE
• LEGEND_RIGHT
• LEGEND_BOTTOM

location ChartPosition (enumeration Required. Specifies whether the chart is displayed at the
of type string) top or bottom of the report.
secondaryGroupingColumn string For grouped chart types: Specifies the field by which to
group the data.
showAxisLabels boolean For bar and line charts: Specifies whether the chart displays
names for each axis.
size ReportChartSize Required. Specifies the chart size.
(enumeration of type string)
summaryAggregate ReportSummaryType Defines how to summarize the chart data. For example,
(enumeration of type string) Sum
summaryAxisManualRangeEnd double When specifying the axis range manually: Defines the
ending value.
summaryAxisManualRangeStart double When specifying the axis range manually: Defines the
starting value.
summaryAxisRange ChartRangeType Required. For bar, line, and column charts: Defines whether
(enumeration of type string) to specify the axis range manually or automatically.
summaryColumn string Required. Specifies the field by which to summarize the
chart data. Typically this field is displayed on the Y-axis.

147
Metadata Components Report

Field Field Type Description

textColor string The color (in HTML format) of the chart text and labels.
textSize int The size of the chart text and labels. Valid values:
• 8
• 9
• 10
• 12
• 14
• 18
• 24
• 36

title string The chart title. Max 255 characters.

titleColor string The color (in HTML format) of the title text.
titleSize int The size of the title text. Valid values:
• 8
• 9
• 10
• 12
• 14
• 18
• 24
• 36

ChartType
An enumeration of type string that defines the chart type. For information on each of these chart types, see "Chart Types" in
the Salesforce online help. Valid values:

Enumeration Value
None

HorizontalBar

HorizontalBarGrouped

HorizontalBarStacked

HorizontalBarStackedTo100

VerticalColumn

VerticalColumnGrouped

VerticalColumnStacked

VerticalColumnStackedTo100

Line

LineGrouped

148
Metadata Components Report

Enumeration Value
LineCumulative

LineCumulativeGrouped

Pie

ChartPosition
An enumeration of type string that specifies the position of the chart in the report. Valid values:

Enumeration Value
CHART_TOP

CHART_BOTTOM

ReportChartSize
An enumeration of type string that specifies the chart size. Valid values:

Enumeration Value
Tiny

Small

Medium

Large

Huge

ChartRangeType
An enumeration of type string that defines the report format. Valid values:

Enumeration Value
Manual

Automatic

ReportTimeFrameFilter
ReportTimeFrameFilter represents the report time period.

Field Field Type Description

dateColumn string Required. The date field on which to filter data. For
example, CLOSE_DATE
endDate date When interval is INTERVAL_CUSTOM, specifies the end
of the custom time period.

149
Metadata Components Report

Field Field Type Description

interval UserDateInterval Required. Specifies the period of time.
(enumeration of type string)
startDate date When interval is INTERVAL_CUSTOM, specifies the start
of the custom time period.

UserDateInterval
An enumeration of type string that defines the period of time. Valid values:

Enumeration Value Description

INTERVAL_CURRENT Current fiscal quarter
INTERVAL_CURNEXT1 Current and next fiscal quarters
INTERVAL_CURPREV1 Current and previous fiscal quarters
INTERVAL_NEXT1 Next fiscal quarter
INTERVAL_PREV1 Previous fiscal quarter
INTERVAL_CURNEXT3 Current and next three fiscal quarters
INTERVAL_CURFY Current fiscal year
INTERVAL_PREVFY Previous fiscal year
INTERVAL_PREV2FY Previous two fiscal years
INTERVAL_AGO2FY Two fiscal years ago
INTERVAL_NEXTFY Next fiscal year
INTERVAL_PREVCURFY Current and previous fiscal years
INTERVAL_PREVCUR2FY Current and previous two fiscal years
INTERVAL_CURNEXTFY Current and next fiscal year
INTERVAL_CUSTOM A custom time period. Use startDate and endDate fields to specify the time period's
start date and end date.
INTERVAL_YESTERDAY Yesterday
INTERVAL_TODAY Today
INTERVAL_TOMORROW Tomorrow
INTERVAL_LASTWEEK Last calendar week
INTERVAL_THISWEEK This calendar week
INTERVAL_NEXTWEEK Next calendar week
INTERVAL_LASTMONTH Last calendar month
INTERVAL_THISMONTH This calendar month
INTERVAL_NEXTMONTH Next calendar month
INTERVAL_LASTTHISMONTH Current and previous calendar months

150
Metadata Components Report

Enumeration Value Description

INTERVAL_THISNEXTMONTH Current and next calendar months
INTERVAL_CURRENTQ Current calendar quarter
INTERVAL_CURNEXTQ Current and next calendar quarters
INTERVAL_CURPREVQ Current and previous calendar quarters
INTERVAL_NEXTQ Next calendar quarter
INTERVAL_PREVQ Previous calendar quarter
INTERVAL_CURNEXT3Q Current and next three calendar quarters
INTERVAL_CURY Current calendar year
INTERVAL_PREVY Previous calendar year
INTERVAL_PREV2Y Previous two calendar years
INTERVAL_AGO2Y Two calendar years ago
INTERVAL_NEXTY Next calendar year
INTERVAL_PREVCURY Current and previous calendar years
INTERVAL_PREVCUR2Y Current and previous two calendar years
INTERVAL_CURNEXTY Current and next calendar years
INTERVAL_LAST7 Last 7 days
INTERVAL_LAST30 Last 30 days
INTERVAL_LAST60 Last 60 days
INTERVAL_LAST90 Last 90 days
INTERVAL_LAST120 Last 120 days
INTERVAL_NEXT7 Next 7 days
INTERVAL_NEXT30 Next 30 days
INTERVAL_NEXT60 Next 60 days
INTERVAL_NEXT90 Next 90 days
INTERVAL_NEXT120 Next 120 days
LAST_FISCALWEEK When custom fiscal years are enabled: Last fiscal week
THIS_FISCALWEEK When custom fiscal years are enabled: This fiscal week
NEXT_FISCALWEEK When custom fiscal years are enabled: Next fiscal week
LAST_FISCALPERIOD When custom fiscal years are enabled: Last fiscal period
THIS_FISCALPERIOD When custom fiscal years are enabled: This fiscal period
NEXT_FISCALPERIOD When custom fiscal years are enabled: Next fiscal period
LASTTHIS_FISCALPERIOD When custom fiscal years are enabled: This fiscal period and last fiscal period
THISNEXT_FISCALPERIOD When custom fiscal years are enabled: This fiscal period and next fiscal period

151
Metadata Components Report

Declarative Metadata Sample Definition

A sample XML report definition:

<?xml version="1.0" encoding="UTF-8"?>

<Report xmlns="http://soap.sforce.com/2006/04/metadata">
<aggregates>
<calculatedFormula>AMOUNT:SUM + OPP_QUANTITY:SUM</calculatedFormula>
<datatype>number</datatype>
<developerName>FORMULA1</developerName>
<isActive>true</isActive>
<masterLabel>CSF Hello</masterLabel>
<scale>2</scale>
</aggregates>
<chart>
<backgroundColor1>#FFFFFF</backgroundColor1>
<backgroundColor2>#FFFFFF</backgroundColor2>
<backgroundFadeDir>Diagonal</backgroundFadeDir>
<chartType>HorizontalBarGrouped</chartType>
<groupingColumn>CLOSE_DATE</groupingColumn>
<legendPosition>Right</legendPosition>
<location>CHART_BOTTOM</location>
<secondaryGroupingColumn>INDUSTRY</secondaryGroupingColumn>
<showAxisLabels>true</showAxisLabels>
<size>Medium</size>
<summaryAggregate>Average</summaryAggregate>
<summaryAxisManualRangeEnd>40.0</summaryAxisManualRangeEnd>
<summaryAxisManualRangeStart>5.0</summaryAxisManualRangeStart>
<summaryAxisRange>Manual</summaryAxisRange>
<summaryColumn>AMOUNT</summaryColumn>
<textColor>#000000</textColor>
<textSize>12</textSize>
<title>My Chart</title>
<titleColor>#000000</titleColor>
<titleSize>18</titleSize>
</chart>
<colorRanges>
<aggregate>Average</aggregate>
<columnName>AMOUNT</columnName>
<highBreakpoint>5678.0</highBreakpoint>
<highColor>#54C254</highColor>
<lowBreakpoint>1234.0</lowBreakpoint>
<lowColor>#6716EF</lowColor>
<midColor>#C2C254</midColor>
</colorRanges>
<colorRanges>
<columnName>RowCount</columnName>
<highBreakpoint>100.0</highBreakpoint>
<highColor>#54C254</highColor>
<lowBreakpoint>30.0</lowBreakpoint>
<lowColor>#C25454</lowColor>
<midColor>#C2C254</midColor>
</colorRanges>
<columns>
<field>FULL_NAME</field>
</columns>
<columns>
<field>OPPORTUNITY_NAME</field>
</columns>
<columns>
<field>TYPE</field>
</columns>
<columns>
<aggregateTypes>Sum</aggregateTypes>
<aggregateTypes>Average</aggregateTypes>
<field>AMOUNT</field>
</columns>

152
Metadata Components Report

<columns>
<field>CLOSE_DATE</field>
</columns>
<columns>
<field>STAGE_NAME</field>
</columns>
<columns>
<field>ROLLUP_DESCRIPTION</field>
</columns>
<columns>
<field>CREATED_DATE</field>
</columns>
<columns>
<field>PRODUCT_NAME</field>
</columns>
<columns>
<field>QUANTITY</field>
</columns>
<columns>
<field>UNIT_PRICE</field>
</columns>
<columns>
<field>TOTAL_PRICE</field>
</columns>
<columns>
<field>SERVICE_DATE</field>
</columns>
<columns>
<field>SERVICE_MONTH</field>
</columns>
<columns>
<field>PRODUCT_DESCRIPTION</field>
</columns>
<columns>
<field>PRODUCT_PRICE</field>
</columns>
<columns>
<field>PRODUCT_CUSTOMER_ID</field>
</columns>
<columns>
<field>PRODUCT_ACTIVE</field>
</columns>
<columns>
<field>ACCOUNT_NAME</field>
</columns>
<currency>AED</currency>
<filter>
<booleanFilter>(1 or 2 or 3 or 4 or 5 or 6)</booleanFilter>
<criteriaItems>
<column>AMOUNT</column>
<operator>greaterThan</operator>
<value>USD 1000.0</value>
</criteriaItems>
<criteriaItems>
<column>ACCOUNT_NAME</column>
<operator>startsWith</operator>
<value>Acme</value>
</criteriaItems>
<criteriaItems>
<column>OPPORTUNITY.CURRENCY_ISO_CODE</column>
<operator>equals</operator>
<value>USD,GBP,ADP</value>
</criteriaItems>
<criteriaItems>
<column>FORECAST_CATEGORY</column>
<operator>equals</operator>
<value>Omitted,Pipeline</value>

153
Metadata Components ReportType

</criteriaItems>
<criteriaItems>
<column>Account.Animal__c</column>
<operator>equals</operator>
<value>Dog;Cow,Cat;Pig</value>
</criteriaItems>
<criteriaItems>
<column>STAGE_NAME</column>
<operator>equals</operator>
<value>Prospecting</value>
</criteriaItems>
<language>en_US</language>
</filter>
<format>Matrix</format>
<groupingsAcross>
<field>INDUSTRY</field>
<sortOrder>Asc</sortOrder>
</groupingsAcross>
<groupingsDown>
<dateGranularity>Month</dateGranularity>
<field>CLOSE_DATE</field>
<sortOrder>Asc</sortOrder>
</groupingsDown>
<name>Simple Opportunity Report</name>
<params>
<name>open</name>
<value>all</value>
</params>
<params>
<name>probability</name>
<value>>0</value>
</params>
<reportType>OpportunityProduct</reportType>
<scope>organization</scope>
<showDetails>true</showDetails>
<timeFrameFilter>
<dateColumn>CLOSE_DATE</dateColumn>
<interval>INTERVAL_CURRENT</interval>
</timeFrameFilter>
</Report>

Declarative Metadata File Suffix and Directory Location

The file suffix is .reportType for the custom report type definition. There is one file per custom report type. Report types are
stored in the reportTypes directory of the corresponding package directory.

Version
Custom report types are available in API version 14.0 and later.

154
Metadata Components ReportType

Fields

Field Name Field Type Description

baseObject string Required.The primary object for the custom report type, for example,
Account. All objects, including custom objects, are supported. You
cannot edit this field after initial creation.
category ReportTypeCategory Required. This field controls the category for the report in the report
(enumeration of type string) wizard. The valid values are:
• accounts
• opportunities
• forecasts
• cases
• leads
• campaigns
• activities
• busop
• products
• admin
• territory
• other
• content

deployed boolean Required. Indicates whether the report type is available for use in
the report wizard (true) or whether it's still in development
(false).
description string The description of the custom report type.
fullName string The report type developer name used as a unique identifier for API
access. The fullName can only contain characters, letters, and the
underscore (_) character, must start with a letter, and cannot end
with an underscore or contain two consecutive underscore characters.
join ObjectRelationship The object joined to the baseObject. For example, Contacts may
be joined to the primary Accounts object.
label string Required. The report type label.
sections ReportLayoutSection[] The groups of columns available for the report type. Though columns
are not strictly required, a report without columns is not very useful.

ObjectRelationship
ObjectRelationship represents a join to another object. For more information, see "Choosing the Object Relationships that
Display on Reports Created from Custom Report Types" in the Salesforce online help.

Field Name Field Type Description

join ObjectRelationship This field is a recursive reference that allows you to join more than two
objects. A maximum of four objects can be joined in a custom report type.
When more than two objects are joined, an inner join is not allowed if
there has been an outer join earlier in the join sequence. The baseObject

155
Metadata Components ReportType

Field Name Field Type Description

is first joined to the object specified in relationship; the resulting data
set is then joined with any objects specified in this field.
outerJoin boolean Required. Indicates whether this is an outer join (true) or not (false).
An outer join returns a row even if the joined table does not contain a
matching value in the join column.
relationship string Required. The object joined to the primary object; for example, Contacts.

ReportLayoutSection
ReportLayoutSection represents a group of columns used in the custom report type.

Field Name Field Type Description

columns ReportTypeColumn[] The list of columns projected from the query, defined
by this custom report type.
masterLabel string Required. The label for this group of columns in the
report wizard.

ReportTypeColumn
ReportTypeColumn represents a column in the custom report type.

Field Name Field Type Description

checkedByDefault boolean Required. Indicates whether this column is selected be default (true) or
not (false).
displayNameOverride string A customized column name, if desired.
field string Required. The field name associated with the report column.
table string Required. The table associated with the field; for example, Account.

Declarative Metadata Sample Definition

The definition of a custom report type is shown below. Account is joined to Contacts and the resulting data set is joined with
Assets.

<?xml version="1.0" encoding="UTF-8"?>

<ReportType xmlns="http://soap.sforce.com/2006/04/metadata">
<baseObject>Account</baseObject>
<category>accounts</category>
<deployed>true</deployed>
<description>Account linked to Contacts and Assets</description>
<join>
<join>
<outerJoin>false</outerJoin>
<relationship>Assets</relationship>
</join>
<outerJoin>false</outerJoin>
<relationship>Contacts</relationship>
</join>
<label>Account Contacts and Assets</label>
<sections>

156
Metadata Components Scontrol

<columns>
<checkedByDefault>true</checkedByDefault>
<field>obj_lookup__c.Id</field>
<table>Account</table>
</columns>
<columns>
<checkedByDefault>false</checkedByDefault>
<field>obj_lookup__c.Name</field>
<table>Account</table>
</columns>
<columns>
<checkedByDefault>false</checkedByDefault>
<field>Opportunity__c.Amount</field>
<table>Account</table>
</columns>
<columns>
<checkedByDefault>false</checkedByDefault>
<field>Owner.IsActive</field>
<table>Account</table>
</columns>
<masterLabel>Accounts</masterLabel>
</sections>
<sections>
<columns>
<checkedByDefault>false</checkedByDefault>
<field>Owner.Email</field>
<table>Account.Contacts</table>
</columns>
<columns>
<checkedByDefault>false</checkedByDefault>
<field>byr__c</field>
<table>Account.Contacts</table>
</columns>
<columns>
<checkedByDefault>true</checkedByDefault>
<field>ReportsTo.CreatedBy.Contact.Owner.MobilePhone</field>
<table>Account.Contacts</table>
</columns>
<masterLabel>Contacts</masterLabel>
</sections>
</ReportType>

Scontrol
Represents an Scontrol component, corresponding to an s-control in the Salesforce user interface. For more information, see
"About S-Controls" in the Salesforce online help. This metadata type extends the MetadataWithContent component and
shares its fields.

Declarative Metadata File Suffix and Directory Location

The file suffix is .scf for the s-control file. The accompanying metadata file is named ScontrolName-meta.xml.
Scontrol components are stored in the scontrols folder in the corresponding package directory.

Version
Scontrols are available in API version 10.0 and later.

157
Metadata Components Scontrol

Fields
This metadata type contains the following fields:

Field Name Field Type Description

content base64Binary Content of the s-control. Base 64-encoded binary data. Prior to
making an API call, client applications must encode the binary
attachment data as base64. Upon receiving a response, client
applications must decode the base64 data to binary. This
conversion is usually handled for you by a SOAP client. This
field is inherited from the MetadataWithContent component.
contentSource SControlContentSource Required. Determines how you plan to use the s-control:
(enumeration of type string) • HTML: Select this option if you want to enter the content for
your s-control in content.
• URL: Select this option if you want to enter the link or URL
of an external website in content.
• Snippet: Snippets are s-controls that are designed to be
included in other s-controls. Select this option if you want to
enter the content for your s-control snippet in content.

description string Optional text that describes the s-control. This only displays to
users with "View All Data" permission (administrator).
encodingKey Encoding (enumeration of type Required. The default encoding setting is Unicode: UTF-8.
string) Change it if you are passing information to a URL that requires
data in a different format. This option is available when you select
URL as the value for contentSource.
fileContent base64 File contents displayed if you add this s-control to a custom link.
The file can contain a Java applet, Active-X control, or any other
type of content you want. This option only applies to s-controls
with a value of HTML for contentSource.
fileName string The unique name for the s-control. It must contain alphanumeric
characters only and begin with a letter. This field cannot be
changed for components installed by a managed package. It is
only relevant if the fileContent field also has a value. This is
a new field in API version 14.0.
fullName string The s-control developer name used as a unique identifier for API
access. The fullName can only contain characters, letters, and the
underscore (_) character, must start with a letter, and cannot end
with an underscore or contain two consecutive underscore
characters. If this field contained characters before version 14.0
that are no longer allowed, the characters were stripped out of
this field, and the previous value of the field was saved in the
name field. This field is inherited from the Metadata component.

name string Required. The unique name for the s-control. It must contain
alphanumeric characters only and begin with a letter. For example
example_s_control.
supportsCaching boolean Required. Indicates whether the s-control supports caching
(true) or not (false). Caching optimizes the page so that it

158
Metadata Components StaticResource

Field Name Field Type Description

remembers which s-controls are on the page when it reloads. This
option only applies to HTML s-controls.

Declarative Metadata Sample Definition

The following sample creates the Myriad_Publishing.scf s-control, which creates a link to the website specified in
the s-control. The corresponding Myriad_Publishing.scf-meta.xml metadata file follows the s-control file.
Myriad_Publishing.scf file:

http://www.myriadpubs.com

Myriad_Publishing.scf-meta.xml:

<?xml version="1.0" encoding="UTF-8"?>

<Scontrol xmlns="http://soap.sforce.com/2006/04/metadata">
<contentSource>URL</contentSource>
<description>s-control to open Myriad Publishing website.</description>
<encodingKey>UTF-8</encodingKey>
<name>Myriad Publishing</name>
<supportsCaching>true</supportsCaching>
</Scontrol>

StaticResource
Represents a static resource file, often a code library in a ZIP file. This metadata type extends the MetadataWithContent
component and shares its fields.
Static resources allow you to upload content that you can reference in a Visualforce page, including archives (such as .zip and
.jar files), images, stylesheets, JavaScript, and other files.

File Suffix and Directory Location

The file suffix is .resource for the template file. The accompanying metadata file is named resource-meta.xml.
Static resource components are stored in the staticresources folder in the corresponding package directory.

Version
Static resources are available in API version 12.0 and later.

Fields
This metadata type contains the following fields:

Field Name Field Type Description

cacheControl StaticResourceCacheControl Required. Indicates whether the static resource is marked with a public
(enumeration of type string) caching tag so that a third-party delivery client can cache the content. This
is a new field in API version 14.0. The valid values are:
• Private
• Public

159
Metadata Components Translations

Field Name Field Type Description

content base64Binary The static resource content. Base 64-encoded binary data. Prior to making
an API call, client applications must encode the binary attachment data as
base64. Upon receiving a response, client applications must decode the
base64 data to binary. This conversion is usually handled for you by a
SOAP client. This field is inherited from the MetadataWithContent
component.
contentType string Required. The content type of the file, for example text/plain.
description string The description of the static resource.
fullName string The static resource name. The name can only contain characters, letters,
and the underscore (_) character, must start with a letter, and cannot end
with an underscore or contain two consecutive underscore characters.
Inherited from the Metadata component, this field is not defined in the
WSDL for this component. It must be specified when creating, updating,
or deleting. See create() to see an example of this field specified for a
call.

Declarative Metadata Sample Definition

<?xml version="1.0" encoding="UTF-8"?>

<StaticResource xmlns="http://soap.sforce.com/2006/04/metadata">
<contentType>text/plain</contentType>
<description>Test Resource</description>
</StaticResource>

Translations
This metadata type allows you to work with translations for a variety of languages. The supported languages are listed in
Language on page 160. It extends the Metadata metadata type and inherits its fullName field. The ability to translate component
labels is part of the Translation Workbench. For more information, see "Setting Up Translation Workbench" in the Salesforce
online help.

Language
The translation languages supported are identified by a five-character locale code or a two-character language code. These
codes are listed in the table below. A complete locale includes a two-character ISO language code, followed by an underscore
(_) and a two-character ISO country code. For example, the locale is “en_US” for the United States. Some of the locales below
only specify a two-character ISO language code, for example “fr.”

Locale Code Language

cs Czech
da Danish
de German
en_US English (United States)

160
Metadata Components Translations

Locale Code Language

es Spanish
fi Finnish
fr French
hu Hungarian
in Indonesian
it Italian
ja Japanese
ko Korean
nl_NL Dutch
pl Polish
pt_BR Portuguese (Brazilian)
sv Swedish
th Thai
tr Turkish
zh_CN Chinese (Simplified)
zh_TW Chinese (Traditional)

Declarative Metadata File Suffix and Directory Location

Translations are stored in a file with a format of localeCode.translation, where localeCode is the locale code of the
translation language. For example, the file name for German translations is de.translation. The supported locale codes are
listed in Language on page 160.
Custom object translations are stored in the translations folder in the corresponding package directory.

Version
Translations components are available in API version 14.0 and later.

Fields

Field Field Type Description

customApplications CustomApplicationTranslation[] A list of custom application translations.
customLabels CustomLabelTranslation[] A list of custom label translations.
customPageWebLinks CustomPageWebLinkTranslation[] A list of translations for web links defined in a home
page component.
customTabs CustomTabTranslation[] A list of custom tab translations.

161
Metadata Components Translations

Field Field Type Description

fullName string Required. The language code; for example, de for
German.
Inherited from Metadata, this field is not defined in
the WSDL for this metadata type. It must be
specified when creating, updating, or deleting. See
create() to see an example of this field specified
for a call.

reportTypes ReportTypeTranslation[] A list of report type translations.

scontrols ScontrolTranslation[] A list of s-control translations.

CustomApplicationTranslation
CustomApplicationTranslation contains details for a custom application translation. For more details, see CustomApplication
on page 68.

Field Field Type Description

label string Required. The translated custom application name.
Maximum of 765 characters.
name string Required. Name of the custom application.

CustomLabelTranslation
CustomLabelTranslation contains details for a custom label translation. For more details, see CustomLabels on page 69.

Field Field Type Description

label string Required. The translated custom label name. Maximum of
765 characters.
name string Required. The custom label name.

CustomPageWebLinkTranslation
CustomPageWebLinkTranslation contains details for a translation of a web link defined in a home page component. For
more details, see CustomPageWebLink on page 100.

Field Field Type Description

label string Required. The translated web link.
name string Required. Name of the web link.

CustomTabTranslation
CustomTabTranslation contains details for a translation of a custom tab. For more details, see CustomTab on page 106.

162
Metadata Components Translations

Field Field Type Description

label string Required. The translated custom tab name.
name string Required. Custom tab name.

ReportTypeTranslation
ReportTypeTranslation contains details for a translation of a custom report type. For more details, see ReportType on page
154.

Field Field Type Description

description string The translated report type description.
label string The translated report type name.
name string Required. The name of the report type.
sections ReportTypeSectionTranslation[] A list of report type section translations.

ReportTypeSectionTranslation
ReportTypeSectionTranslation contains details for a report type section translation.

Field Field Type Description

columns ReportTypeColumnTranslation[] A list of report type column translations.
label string The translated report type section name.
name string Required.The name of the report type section.

ReportTypeColumnTranslation
ReportTypeColumnTranslation contains details for a report type column translation.

Field Field Type Description

label string Required. The translated report type column name.
name string Required. The report type column name.

ScontrolTranslation
ScontrolTranslation contains details for a translation of an s-control. For more information, see "About S-Controls" in the
Salesforce online help.

Field Field Type Description

label string Required. The translated s-control name.
name string Required. The name of the s-control.

163
Metadata Components Workflow

Declarative Metadata Sample Definition

A sample XML definition of a translations component is shown below.

<?xml version="1.0" encoding="UTF-8"?>

<Translations xmlns="http://soap.sforce.com/2006/04/metadata">
<customApplications>
<label>Anführungsstrich-Manager</label>
<name>Quote Manager</name>
</customApplications>
<customLabels>
<label>Dieses ist ein manueller Anführungsstrich</label>
<name>quoteManual</name>
</customLabels>
</Translations>

Declarative Metadata File Suffix and Directory Location

The file suffix is .workflow for the workflow file. There is one file per standard or custom object that has workflow, which are
stored in the workflows directory of the corresponding package.

Version
Workflow rules are available in API version 13.0 and later.

Workflow
This metadata type represents the valid types of workflow rules and actions associated with a standard or custom object.

Field Name Field Type Description

alerts WorkflowAlert[] An array of all alerts for the object associated with the
workflow.
fieldUpdates WorkflowFieldUpdate[] An array of all field updates for the object associated with
the workflow.

164
Metadata Components Workflow

Field Name Field Type Description

fullName string The developer name used as a unique identifier for API
access. The fullName can only contain characters, letters,
and the underscore (_) character, must start with a letter,
and cannot end with an underscore or contain two
consecutive underscore characters. This field is inherited
from the Metadata component.
outboundMessages WorkflowOutboundMessage[] An array of all of the outbound messages for the object
associated with the workflow.
rules WorkflowRule[] An array of all the object associated with the workflow.
tasks WorkflowTask[] An array of all the tasks for the object associated with the
workflow.

WorkflowAlert
WorkflowAlert represents an email alert associated with a workflow rule.

Field Name Field Type Description

ccEmails string[] Additional CC email addresses.
fullName string The developer name used as a unique identifier for API
access. The fullName can only contain characters, letters,
and the underscore (_) character, must start with a letter,
and cannot end with an underscore or contain two
consecutive underscore characters. This field is inherited
from the Metadata component.
protected boolean Required. Indicates whether this component is protected
(true) or not (false). Protected components cannot
be linked to or referenced by components created in the
installing organization.
recipients WorkflowEmailRecipient[] The recipients for the email.
template string Required. Named reference to an EmailTemplate. This
email template does not have to exist in the zip file, but
it must exist in the metadata API.

WorkflowEmailRecipient
WorkflowEmailRecipient represents a recipient for an email alert associated with a workflow rule.

Field Name Field Type Description

field string Name of the field referenced in type. The field named
should be of the type specified in type.
recipient string The recipients for the email. Depending on the type
selected, this may be required.

165
Metadata Components Workflow

Field Name Field Type Description

type ActionEmailRecipientTypes Named reference to an EmailTemplate component. Valid
(enumeration of type string) values are:
• accountOwner - The email is sent to the record's
account owner (for example, the Account owner for an
Opportunity).
• accountTeam - Only applicable on the Account
object. The email is sent to everyone on that Account's
account team.
• contactLookup - The email is sent to a contact
whose value is looked up from a field on the record. For
this value, the field field must reference a Contact.
• creator - The email is sent to the record's creator.
• customerPortalOwner - The email is sent to a
specific self-service portal user. For this value, the
recipient field must reference a User (by username),
only self-service portal users.
• email - The email is sent to an email address whose
value is looked up from a field on the record. For this
value, the field field must reference an email field.
• group - The email is sent to all users in a group. For
this value, the recipient field must reference a group (by
group name).
• opportunityTeam - Only applicable on the
Opportunity object. The email is sent to everyone on
that Opportunity's sales team.
• owner - The email is sent to the record's owner.
• partnerUser - The email is sent to a specific partner
user. For this value, the recipient field must reference
a User (by username), only partner users.
• portalRole - Like role, but for portal roles only.
• portalRoleSubordinates - Like
roleSubordinates, but for portal roles only.
• role - The email is sent to all users in a role. For this
value, the recipient field must reference a Role (in the
role hierarchy, by role name).
• roleSubordinates - The email is sent to all users
in a role subordinates. For this value, the recipient field
must reference a Role.
• roleSubordinatesInternal - Like
roleSubordinates, but for internal portal roles
only
• user - The email is sent to a specific user. For this
value, the recipient field must reference a User (by
username)
• userLookup - The email is sent to a user whose value
is looked up from a field on the record. For this value,
the field field must reference a user foreign key field.

166
Metadata Components Workflow

WorkflowFieldUpdate
WorkflowFieldUpdate represents a workflow field update. Field updates allow you to automatically update a field value to
one that you specify when a workflow rule is triggered. For more information, see "Defining Field Updates" in the Salesforce
online help.

Field Name Field Type Description

description string The description of the field update. This information is useful
to track the reasoning for initially configuring the field update.
field string Required. The field (on the object for the workflow) to be
updated.
formula string If the operation field value is Formula, this is set to a
formula used to compute the new field value.
fullName string The developer name used as a unique identifier for API access.
The fullName can only contain characters, letters, and the
underscore (_) character, must start with a letter, and cannot
end with an underscore or contain two consecutive underscore
characters. This field is inherited from the Metadata
component.
literalValue string If the operation field value is Literal, this is the literal
value for the field.
lookupValue string If the operation field value is lookupValue, this is the
lookup value that is referenced.
lookupValueType LookupValueType The type of object that the lookupValue field value is
(enumeration of type string) referencing. The valid values are:
• Queue
• RecordType
• User

notifyAssignee boolean Required. Notify the assignee when the field is updated.
operation FieldUpdateOperation Required. The operation that computes the value with which
(enumeration of type string) to update the field. Valid values are:
• Formula - Indicates the field will be set to a formula. If
set, the formula must be a valid formula.
• Literal - Indicates the field will be set to a literal value.
If set, the literalValue must be a valid literal value for this
field.
• LookupValue - Similar to Literal, but for an object
reference, such as a contact, user, account, etc. If set, the
lookupValue element must be set. Only User is
supported in the current API.
• NextValue - Indicates the field will be set its next value;
this is only allowed when the field update references a
picklist.
• Null - Indicates the field will be set to null.
• PreviousValue - Indicates the field will be set its
previous value; this is only allowed when the field update
references a picklist.

167
Metadata Components Workflow

Field Name Field Type Description

protected boolean Required. Indicates whether this component is protected
(true) or not (false). Protected components cannot be
linked to or referenced by components created in the installing
organization.
targetObject string This is set if the change is detected on a child record. If this
is set, it points to the foreign key reference on the child object
(for example, EmailMessage.ParentId) pointing to
the parent (for example, Case). When set, the formula is
based on the child object (for example, EmailMessage).
This field is named sourceField before version 14.0. The
field name change is automatically handled between versions
and does not require any manual editing of existing XML
component files.

WorkflowOutboundMessage
WorkflowOutboundMessage represents an outbound message associated with a workflow rule. Outbound messages are
workflow and approval actions that send the information you specify to an endpoint you designate, such as an external service.
An outbound message sends the data in the specified fields in the form of a SOAP message to the endpoint. For more
information, see "Defining Outbound Messages" in the Salesforce online help.

Field Name Field Type Description

description string Describes the outbound message.
endpointUrl string Required. The endpoint URL to which the outbound message is
sent.
fields string[] The named references to the field that are to be sent.
fullName string The developer name used as a unique identifier for API access. The
fullName can only contain characters, letters, and the underscore
(_) character, must start with a letter, and cannot end with an
underscore or contain two consecutive underscore characters. This
field is inherited from the Metadata component.
includeSessionId boolean Required. Set if you want the Salesforce session ID included in the
outbound message. Useful if you intend to make API calls and you
do not want to include a username and password.
integrationUser string Required.The named reference to the user under which this message
is sent.
protected boolean Required. Indicates whether this component is protected (true)
or not (false). Protected components cannot be linked to or
referenced by components created in the installing organization.
useDeadLetterQueue boolean This field is only available for organizations with dead letter queue
permissions turned on. If set, this outbound message will use the
dead letter queue if normal delivery fails.

WorkflowRule
This metadata type represents a workflow rule. It extends the Metadata metadata type and inherits its fullName field.

168
Metadata Components Workflow

Field Name Field Type Description

actions WorkflowActionReference[] An array of references for the actions that should happen
when this rule fires.
active boolean Required. Determines if this rule is active.
booleanFilter string For advanced criteria filter, the boolean formula, for
example, (1 AND 2) OR 3.
criteriaItems FilterItem[] An array of the boolean criteria (conditions) under which
this rule fires. Note that either this or formula must be
set.
description string The description of the workflow rule
formula string The formula condition under which this rule first (either
this or criteriaItems must be set)
fullName string The developer name used as a unique identifier for API
access. The fullName can only contain characters, letters,
and the underscore (_) character, must start with a letter,
and cannot end with an underscore or contain two
consecutive underscore characters. This field is inherited
from the Metadata component.
triggerType WorkflowTriggerTypes Under what conditions the trigger fires. Valid values are:
(enumeration of type string) • onAllChanges - The workflow rule is considered on
all changes.
• onCreateOnly - The workflow rule is considered
only on create.
• onCreateOrTriggeringUpdate - The workflow
rule is considered on create and triggering update.

WorkflowActionReference
WorkflowActionReference represents one of the four workflow actions.

Field Name Field Type Description

name string Required. The name of the workflow action.
type WorkflowActionType Required. There are four types of workflow actions:
(enumeration of type • Alert
string) • FieldUpdate
• OutboundMessage
• Task

WorkflowTask
This metadata type references an assigned workflow task.

169
Metadata Components Workflow

Field Name Field Type Description

assignedTo string Specifies the user, role, or team to which the workflow
rule or action is assigned. The field corresponding to
the value specified here must be the same as the
specified assignedToType.
assignedToType ActionTaskAssignedToTypes Valid string values for this type are:
(enumeration of type string) • accountCreator - When set, the task is
assigned to the record's account's creator.
• accountOwner - When set, the task is assigned
to the record's account's owner (Opportunity).
• accountTeam - Same as WorkflowAlert type
• creator - When set, the task is assigned to the
record's creator.
• opportunityTeam - Same as WorkflowAlert
type
• owner - When set, the task is assigned to the
record's owner.
• partnerUser - When set, the assignedTo field
references a User (by username), a partner user.
• portalRole - When set, the assignedTo field
references a Role (by role name), a portal role.
• role - When set, the assignedTo field references
a Role (by role name)
• user - When set, the assignedTo field references
a User (by username)

description string The description of this workflow task.

dueDateOffset int Required. The offset, in days, from either the trigger
date, or the date specified in the (optional)
offsetFromField. This can be a negative number.

fullName string The developer name used as a unique identifier for API
access. The fullName can only contain characters,
letters, and the underscore (_) character, must start
with a letter, and cannot end with an underscore or
contain two consecutive underscore characters. This
field is inherited from the Metadata component.
notifyAssignee boolean Required. Set to send an email notification when the
task is assigned.
offsetFromField string Optional field reference of the date field from which
the dueDate should be computed.
priority string Required. The priority to assign the created task.
protected boolean Required. Indicates whether this component is
protected (true) or not (false). Protected
components cannot be linked to or referenced by
components created in the installing organization.
status string Required. The status to assign the created task.

170
Metadata Components Workflow

Declarative Metadata Sample Definition

The following is the definition of a workflow rule:

<?xml version="1.0" encoding="UTF-8"?>

<Workflow xmlns="http://soap.sforce.com/2006/04/metadata">
<alerts>
<fullName>AnotherAlert</fullName>
<protected>false</protected>
<recipients>
<type>accountOwner</type>
</recipients>
<recipients>
<field>Contact__c</field>
<type>contactLookup</type>
</recipients>
<recipients>
<field>Email__c</field>
<type>email</type>
</recipients>
<template>TestEmail/Email Test</template>
</alerts>
<fieldUpdates>
<fullName>EnumFieldUpdate</fullName>
<description>Blah</description>
<field>EnumField__c</field>
<notifyAssignee>true</notifyAssignee>
<operation>NextValue</operation>
<protected>false</protected>
</fieldUpdates>
<fieldUpdates>
<fullName>EnumFieldUpdate2</fullName>
<description>Blah</description>
<field>EnumField__c</field>
<literalValue>PLX2</literalValue>
<notifyAssignee>true</notifyAssignee>
<operation>Literal</operation>
<protected>false</protected>
</fieldUpdates>
<fieldUpdates>
<fullName>FieldUpdate</fullName>
<description>TestField update desc</description>
<field>Name</field>
<formula>Name & "Updated"</formula>
<notifyAssignee>false</notifyAssignee>
<operation>Formula</operation>
<protected>false</protected>
</fieldUpdates>
<fieldUpdates>
<fullName>LookupOnContact</fullName>
<field>RealOwner__c</field>
<lookupValue>admin@acme.com</lookupValue>
<notifyAssignee>false</notifyAssignee>
<operation>LookupValue</operation>
<protected>false</protected>
</fieldUpdates>
<outboundMessages>
<fullName>AnotherOutbound</fullName>
<description>Another Random outbound.</description>
<endpointUrl>http://www.test.com</endpointUrl>
<fields>Email__c</fields>
<fields>Id</fields>
<fields>Name</fields>
<includeSessionId>true</includeSessionId>
<integrationUser>admin@acme.com</integrationUser>
<protected>false</protected>
</outboundMessages>

171
Metadata Components Workflow

<rules>
<fullName>BooleanFilter</fullName>
<active>false</active>
<booleanFilter>1 AND 2 OR 3</booleanFilter>
<criteriaItems>
<field>CustomObjectForWorkflow__c.CreatedById</field>
<operation>notEqual</operation>
</criteriaItems>
<criteriaItems>
<field>CustomObjectForWorkflow__c.CreatedById</field>
<operation>notEqual</operation>
<value>abc</value>
</criteriaItems>
<criteriaItems>
<field>CustomObjectForWorkflow__c.CreatedById</field>
<operation>equals</operation>
<value>xyz</value>
</criteriaItems>
<triggerType>onCreateOrTriggeringUpdate</triggerType>
</rules>
<rules>
<fullName>Custom Rule1</fullName>
<actions>
<name>AnotherAlert</name>
<type>Alert</type>
</actions>
<actions>
<name>EnumFieldUpdate2</name>
<type>FieldUpdate</type>
</actions>
<actions>
<name>FieldUpdate</name>
<type>FieldUpdate</type>
</actions>
<active>true</active>
<criteriaItems>
<field>CustomObjectForWorkflow__c.Name</field>
<operation>startsWith</operation>
<value>ABC</value>
</criteriaItems>
<description>Custom Rule1 desc</description>
<triggerType>onCreateOrTriggeringUpdate</triggerType>
</rules>
<rules>
<fullName>IsChangedFunctionRule</fullName>
<active>true</active>
<description>IsChangedDesc</description>
<formula>ISCHANGED(Name)</formula>
<triggerType>onAllChanges</triggerType>
</rules>
<tasks>
<fullName>AnotherTask</fullName>
<assignedToType>owner</assignedToType>
<description>Random Comment</description>
<dueDateOffset>20</dueDateOffset>
<notifyAssignee>true</notifyAssignee>
<priority>High</priority>
<protected>false</protected>
<status>Completed</status>
</tasks>
<tasks>
<fullName>RoleTask</fullName>
<assignedTo>R11</assignedTo>
<assignedToType>role</assignedToType>
<dueDateOffset>-2</dueDateOffset>
<notifyAssignee>true</notifyAssignee>
<offsetFromField>CustomObjectForWorkflow__c.CreatedDate</offsetFromField>

172
Metadata Components Workflow

<priority>High</priority>
<protected>false</protected>
<status>Completed</status>
</tasks>
<tasks>
<fullName>UserTask</fullName>
<assignedTo>admin@acme.com</assignedTo>
<assignedToType>user</assignedToType>
<dueDateOffset>-2</dueDateOffset>
<notifyAssignee>true</notifyAssignee>
<offsetFromField>User.CreatedDate</offsetFromField>
<priority>High</priority>
<protected>false</protected>
<status>Completed</status>
</tasks>
</Workflow>

173
Index

Index
A components (continued)
ValidationRule 90
ApexClass component 63 Workflow 164
ApexComponent component 64 create call (asynchronous) 24
ApexPage component 65 Custom report type component 154
ApexTrigger component 66 CustomApplication component 68
CustomDataType component 69
CustomField component 74
C CustomLabels component 69
calls CustomObject
checkDeployStatus 43 Weblink component 91
checkRetrieveStatus 54 CustomObject component 71
checkStatus 23 CustomObjectTranslation component 95
create (asynchronous) 24 CustomPageWebLink component 100
delete (asynchronous) 26 CustomSite component 103
deploy 36 CustomTab component 106
describeMetadata 58
listMetadata 60, 61 D
retrieve 48
retrieve request 55 Dashboard component 108
update (asynchronous) 28 Declarative development 32
checkDeployStatus metadata call 43 delete (asynchronous) call 26
checkRetrieveStatus metadata call 54 deploy call 36
checkStatus metadata call 23 describeMetadata call 58
components Document component 114
ApexClass 63
ApexComponent 64
ApexPage 65
E
ApexTrigger 66 EmailTemplate component 115
CustomApplication 68 error handling 22
CustomDataType 69 expiration of session ID 22
CustomField 74
CustomFieldTranslation 95
CustomLabel 69 F
CustomLabels 69
CustomObject 71 field types 94
CustomObjectTranslation 95 File-based metadata 32
CustomPageWebLink 100 Folder component 118
CustomTab 106
Dashboard 108 H
Document 114
EmailTemplate 115 HomePageComponent component 119
Folder 118 HomePageLayout component 120
HomePageComponent 119
HomePageLayout 120
Layout 121
L
Letterhead 127 Layout component 121
ListView 79 Letterhead component 127
ListViewFilter 79 listMetadata call 60
Metadata 129 ListMetadataQuery 61
MetadataWithContent 130 ListView component 79
ObjectRelationship 154
Picklist 81
Profile 133 M
RecordType 84
ReportType 154 Metadata 32
Scontrol 157 metadata calls 3
SearchLayouts 86 Metadata component 129, 130
SharingReason 88 metadata components
SharingRecalculation 89 CustomSite 103
Static resource 159 Portal 131 174
Translations 160 Report 140
Index
Metadata components 62 Static resource component 159
support policy
backward compatibility 4
O call deprecation 4
outer join 154 deprecated calls 4
metadata API 4
supported calls 62
P
Picklist definitions 81 T
Portal component 131
Profile component 133 Translations component 160
types of fields 94

Q
U
quick start 6
understanding metadata calls and components
metadata 3
R update (asynchronous) call 28

RecordType component 84
Report component 140 V
retrieve call 48
retrieve request 55 ValidationRule component 90
Visualforce component, see ApexComponent 64
Visualforce page, see ApexPage 65
S
sample code 6 W
Scontrol component 157
SearchLayouts component 86 Weblink component of CustomObject 91
session ID expiration 22 Workflow component 164
SharingReason component 88 WSDL integration 6
SharingRecalculation component 89

175

ES.0.06.0021-C - Compilation and Handover of Project Dossier
100% (5)
ES.0.06.0021-C - Compilation and Handover of Project Dossier
34 pages
Epicor905 Install Guide SQL
No ratings yet
Epicor905 Install Guide SQL
112 pages
Making A SANS Index
100% (1)
Making A SANS Index
3 pages
Worksite Server Administrators Guide 8 5 For Imanage Server
0% (2)
Worksite Server Administrators Guide 8 5 For Imanage Server
382 pages
Top 50 Virtualization Security Questions
No ratings yet
Top 50 Virtualization Security Questions
20 pages
Ax2012 Enus Deviv 04 PDF
100% (1)
Ax2012 Enus Deviv 04 PDF
54 pages
SR-201 Network Relay Quick Start Guide
No ratings yet
SR-201 Network Relay Quick Start Guide
7 pages
BS en 16102 2011
No ratings yet
BS en 16102 2011
58 pages
Script Login & Logout (Macromedia Dreamweaver 8)
100% (2)
Script Login & Logout (Macromedia Dreamweaver 8)
5 pages
XXXX XXXX Salesforce Developer/Administrator XXX-XXX-XXXXXX
No ratings yet
XXXX XXXX Salesforce Developer/Administrator XXX-XXX-XXXXXX
7 pages
Introduction To Explicit Cursors
0% (1)
Introduction To Explicit Cursors
7 pages
Report On Banking Management System PDF Free 5 33
No ratings yet
Report On Banking Management System PDF Free 5 33
29 pages
Formal Verification of Smartcontracts
No ratings yet
Formal Verification of Smartcontracts
6 pages
Salesforce Data Loader
No ratings yet
Salesforce Data Loader
51 pages
API Design Ebook 2012 03
No ratings yet
API Design Ebook 2012 03
38 pages
Version 1: Winter '13
No ratings yet
Version 1: Winter '13
50 pages
Integration Workbook
No ratings yet
Integration Workbook
20 pages
SalesForce Certification Lab II
No ratings yet
SalesForce Certification Lab II
48 pages
Vigenere Cipher C#
No ratings yet
Vigenere Cipher C#
4 pages
Salesforce Security Notes For Certification
No ratings yet
Salesforce Security Notes For Certification
7 pages
Course 6: Entity Relationship Diagrams: 1. Basic Elements and Rules
No ratings yet
Course 6: Entity Relationship Diagrams: 1. Basic Elements and Rules
46 pages
1602505091unit 3 Cyber Security Tools & Techniques
No ratings yet
1602505091unit 3 Cyber Security Tools & Techniques
27 pages
1.what Is The Difference Between An Abstract Class and Interface?
No ratings yet
1.what Is The Difference Between An Abstract Class and Interface?
10 pages
Angular Notes
No ratings yet
Angular Notes
19 pages
Securing Communication of Legacy Applications with IPSec: Step-by-Step Guide to Protecting “Data in Transit” without Changes in Your Existing Software
From Everand
Securing Communication of Legacy Applications with IPSec: Step-by-Step Guide to Protecting “Data in Transit” without Changes in Your Existing Software
Slava Gomzin
No ratings yet
Dapr For NET Developers
No ratings yet
Dapr For NET Developers
178 pages
Er Diagram
No ratings yet
Er Diagram
1 page
Visualforce Workbook VF
No ratings yet
Visualforce Workbook VF
45 pages
Oracle Fusion Autolock Box
No ratings yet
Oracle Fusion Autolock Box
2 pages
Brana Web Guidline
No ratings yet
Brana Web Guidline
30 pages
REPORT Block Chain
No ratings yet
REPORT Block Chain
17 pages
BCS-011 Computer Basics and PC Software Solved Assignment 2019-2020
80% (10)
BCS-011 Computer Basics and PC Software Solved Assignment 2019-2020
11 pages
OpenSSO Architecture Overview
No ratings yet
OpenSSO Architecture Overview
14 pages
Bbanking Management System
No ratings yet
Bbanking Management System
31 pages
Dumpleader: Ensure Success With Money Back Guarantee
No ratings yet
Dumpleader: Ensure Success With Money Back Guarantee
5 pages
A Study On Removal Techniques of Cross-Site From Web Application
No ratings yet
A Study On Removal Techniques of Cross-Site From Web Application
7 pages
Salesforce Dumps
No ratings yet
Salesforce Dumps
6 pages
2E Payment System
No ratings yet
2E Payment System
23 pages
Advanced Application Express
No ratings yet
Advanced Application Express
65 pages
JD - Lead Salesforce Developer-2
No ratings yet
JD - Lead Salesforce Developer-2
2 pages
Amazon Web Services - Wikipedia, The Free Encyclopedia
No ratings yet
Amazon Web Services - Wikipedia, The Free Encyclopedia
8 pages
Declarative Model (Page Layouts, Recordtype, Workflows, Validation Rules)
No ratings yet
Declarative Model (Page Layouts, Recordtype, Workflows, Validation Rules)
2 pages
Webmethods Interview Quesstions
No ratings yet
Webmethods Interview Quesstions
1 page
Salesforce Extension Installation and Configuration Guide
No ratings yet
Salesforce Extension Installation and Configuration Guide
33 pages
Course Outline SPFX
No ratings yet
Course Outline SPFX
4 pages
Detection of Url Based Phishing Attacks Using Machine Learning IJERTV8IS110269
No ratings yet
Detection of Url Based Phishing Attacks Using Machine Learning IJERTV8IS110269
8 pages
Google Tokens
No ratings yet
Google Tokens
3 pages
App Builder Notes
No ratings yet
App Builder Notes
8 pages
BIRT 2.6 Data Analysis and Reporting
From Everand
BIRT 2.6 Data Analysis and Reporting
John Ward
2/5 (1)
Exam Ref 70-486 Developing ASP - Net MVC Web Applications 2nd Edition by James ChambersDavid PaquetteSimon Timms
0% (1)
Exam Ref 70-486 Developing ASP - Net MVC Web Applications 2nd Edition by James ChambersDavid PaquetteSimon Timms
4 pages
Cisco 2901 Router Datasheet
No ratings yet
Cisco 2901 Router Datasheet
15 pages
Creating Customized Panes in Syspro - Documentation
100% (1)
Creating Customized Panes in Syspro - Documentation
27 pages
AngularJS Notes
No ratings yet
AngularJS Notes
37 pages
Ethereum Attacks
No ratings yet
Ethereum Attacks
89 pages
Getting Started WIth SalesForce
No ratings yet
Getting Started WIth SalesForce
32 pages
Ultimatep2V: by Chris Huss and Mike Laverick
No ratings yet
Ultimatep2V: by Chris Huss and Mike Laverick
29 pages
Statistics Webservices Api Reference Guide
No ratings yet
Statistics Webservices Api Reference Guide
69 pages
Salesforce App Limits Cheatsheet
No ratings yet
Salesforce App Limits Cheatsheet
50 pages
Remix Ide
No ratings yet
Remix Ide
161 pages
Sky Computing
No ratings yet
Sky Computing
43 pages
MIS CRM Software
50% (2)
MIS CRM Software
18 pages
C# Collections
No ratings yet
C# Collections
62 pages
Ramakrishna Resume Feb13
No ratings yet
Ramakrishna Resume Feb13
2 pages
Your Personal Newspaper: Eye in The Sky For City Crime Fighting Can Bill Gates Prevent The Next Katrina?
No ratings yet
Your Personal Newspaper: Eye in The Sky For City Crime Fighting Can Bill Gates Prevent The Next Katrina?
3 pages
Sales Force Apex Language Reference Ver 15.0
100% (1)
Sales Force Apex Language Reference Ver 15.0
370 pages
Vedicmaths Ebook
100% (9)
Vedicmaths Ebook
212 pages
Nigeria Open Data Policy 1
No ratings yet
Nigeria Open Data Policy 1
17 pages
Microsoft SharePoint As A Digital Asset Management (DAM) System
No ratings yet
Microsoft SharePoint As A Digital Asset Management (DAM) System
38 pages
2024-06-01 04-24-27
No ratings yet
2024-06-01 04-24-27
12 pages
classificationk
No ratings yet
classificationk
7 pages
Easy Cost Planning in PS
No ratings yet
Easy Cost Planning in PS
6 pages
Oracle Fusion Applications Post-Installation Guide
No ratings yet
Oracle Fusion Applications Post-Installation Guide
124 pages
Introduction Into Luhmanns Zettelkasten Thinking
100% (2)
Introduction Into Luhmanns Zettelkasten Thinking
56 pages
Aarne Onni Tutkielma 2022
No ratings yet
Aarne Onni Tutkielma 2022
44 pages
What'S New in Ibm Infosphere Information Server 8.7
No ratings yet
What'S New in Ibm Infosphere Information Server 8.7
28 pages
Fast17 Full Proceedings
No ratings yet
Fast17 Full Proceedings
417 pages
A-Z of RAG Question Answering Methods in Langchain
No ratings yet
A-Z of RAG Question Answering Methods in Langchain
33 pages
Rohit Data Analyst Professional Summary
No ratings yet
Rohit Data Analyst Professional Summary
10 pages
Multidimensional Data Mode:-: Characteristics of Data Warehouse
100% (1)
Multidimensional Data Mode:-: Characteristics of Data Warehouse
26 pages
MDM 4
No ratings yet
MDM 4
159 pages
TCAP Grade 3 Math Item Release
No ratings yet
TCAP Grade 3 Math Item Release
20 pages
SSRN Id4166807
No ratings yet
SSRN Id4166807
19 pages
THE SAP® Business One Software Development Kit: SAP Functions in Detail
No ratings yet
THE SAP® Business One Software Development Kit: SAP Functions in Detail
24 pages
IEEE Standard For Learning
No ratings yet
IEEE Standard For Learning
50 pages
The Complete Manual
No ratings yet
The Complete Manual
152 pages
Lab 1 - Intro To Remote Sensing and EE
No ratings yet
Lab 1 - Intro To Remote Sensing and EE
8 pages
Test Bank for Database Concepts 9th Edition Kroenke - Download PDF
100% (6)
Test Bank for Database Concepts 9th Edition Kroenke - Download PDF
54 pages
wt2015 Echoprint
No ratings yet
wt2015 Echoprint
5 pages
FCE Listening Part 1 - Free Practice Test
100% (1)
FCE Listening Part 1 - Free Practice Test
1,019 pages
The Future of Python Packaging - Python Packaging User Guide Documentation
No ratings yet
The Future of Python Packaging - Python Packaging User Guide Documentation
3 pages
Next Generation Web Search: Setting Our Sites
No ratings yet
Next Generation Web Search: Setting Our Sites
11 pages
ImplementationandMaintenanceStudentGuide PDF
No ratings yet
ImplementationandMaintenanceStudentGuide PDF
168 pages
Data Warehouse-Ccs341 Material
No ratings yet
Data Warehouse-Ccs341 Material
58 pages
Name Four Common Misconceptions About Digital Preservation
No ratings yet
Name Four Common Misconceptions About Digital Preservation
6 pages