Sf Industry Commoncore Datamapper
Scaffold Salesforce OmniStudio Data Mapper Extract, Load, and Transform metadata with naming and field-mapping patterns for Industry Common Core implementations.
Overview
SF Industry Common Core Data Mapper is an agent skill for the Build phase that provides OmniStudio Data Mapper Extract/Load/Transform templates and field-mapping stubs for Salesforce Industry Common Core work.
Install
npx skills add https://github.com/jaganpro/sf-skills --skill sf-industry-commoncore-datamapperWhat is this skill?
- JSON templates for DR_Extract, DR_Load, and DR_Transform with {{Object}} and {{Purpose}} placeholders
- OmniDataTransformItem field-mapping skeleton with filter operator slots
- Patterns informed by OmniStudio dependency and cross-component relationship practices
- Credits omnistudio-mcp-server for dependency analysis and metadata query patterns
- Starts components as IsActive__c false for safer promotion workflows
Adoption & trust: 877 installs on skills.sh; 418 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You must stand up OmniStudio Data Mappers with consistent names and field maps but lack a repeatable JSON starting point tied to industry common core objects.
Who is it for?
Salesforce developers or solo implementers on Financial Services or other Industry Cloud projects using OmniStudio Data Mapper.
Skip if: Teams not on Salesforce OmniStudio or projects that only need generic REST API integration outside the Salesforce stack.
When should I use this skill?
User authors or extends Salesforce OmniStudio Data Mapper components for Industry Common Core Extract, Load, or Transform flows.
What do I get? / Deliverables
You get copy-ready DR_Extract, DR_Load, DR_Transform, and transform-item JSON you can adapt, activate, and wire into Integration Procedures.
- DR_Extract / DR_Load / DR_Transform JSON definitions
- OmniDataTransformItem mapping row template
- Inactive-by-default mapper records ready for customization
Recommended Skills
Journey fit
OmniStudio Data Mappers are integration artifacts created while wiring Salesforce industry cloud data flows during product build. Integrations subphase covers CRM and platform connectors where declarative ETL-style mappers connect Salesforce objects to experience layers.
How it compares
OmniStudio metadata templates—not a general-purpose database ETL framework or a live MCP deployment by themselves.
Common Questions / FAQ
Who is sf-industry-commoncore-datamapper for?
Salesforce builders and consultants drafting OmniStudio Data Mapper metadata for industry cloud solutions who want consistent DR_* scaffolding.
When should I use sf-industry-commoncore-datamapper?
Use it during Build/integrations when creating Extract, Load, or Transform mappers, defining OmniDataTransformItem rows, or aligning mappers with Integration Procedures on Industry Common Core.
Is sf-industry-commoncore-datamapper safe to install?
It is documentation and JSON patterns only; review the Security Audits panel on this Prism page for the hosting repo before install.
SKILL.md
READMESKILL.md - Sf Industry Commoncore Datamapper
{ "Name": "DR_Extract_{{Object}}_{{Purpose}}", "Type": "Extract", "IsActive__c": false, "Description": "Extract {{Object}} records for {{Purpose}}" } { "OmniDataTransformationId": "{{ParentTransformId}}", "Name": "{{FieldName}}", "InputObjectName": "{{SalesforceObjectApiName}}", "InputFieldName": "{{SalesforceFieldApiName}}", "OutputObjectName": "{{OutputNodeName}}", "OutputFieldName": "{{OutputFieldName}}", "OmniDataTransformItemOrder": 1, "FilterDataType": "String", "FilterOperator": "", "FilterValue": "" } { "Name": "DR_Load_{{Object}}_{{Purpose}}", "Type": "Load", "IsActive__c": false, "Description": "Load {{Object}} records for {{Purpose}}" } { "Name": "DR_Transform_{{Object}}_{{Purpose}}", "Type": "Transform", "IsActive__c": false, "Description": "Transform {{Object}} data structure for {{Purpose}}" } # Credits & Acknowledgments This skill was built upon the collective knowledge of the Salesforce OmniStudio community. We gratefully acknowledge the following projects, teams, and resources whose work informed the patterns and best practices in this skill. --- ## Tools & Projects ### sf-explorer/omnistudio-mcp-server **[github.com/sf-explorer/omnistudio-mcp-server](https://github.com/sf-explorer/omnistudio-mcp-server)** Key contributions: - Dependency analysis patterns for OmniStudio components - Cross-component relationship mapping (Data Mapper <-> Integration Procedure <-> OmniScript) - Metadata querying patterns for OmniDataTransform records ### @salesforce/omnistudio-mcp **Official Salesforce OmniStudio MCP Server** Key contributions: - Canonical OmniStudio metadata type definitions - Standard field mapping patterns and type structures - OmniDataTransform and OmniDataTransformItem schema reference --- ## Salesforce Engineering ### Salesforce Industries Engineering Key contributions: - OmniStudio platform architecture and Data Mapper runtime - OmniDataTransform metadata API and deployment model - Turbo Extract server-side compilation engine - DataRaptor to Data Mapper migration path and naming continuity --- ## Educational Resources ### OmniStudio Trailhead Modules **[trailhead.salesforce.com](https://trailhead.salesforce.com)** Key contributions: - DataRaptor fundamentals and hands-on exercises - Extract, Transform, and Load workflow patterns - Integration Procedure and Data Mapper interaction models - OmniStudio Developer certification preparation material Relevant trails and modules: - Build OmniStudio DataRaptors - OmniStudio Integration Procedures - OmniStudio Developer Certification Prep --- ## Official Salesforce Resources - **OmniStudio Developer Guide**: https://developer.salesforce.com/docs/atlas.en-us.omnistudio.meta/omnistudio/ - **OmniStudio Trailhead**: https://trailhead.salesforce.com/en/content/learn/trails/build-omnistudio-components - **Salesforce Industries Documentation**: https://help.salesforce.com/s/articleView?id=sf.os_dataraptors.htm --- ## Community Resources ### Salesforce Stack Exchange **[salesforce.stackexchange.com](https://salesforce.stackexchange.com/)** - DataRaptor/Data Mapper Q&A and troubleshooting - Performance optimization discussions - Field mapping pattern solutions ### Salesforce Ben **[salesforceben.com](https://www.salesforceben.com/)** - OmniStudio overview articles - DataRaptor best practice guides - Industries Cloud adoption guidance --- ## Contributor ### David Ryan (weytani) **Primary Contributor** — [GitHub](https://github.com/weytani) This sf-industry-commoncore-datamapper skill was contributed by David Ryan (weytani) as part of the Jaganpro/sf-skills skill library. --- ## Special Thanks To the Salesforce Industries and OmniStudio community -- consultants, developers, architects, and ISV partners -- for sharing practical knowledge about Data Mapper patterns, performance tuning, and production deployment strategies. --- *If we've missed anyone whose work influenced this skill, please let us