Agent skill · forcedotcom
field-service-sobject-create-configure
Headless 360 REST API deployment step for creating sObject records. Handles describe-based field discovery, required-field derivation, entity-relationship ordering, and composite graph transactions. Use this skill when a designer skill (or a user directly) needs to create sObject records after design confirmation, including non-setup sObject creation.
What it needs
About 6k tokens when loaded.
What this skill does
Managing Sfs Sobject Create When to Use This Skill Create sObject records via Headless 360 REST API. Describes the flow (describe → query → create), Field Service data model DAG, field requirements, insertion order, and common pitfalls. Reference when creating Skill, WorkType, SkillRequirement, or other Field Service sObjects. Workflow Create an sObject record via headless-360 Be helpful — understand business context before creating records. Consider the business domain of the sObject being created and iterate through short, structured questions (ask/why/impact) until no ambiguities remain that would change what gets created. Skip questions when answers are already obvious from context or existing data. Flow Phase 1: Describe — dispatchreadonly GET /services/data/v67.0/sobjects/<SObject>/describe Phase 2: Query existing records — learn the org's shape... dispatchreadonly GET /services/data/v67.0/query, queryParams.q = "SELECT <required + picklist fields> FROM <SObject> ORDER BY CreatedDate DESC LIMIT 20". Use it to: match naming/value conventions, see which optional fields are actually populated, catch duplicates, and confirm write access before spending a create. Phase 3: Create — dispatch POST to create records. Single... Data model DAG Example (Field Service junction pattern — same pattern applies to any sObject DAG based on the data shape): Fields and insertion order Scan describe fields[] for createable:true (skip the rest — describe is large). Such a field is required when also nillable:false and defaultedOnCreate:false (defaulted ones the platform fills — omit). Two kinds: Scalar → put its value in the create body. type:"reference" → foreign key. If nillable:false (hard edge), create parent in referenceTo[] first. Polymorphic refs list many — pick one. Topo-sort: roots first, pass each id to dependents. nillable:true refs → optional, PATCH later. Pitfalls: Base sObject CRUD is NOT in the discover corpus — skip discover, go straight to describe → dispatch. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/field-service-sobject-create-configure