handling-sf-data

Create, update, delete, and bulk-load Salesforce records with describe-first validation.

803|289|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/forcedotcom/sf-skills --skill handling-sf-data
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handling-sf-data
Source: https://github.com/forcedotcom/sf-skills/tree/main/skills/handling-sf-data
Command: npx skills add https://github.com/forcedotcom/sf-skills --skill handling-sf-data

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

handling-sf-data eliminates slow, brittle Salesforce org data setup by guiding record CRUD and bulk import/export through a describe-first validation workflow with cleanup built in.

Core Features & Use Cases

  • Describe-first data validation: validates required fields, createable/updateable constraints, and picklist values before writes to prevent common failures.
  • CLI-first and Bulk API 2.0 operations: supports targeted sf data commands for CRUD plus bulk insert/update/upsert/delete and exports for large datasets.
  • Cleanup and isolation discipline: provides rollback/savepoint guidance and delete-by-pattern/created-date strategies to avoid polluting org state.

Quick Start

Tell your AI: Create 251 test Account records with varying Industries for trigger testing in org dev, using describe-first validation and provide cleanup instructions.

Frequently Asked Questions about handling-sf-data

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bulk load test records into a Salesforce org without hitting validation errors?

Salesforce bulk data loading prevents validation errors by running a describe-first workflow that checks required fields, createable constraints, and picklist values before writing records via Bulk API 2.0 or sf CLI v2.

How do I bulk-load test records into a Salesforce org and prevent field validation failures?

Salesforce bulk data loading prevents validation failures by applying describe-first validation to check required fields, createable constraints, and picklist values before writing records via Bulk API 2.0 or sf CLI.

What's the best way to clean up and rollback Salesforce test data after bulk operations?

Salesforce test data cleanup uses rollback guidance with delete-by-pattern and created-date strategies, applying savepoint discipline to remove seeded records and avoid polluting the org state after bulk operations.

Does the sf CLI support hierarchical tree imports for Salesforce data migration?

Yes, Salesforce data operations support hierarchical tree imports using sf CLI v2 data commands combined with optional anonymous Apex orchestration to manage complex parent-child record relationships during migration.

How do I troubleshoot failed Salesforce data operations for triggers and flows?

Troubleshoot failed Salesforce data operations for triggers and flows by using anonymous Apex orchestration and describe-first validation to identify field constraint violations, failed CRUD operations, and integration errors before reprocessing.

Can I use anonymous Apex to orchestrate complex Salesforce data seeding?

Yes, anonymous Apex orchestrates complex Salesforce data seeding by coordinating CRUD operations and bulk import workflows, allowing you to script multi-step record creation and validation logic within the org.