data-modeling

Analyze Salesforce object models and propose relationship types, external IDs, and record-type strategies.

2|Updated Mar 18, 2026

Search Tags:#data-modeling #salesforce #relationship-patterns #external-ids #big-objects #data-skew

Ready to run

npx skills add https://github.com/bhanu91221/claude-sfdx-iq --skill data-modeling-bhanu91221

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: data-modeling
Source: https://github.com/bhanu91221/claude-sfdx-iq/tree/main/skills/data-modeling
Command: npx skills add https://github.com/bhanu91221/claude-sfdx-iq --skill data-modeling-bhanu91221

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Salesforce data modeling decisions are error-prone without clear guidance on relationship types, key fields, and data governance. This Skill provides patterns and examples to help teams decide between Master-Detail, Lookup, and Junctions, and to plan External IDs, Record Types, and Big Objects for scalable, maintainable data architectures.

Core Features & Use Cases

Clear decision criteria for Master-Detail vs Lookup, and guidance on creating junction objects for many-to-many relationships.
Guidance on External IDs, Record Types, and Big Objects to support integration, data migration, and archival strategies.
Practical scenarios addressing data integrity, sharing, performance, and governance across admins, developers, and architects.

Quick Start

Analyze a Salesforce object model and propose relationship types, external IDs, and record-type strategy for a new app.

Frequently Asked Questions about data-modeling

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

FAQPage Schema

When should I use Master-Detail vs Lookup relationships in Salesforce?▼

Use Master-Detail for tightly coupled objects requiring cascading deletes and roll-up summaries, and Lookup for loosely linked records. Salesforce data modeling decisions depend on whether you need strict data integrity or independent record sharing and deletion behaviors.

How do I model many-to-many relationships using junction objects in Salesforce?▼

To model many-to-many relationships, create a junction object with two Master-Detail fields referencing the parent objects. This Salesforce junction pattern ensures data integrity while allowing flexible linking and reporting across both parent record sets.

What is the best way to use External IDs for Salesforce data migration?▼

External IDs mark custom fields as unique identifiers to prevent duplicate records during data migration and integration. Using External IDs in Salesforce data modeling allows upsert operations to match incoming source data against existing records efficiently.

Should I use Record Types or separate custom objects for different business processes?▼

Use Record Types when objects share the same core fields but need different page layouts and picklist values, and separate objects when data structures fundamentally diverge. Choosing correctly prevents data skew and maintains Salesforce performance.

How do Big Objects handle data archiving and what constraints apply?▼

Big Objects manage massive data volumes for archival and audit purposes in Salesforce, but carry strict indexing and querying constraints. Salesforce data modeling with Big Objects requires careful planning of indexed fields to avoid performance limitations.

Why does data skew happen in Salesforce and how can I prevent it?▼

Data skew occurs when too many child records are associated with a single parent record, causing locking and performance issues. Prevent Salesforce data skew by distributing ownership and relationship patterns across multiple parent records.