Agent skill · forcedotcom
field-service-data-capture-reference-configure
Build, edit, and deploy Salesforce Data Capture Flows (processType DataCaptureFlow) — Field Service mobile / offline forms. Use when authoring flow-meta.xml with runtime_service_fieldservice:dc* components, Repeater loops (.AllItems), master-detail child record persistence, visual polish (gradient banners, progress bars, callouts), supporting objects with FLS/permsets, debugging DataCaptureFlow deploy errors, or troubleshooting why a deployed form doesn't appear on the FSL Mobile Forms tab (DDC/WorkPlan OWD + AssignedResource sharing prerequisites).
What it needs
About 8k tokens when loaded.
What this skill does
Querying Fs Data Capture Reference When to Use This Skill Build, edit, and deploy Salesforce Data Capture Flows (processType DataCaptureFlow) — Field Service mobile / offline forms. Use when authoring flow-meta.xml with runtimeservicefieldservice:dc components, Repeater loops (.AllItems), master-detail child record persistence, visual polish (gradient banners, progress bars, callouts), supporting objects with FLS/permsets, debugging DataCaptureFlow deploy errors, or troubleshooting why a deployed form doesn't appear on the FSL Mobile Forms tab (DDC/WorkPlan OWD + AssignedResource sharing prerequisites). Workflow Salesforce Data Capture Flow Skill Build, edit, and deploy Salesforce Flows with processType: DataCaptureFlow (Field Service mobile / offline forms). --- Required metadata (every flow) Optional IsLlmTargetable custom property — if you include it, it must be a JSON string, not a boolean: The <booleanValue>false</booleanValue> form deploys but blocks activation — error: The value of the IsLlmTargetable custom property's value field must be a string in JSON format. Omitting the property entirely is also fine. --- XML structure rules Salesforce's Flow schema enforces grouping — all elements of the same type must appear in a single contiguous block. Deploy fails with Element X is duplicated at this location when violated. Group order doesn't matter, but within each group elements must be adjacent: all <choices> together all <dynamicChoiceSets> together all <screens> together all <decisions> together all <recordLookups> together all <recordCreates> together all <recordUpdates> together all <loops> together all <assignments> together all <variables> together Connector references determine execution order, not XML order. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/field-service-data-capture-reference-configure--3cf219