Data Capture Limitations and Guidelines

Learn more about Data Capture limitations and best practices.

Data Capture has the following limitations.

Flow Structure and Data Operations

Create, update, or delete operations can only be added to the end of the flow. You can’t add screens after or between any Create, Update, or Delete operations. Create, Update, and Delete operations can be in any order, as long as they are all at the end of the flow.
Note This constraint protects the integrity of offline functionality. Create, Update, and Delete operations can only be executed while a mobile worker is online. When a mobile worker is offline, these operations can’t execute until the mobile worker is online again.
Create Records, Get Records, Update Records, Delete Records operations can only be used to retrieve records of User Interface API enabled objects. You can find a list of supported objects at All Supported Objects.
Get Records operations can only be used to retrieve records of User Interface API enabled objects. You can find a list of supported objects at All Supported Objects.
Subflows are supported, but you can’t use Create, Update, or Delete operations with them.

Custom LWCs aren’t supported.
Components with choices (Choice, Collection Choice Set, or Record Choice Set) can only be configured with Text data types.
Choice sets don't store additional fields to variables.
Repeaters with Data Source configurations aren’t supported.
The Signature, Upload File, and Upload Image components don’t work when using the Flow Builder in Debug or Run mode.
The Upload Image, Upload File, Image Preview, Matrix, Lookup, and Signature components don’t support Voice to Form (Beta).
The Display Text component doesn’t support custom URL scheme links, for example, comgooglemaps:// for opening external apps.

Only the following global variables are supported: $Api, $Label, $Organization, $Profile, $System, $User, $UserRole) and ($Flow.CurrentDate, $Flow.CurrentDateTime, $Flow.InterviewStartTime, $Flow.InterviewGuid. To learn more about global variables, see Flow Resources: Global Variables.
Collection variables aren’t supported for conditional visibility.
When Record, Date & Time, and Date collection variables are created they can’t use the contains operator in Decision elements.
Only these formula options are supported: ABS, ADDMONTHS, AND, BEGINS, BLANKVALUE, CASE, CEILING, CONTAINS, DATE, DATETIMEVALUE, DATEVALUE, DAY, EXP, FIND, FLOOR, IF, ISBLANK, ISNULL, ISNUMBER, ISPICKVAL, LEFT, LEN, LN, LOG, LOWER, MAX, MCEILING, MFLOOR, MID, MIN, MOD, MONTH, NOT, NOW, NULLVALUE, NUMBER, OR, REGEX, RIGHT, ROUND, SQRT, STRING\_LITERAL, SUBSTITUTE, TEXT, TODAY, TRIM, UPPER, VALUE, WEEKDAY, YEAR.

Error messages for validation issues can’t reference elements from another screen.

You can’t upload files larger than 100 MB. To compress image files, see Media Utils in the Lightning Web Components Developer Guide.
To avoid performance issues, use Data Capture on phones with more than 4GB of RAM.
To avoid performance issues, don't upload more than 10 files or images at a time.
To avoid performance issues, break down complex forms that use a single screen, into multiple screens.

Only admin profiles and users with Manage Flow permissions can associate a Data Capture flow to the junction object.
Generating PDFs for completed Data Capture forms is available only for Unlimited Edition users.
For Get Records, you can sort a maximum of 2000 records. If you are looking for a specific record, you can use filters or sort order to improve the sort speed.

Did this article solve your issue?

Let us know so we can improve!