Certified Platform App Builder Data Modeling and Management

Data Modeling and Management Detailed Explanation

Data modeling and management in Salesforce are all about defining how data is stored, structured, and related. This includes objects, fields, relationships, and the tools used for data import, export, and validation.

Core Component 1: Objects

What are Objects?

• Objects are like tables in a database that store data. Each object contains rows (records) and columns (fields).
• Salesforce uses objects to organize data and provide structure.

Types of Objects

1. Standard Objects:

   • Predefined by Salesforce and available in every instance.
   • Examples:
     • Account: Represents a company or an organization.
     • Contact: Represents a person, usually associated with an Account.
     • Opportunity: Represents a potential sale or business deal.

2. Custom Objects:

   • Created by users to store business-specific data.
   • Examples:
     • If you run a university, you might create a custom object called "Student" with fields like "Major" and "Graduation Date."

3. External Objects:

   • Represent data stored outside Salesforce, such as in external databases.
   • Accessed using tools like OData protocol.
   • Example: You can connect Salesforce to an external inventory management system and use external objects to display inventory data in Salesforce.

Core Component 2: Fields

What are Fields?

• Fields are like columns in a table, where each field stores a specific type of information for an object.

Field Data Types:

1. Standard Data Types:

   • Text: For storing alphanumeric data.
   • Number: For storing numeric values.
   • Currency: For monetary values.
   • Date/Time: For storing date or timestamp information.

2. Formula Fields:

   • Special fields that dynamically calculate values based on other fields.
   • Example: A formula field could calculate "Total Price" as Quantity * Unit Price.

Custom Field Features:

1. Required Fields:

   • Ensures that a field must be filled out before saving a record.
   • Example: A field like "Email Address" can be marked as required.

2. Default Values:

   • Pre-populates a field with a value when a new record is created.
   • Example: Defaulting a "Status" field to "New."

Validation Rules:

• Enforce specific business rules to ensure data accuracy.

• Example:

  ISPICKVAL(Status, "Open") && ISBLANK(Assigned_To__c)
  

  • Ensures that when the "Status" is "Open," the "Assigned To" field cannot be left blank.

Core Component 3: Relationships

What are Relationships?

• Relationships define how objects relate to each other. This is similar to relationships between tables in a relational database.

Types of Relationships:

1. Lookup Relationship:

   • A loose connection between two objects.
   • Example:
     • An Employee object might have a lookup relationship to a Department object. An employee can be linked to a department, but the relationship is optional.

2. Master-Detail Relationship:

   • A tightly coupled relationship where the child object depends on the parent object.
   • Key Features:
     • Ownership: The parent owns the child. If the parent is deleted, the child is also deleted.
     • Roll-Up Summary Fields: Allows the parent to aggregate data from its children.
   • Example:
     • A custom "Invoice" object might have a master-detail relationship with the "Account" object. If the account is deleted, all associated invoices are also deleted.

3. Hierarchical Relationship:

   • Specific to the User object.
   • Used to define reporting relationships between users.
   • Example:
     • A "Manager" field in the User object could define a hierarchy for reporting purposes.

Core Component 4: Data Import and Export Tools

Import Tools:

1. Data Import Wizard:

   • User-friendly tool accessible from the Salesforce UI.
   • Suitable for importing small volumes of data (up to 50,000 records).
   • Supports common standard objects (like Accounts, Contacts) and custom objects.

2. Data Loader:

   • A powerful tool for bulk data operations.
   • Suitable for importing, updating, or deleting large volumes of data (more than 50,000 records).
   • Requires installation on your computer.

Export Tools:

1. Data Export Tool:
   • Used for creating data backups.
   • Provides options for scheduling regular data exports.

Deletion Tools:

1. Mass Delete Records:
   • A built-in tool in Salesforce for deleting multiple records at once.
   • Example: Delete old leads or test data in bulk.

Beginner’s Practical Steps

1. Explore Salesforce Objects:

   • Use the Salesforce UI to view standard objects like Accounts and Contacts.
   • Practice creating custom objects for a scenario in your organization.

2. Work with Fields:

   • Add new fields to an object and experiment with different data types like text, number, and formulas.
   • Try setting up validation rules to enforce business requirements.

3. Experiment with Relationships:

   • Create a custom object and establish both Lookup and Master-Detail relationships with standard objects.

4. Use Data Tools:

   • Import a small set of data using the Data Import Wizard.
   • Export data for backup using the Data Export Tool.

Data Modeling and Management (Additional Content)

Data Modeling and Management in Salesforce involve defining how data is structured, related, and managed within the platform.

1. Objects

Salesforce Objects are database tables that store specific data. While standard and custom objects are commonly used, Big Objects provide unique capabilities for handling large-scale data.

Big Objects

Big Objects are designed to handle massive data volumes (billions of records) while maintaining performance and scalability. Unlike standard and custom objects, Big Objects:

• Support asynchronous SOQL queries only (no real-time reporting or list views).
• Are primarily used for historical data storage, such as archiving old transaction records without affecting system performance.
• Do not support standard CRUD operations (Create, Read, Update, Delete) via UI; instead, they require Apex, API calls, or Data Loader for data manipulation.

Use Case for Big Objects

• A company wants to store 10 years of order history without slowing down Salesforce reports.
• They can create a Big Object to store historical orders while keeping recent orders in a Standard Object (Order) for real-time reporting.

2. Fields

Salesforce Fields store data within objects. Two specialized field types—Roll-Up Summary Fields and Picklists—offer unique capabilities for data aggregation and structured selections.

Roll-Up Summary Fields

Roll-Up Summary Fields are only available in Master-Detail relationships and allow the parent object to summarize child object data.

• Supported Summary Operations:
  • SUM (e.g., Total Revenue from Opportunities related to an Account).
  • COUNT (e.g., Number of Cases related to an Account).
  • MIN/MAX (e.g., Earliest or latest transaction date).
• Limitations:
  • Cannot be used with Lookup relationships.
  • Cannot summarize formula fields.

Example Use Case

A company wants to track the total revenue of an Account based on related Opportunities:

• Create a Roll-Up Summary Field on Account.
• Configure it to SUM the Opportunity Amount field.
• Now, the Account record dynamically displays the total revenue from all its related Opportunities.

Picklist vs. Multi-Select Picklist

Picklists restrict field values to predefined choices, ensuring data consistency.

• Single Picklist:

  • Users select one value from a list.
  • Example: "Order Status" with values "Pending", "Shipped", "Delivered".

• Multi-Select Picklist:

  • Users select multiple values from a list.
  • Example: "Product Categories" where a product can belong to "Electronics" and "Home Appliances" at the same time.
  • Drawback: Multi-Select Picklists are difficult to query via SOQL (INCLUDES operator must be used) and do not support dependent picklists in reports.

Best Practices

• Use Single Picklists whenever possible.
• Avoid Multi-Select Picklists in large datasets due to query and API complexities.
• Use related objects instead of Multi-Select Picklists for better scalability.

3. Relationships

Salesforce Relationships define how objects are connected. In addition to Lookup and Master-Detail relationships, Self-Relationships and Junction Objects allow for hierarchical and many-to-many relationships.

Self-Relationship

A Self-Relationship is a Lookup relationship where an object references itself.

• Example: Employee Hierarchy
  • The "Employee" object has a "Manager" field, which is a Lookup to another Employee record.
  • This structure allows hierarchical relationships where each employee can have a manager.

Junction Object (Many-to-Many Relationship)

Junction Objects facilitate many-to-many relationships between two objects by using two Master-Detail relationships.

Example Use Case: Student-Course Enrollment

In an education system:

• A Student can enroll in multiple Courses.
• A Course can have multiple Students.
• A Junction Object called "Enrollment" is created:
  • Master-Detail 1: Connects to Student.
  • Master-Detail 2: Connects to Course.
• This structure allows students to be enrolled in multiple courses while enabling course tracking.

Why Use a Junction Object?

• Enables cross-object reporting (e.g., listing all students enrolled in a specific course).
• Allows custom automation like triggering alerts when a course reaches maximum enrollment.

4. Data Import & Export Tools

Salesforce provides built-in tools for data import and export, but third-party ETL tools offer additional flexibility.

Third-Party ETL Tools

ETL (Extract, Transform, Load) tools help integrate Salesforce data with external systems (e.g., databases, ERP, CRM). Popular ETL tools include:

• MuleSoft (Salesforce-recommended for enterprise integration).
• Talend (Open-source ETL tool with powerful transformation capabilities).
• Informatica (Enterprise-grade data management and integration).

Use Cases for ETL Tools

• Synchronizing Salesforce data with an external inventory management system.
• Migrating historical customer data from an old CRM to Salesforce.
• Automating data cleansing and enrichment before loading it into Salesforce.

Data Masking in Sandbox Environments

Salesforce Data Masking protects sensitive data in non-production environments (sandboxes).

• Example: A company wants to use customer data for testing but needs to mask credit card numbers to comply with security policies.
• Salesforce Shield Platform Encryption or third-party tools can be used to obfuscate sensitive data.

Data Masking vs. Encryption

Feature	Data Masking	Encryption
Purpose	Obfuscates sensitive data in sandboxes	Protects live production data
Use Case	Testing & development	Compliance with security standards
Data Retrieval	Data is irreversibly modified	Encrypted data can be decrypted with the right keys
Tools	Salesforce Shield, third-party ETL	Shield Platform Encryption

Conclusion

The additional topics covered in this section enhance our understanding of Data Modeling and Management in Salesforce:

1. Big Objects provide massive data storage capabilities without affecting performance.
2. Roll-Up Summary Fields allow for data aggregation in Master-Detail relationships.
3. Picklists vs. Multi-Select Picklists—knowing when to use each ensures data consistency and better query performance.
4. Self-Relationships and Junction Objects support hierarchical and many-to-many relationships.
5. Third-Party ETL Tools help integrate, transform, and migrate data efficiently.
6. Data Masking and Encryption protect sensitive information in sandboxes and production environments.