Apex Developer Guide

Apex Developer Guide
Getting Started with Apex
Writing Apex
Running Apex
Invoking Apex
Apex Transactions and Governor Limits
Using Salesforce Features with Apex
Actions
Approval Processing
Authentication
Chatter Answers and Ideas
Use Cases for the CommercePayments Namespace
Connect in Apex
Moderate Chatter Private Messages with Triggers
DataWeave in Apex (Developer Preview)
Implementing DataWeave in Apex (Developer Preview)
Examples of DataWeave in Apex (Developer Preview)
Limitations of DataWeave in Apex (Developer Preview)
Moderate Feed Items with Triggers
Experience Cloud Sites
Email
External Services
Flows
Metadata
Permission Set Groups
Platform Cache
Salesforce Knowledge
Salesforce Files
Salesforce Connect
Salesforce Reports and Dashboards API via Apex
Salesforce Sites
Support Classes
Territory Management 2.0
Integration and Apex Utilities
Debugging, Testing, and Deploying Apex
Apex Reference
Appendices
Glossary
PDF

Newer Version Available

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

Limitations of DataWeave in Apex (Developer Preview)

DataWeave in Apex has these limitations in Developer Preview.

Feature is available as a developer preview. Feature isn’t generally available unless or until Salesforce announces its general availability in documentation or in press releases or public statements. All commands, parameters, and other features are subject to change or deprecation at any time, with or without notice. Don't implement functionality developed with these commands or tools in a production environment. You can provide feedback and suggestions for the DataWeave in Apex feature in the Trailblazer Community.

Note

  • DataWeave class methods are supported only in scratch orgs that have the DataWeaveInApex feature enabled.
  • DataWeave scripts can’t be packaged during Developer Preview.
  • The DataWeave Java bridge, that is, the ability to bind to static Java methods is disabled. See Introduction to Mule 4. Features that interact with the environment such as the readURL and envVar functions are also disabled. 
  • DataWeave is constrained to disallow the loading of additional libraries. Therefore, scripts must be self-contained.
  • DataWeave modules and importing other scripts aren’t supported. For example, import modules::MyMapping as per Using a Mapping File in a DataWeave Script isn’t supported.

    The feature supports built-in modules. See DataWeave Reference.

    Note

  • DataWeave in Apex doesn’t support these content types.
  • Apex classes must be at API version 53.0 or later to access DataWeave integration methods.
  • There’s a maximum of 50 DataWeave scripts per org.
  • The maximum body size of one DataWeave script is 100000 (one hundred thousand) characters.

XML Entity Expansion isn’t supported, either currently or in the future, as a guard against denial of service attacks.

Note