Metadata API Developer Guide
jNote: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.
DebugLevel
Represents a set of log category levels to assign to a TraceFlag object. Multiple trace flags can use a debug
level.
This type extends the Metadata metadata type and inherits its fullName field.
File Suffix and Directory Location
DebugLevel components have the suffix .debugLevel and are stored in the debugLevels folder.
Version
The DebugLevel metadata type is available in API version 68.0 and later.
Fields
| Name | Type | Description |
| apexCode | ApexLogLevel (enumeration of type string) | Required. The log category level for Apex code. Includes information about Apex
code. Can also include log messages generated by data manipulation language (DML)
statements, inline SOQL or SOSL queries, the start and completion of triggers, the
start and completion of test methods, and so on. The following are valid values.
|
| apexProfiling | ApexLogLevel (enumeration of type string) | Required. The log category level for profiling information. Includes cumulative
profiling information, such as the limits for your namespace, the number of emails
sent, and so on. The following are valid values.
|
| callout | ApexLogLevel (enumeration of type string) | Required. The log category level for callouts. Includes the request-response
XML that the server is sending and receiving from an external Web service. The
request-response XML is useful when debugging issues related to SOAP API calls. The
following are valid values.
|
| database | ApexLogLevel (enumeration of type string) | Required. The log category for database activity. Includes information about
database activity, including every DML statement or inline SOQL or SOSL query. The
following are valid values.
|
| dataAccess | ApexLogLevel (enumeration of type string) | The log category level for rules and policy information for objects accessed
from the UI, which can be used to determine why an object isn’t accessible.The
following are valid values.
|
| label | string | Required. The name for the debug level. Also displays in the Developer Console and in Setup. |
| nba | ApexLogLevel (enumeration of type string) | Required. The log category level for Einstein Next Best Action activity,
including strategy execution details from Strategy Builder. The following are valid values.
|
| system | ApexLogLevel (enumeration of type string) | Required. The log category level for calls to all system methods, such as the
System.debug method. The following are valid values.
|
| validation | ApexLogLevel (enumeration of type string) | Required. The log category level for validation rules. Includes information
about validation rules, such as the name of the rule, or whether the rule evaluated
true or false. The following are valid values.
|
| visualforce | ApexLogLevel (enumeration of type string) | Required. The log category level for Visualforce. Includes information about
Visualforce events, including serialization and deserialization of the view state or
the evaluation of a formula field in a Visualforce page. The following are valid values.
|
| wave | ApexLogLevel (enumeration of type string) | Required. The log category level for CRM Analytics. Includes information such
as template processing errors and rules execution summaries. The following are valid values.
|
| workflow | ApexLogLevel (enumeration of type string) | Required. The log category level for workflow rules. Includes information for
workflow rules, such as the rule name and the actions taken. The following are valid values.
|
Declarative Metadata Sample Definition
The following is an example of a DebugLevel component.
1<?xml version="1.0" encoding="UTF-8"?>
2<DebugLevel xmlns="http://soap.sforce.com/2006/04/metadata">
3 <label>DebugLevel</label>
4 <apexCode>DEBUG</apexCode>
5 <apexProfiling>INFO</apexProfiling>
6 <callout>FINEST</callout>
7 <database>INFO</database>
8 <dataAccess>INFO</dataAccess>
9 <nba>INFO</nba>
10 <system>DEBUG</system>
11 <validation>INFO</validation>
12 <visualforce>INFO</visualforce>
13 <wave>INFO</wave>
14 <workflow>FINEST</workflow>
15</DebugLevel>The following is an example package.xml manifest that references the previous definition.
1<?xml version="1.0" encoding="UTF-8"?>
2<Package xmlns="http://soap.sforce.com/2006/04/metadata">
3 <types>
4 <members>*</members>
5 <name>DebugLevel</name>
6 </types>
7 <version>68.0</version>
8</Package>Wildcard Support in the Manifest File
This metadata type supports the wildcard character * (asterisk) in the package.xml manifest file. For information about using the manifest file, see Deploying and Retrieving Metadata with the Zip File.