Day 2 | Salesforce Learning Bootcamp 2023 | Salesforce Data Model | Object, Field, Record, Tab & App

Introduction and Session Overview

Session Start

• The speaker confirms audio clarity and mentions a brief wait for participants to join the session.

• An exercise sheet link is shared, designed to help attendees practice daily tasks related to Salesforce topics discussed in the sessions.

Purpose of Exercise Sheet

• The exercise sheet will be updated daily with tasks based on previous discussions, aiding beginners in practicing Salesforce concepts.

• Feedback from participants is encouraged regarding the usefulness of the exercise sheet.

Resources and Learning Structure

Accessing Materials

• All relevant links, including Excel sheets and social media platforms, are available in each video's description for easy access.

• A YouTube playlist has been created to organize all videos for participant convenience.

Speaker Introduction

• The speaker introduces themselves as leading a six-month boot camp aimed at covering comprehensive Salesforce content.

Learning Best Practices

Virtual Learning Tips

• Participants are advised to focus on live sessions, take notes for future reference, and ask questions during Q&A segments.

• Emphasis is placed on watching recorded sessions if missed since they build upon one another.

Community Engagement

• Participants are encouraged to use YouTube's comment section for questions or answers, fostering community support among learners.

Motivation and Future Plans

Speaker's Commitment

• The speaker expresses their dedication to running this extensive boot camp while seeking blessings from participants for strength throughout the journey.

Additional Content Offerings

• Future boot camps will cover programming languages like C, C++, and Java aimed at college beginners transitioning into programming.

Today's Topic: Salesforce Data Model

Agenda Overview

• Today's session focuses on understanding key components of the Salesforce data model: objects, fields, records, tabs, and apps.

Understanding Objects and Tabs in Salesforce

Introduction to Objects

• In Salesforce, a table is referred to as an "object." Each row within this table is known as a "record," while the headings of columns are termed "fields."

• The values contained within these fields are called "data values," which remain consistent terminology across both Excel and Salesforce.

Data Model Overview

• An Excel sheet has been prepared with a data model that includes objects such as student, instructor, class, and STD class for practical guidance.

• A theoretical explanation of what an object is will precede the practical creation of objects in Salesforce.

Types of Objects in Salesforce

• Objects in Salesforce function similarly to database tables. There are two main types: standard objects (provided by Salesforce) and custom objects (created based on project requirements).

• Standard objects include common entities like account, contact, case, lead, and opportunity. These support default applications like Salesforce Sales and Service.

Creating Custom Objects

• Custom objects can be created according to specific project needs. When creating any object, three key elements must be provided: label (name), plural label (used for tabs), and API name (unique identifier).

• The API name helps distinguish between standard and custom objects; standard object names typically match their labels while custom ones have "_C" appended.

Navigating with Tabs

• Tabs facilitate navigation within an application. They serve as entry points for viewing or editing information related to specific objects.

• If no tab exists for an object, it won't be visible on the user interface. Clicking a tab reveals the home page associated with that object.

Practical Application: Creating Custom Object & Tab

• The next step involves creating a custom object named "student," based on specified requirements outlined in the Excel sheet.

Creating a Custom Student Object in Salesforce

Steps to Create a Student Object

• To create a custom object, navigate to the Object Manager under Setup and select the "Create Object" option located at the top right corner.

• Fill out three essential fields: Label (Student), Plural Label (Students), and API Name (automatically generated). A description can also be added for project context.

• During object creation, one field must be created. For this example, it will be named "Student ID," which serves as a unique identifier similar to IDs assigned in educational institutions.

Field Type Selection

• The Student ID field can either be set as Text or Auto Number. An Auto Number is preferred as it generates unique identifiers automatically based on defined conventions.

• Define the format for the Auto Number; for instance, using "S-00" followed by a starting number of 1. Optional features can be skipped initially.

Tab Creation Process

• After filling out required information, check the box to launch the tab creation wizard post-object creation.

• If you forget to check this box during object creation, you can still create a tab later for that specific object.

Configuring Tab Settings

• Upon checking the box and saving, you'll see the tab creation page where you can select predefined tab styles and optionally add descriptions.

• Profiles determine user access levels. You have options for applying visibility settings: all profiles or different settings per profile.

Understanding Tab Visibility Options

• Three visibility options are available: Default On (tab appears in navigation bar), Default Off (tab not visible but searchable), and Tab Hidden (not accessible).

• Selecting Default On allows immediate access from navigation bars across all profiles; however, different settings may apply based on project requirements.

Finalizing Tab Creation

• Choose which custom apps will display your new tab during its creation process. You can adjust visibility later if needed.

• After selecting relevant applications and saving changes, both the student object and its corresponding tab are successfully created within Salesforce.

Creating and Managing Custom Objects in Salesforce

Overview of Object Creation

• The default singular label for the object is "student," while the plural label is "students," which appears on the tab.

• If changes are made, refreshing the front end may be necessary to see updates; sometimes multiple refreshes are required for visibility.

• Initially, no information displays under the students tab except for student ID, which was created during object creation.

Understanding Tab Labels

• Each tab's name is in plural form (e.g., "students") because it represents multiple entries or records.

• The student object can be found in the object manager, labeled as a custom object with its creation date and description visible.

Searching and Managing Objects

• Users can utilize a quick find feature to search for objects without scrolling through all available options.

• If a checkbox for creating a tab was missed during initial setup, users can create tabs later by selecting new from the home screen.

Creating Additional Objects

• To create another custom object (instructor), navigate to the object manager and fill out necessary fields like API name and ID format.

• The instructor ID will be set as an auto number with customizable formatting options; examples are provided for clarity.

Finalizing Object Setup

• It’s important to note that unchecking the checkbox during creation means no tab will automatically generate; this process must be done separately afterward.

• After saving an instructor object without creating a tab initially, users must select a style and application when creating it later.

Refreshing Front End Changes

• Once changes are made, refreshing is essential to view newly created tabs like "instructors."

• A summary of key concepts includes understanding standard vs. custom objects/tabs and their respective creation processes.

Exercise Instructions

• For practice, users should create a student custom object with registration numbers (or student IDs), followed by creating corresponding tabs and fields.

Creating Fields and Records in Salesforce

Introduction to Fields

• The session focuses on creating fields within an app, emphasizing the importance of understanding how to implement these concepts through practice.

• In Salesforce, fields correspond to column headings in Excel; they are essential for data organization and storage.

• Various data types are available for creating fields, which can be explored through descriptions provided during the field creation process.

Creating a Field

• To create a field, navigate to the Object Manager and select the relevant object (e.g., Student).

• After selecting the object, access "Fields and Relationships" to initiate the creation of a new field.

• When creating a text field for storing student names, five different text data types are available with descriptions aiding selection.

Field Configuration

• While configuring the new field, provide necessary details such as label (Name), length (100 characters), and API name which is auto-generated.

• A description can be added for clarity on what information will be stored in this field; help text can guide users on input requirements.

• Options include making the name required or unique across records within that object. External ID settings assist with integration purposes.

Page Layout Considerations

• Users can set default values for new records; these must be entered in double quotes when specified.

• The checkbox option allows visibility of this field across all user profiles even if profile settings have not been fully understood yet.

Finalizing Field Creation

• Adding the newly created field to page layouts ensures it appears where needed; unchecking this option means it won't show immediately but can be added later.

• Upon saving, the custom field is identified by an underscore suffix (_C), distinguishing it from standard fields.

Understanding Records in Salesforce

Definition of Records

• Records represent rows within an object and are uniquely identified by their IDs in Salesforce.

• Each record is created by entering values into fields associated with an object. This process follows after defining objects and tabs.

Salesforce Record Management and App Creation

Overview of Salesforce Records

• Each record in Salesforce is identified by a unique ID, allowing for the creation, editing, viewing, and deletion of records under specific objects.

• The user interface (UI) displays different views: detail pages for individual records and list views that show all records with filtering options available.

Creating and Managing Records

• To create a new record, users fill out fields such as Student ID (auto-generated) and Name. For example, entering "Sanjay Gupta" creates a new student record.

• After saving a record, the page layout shows details like Student ID (e.g., s0001), Owner, Last Modified By, and Help Text prompting for the student's name.

• Users can switch to edit mode by clicking on an icon (pencil), allowing modifications to fields like Name while auto-populated fields remain unchanged.

Viewing Records

• Users can view recently viewed records or all records through tabs; currently only one record exists but additional ones can be created easily.

• Fields are essential for creating records; standard fields include Student ID and Owner while custom fields may also be added based on requirements.

Interaction During Demonstration

• Participants are encouraged to answer each other's questions during the demonstration since not all queries can be addressed in real-time.

Understanding App Creation in Salesforce

• An app in Salesforce serves as a container for objects, tabs, and functionalities—similar to organizing code files within a programming project.

• Apps consist of a name, logo, and an ordered set of tabs which help organize related functionalities effectively.

Steps to Create an Application

• To create an application, navigate to App Manager from the home screen. Click on "New Lightning App" to start filling out necessary information such as app name (e.g., Sanjay Gupta Tech School).

• The developer name must be unique across all apps; it serves as the API name similar to object or field names used earlier in the process.

Navigation Types in Applications

• Two types of navigation exist: standard navigation and console navigation. Users should practice creating applications using both types for better understanding.

Finalizing Application Settings

• When setting up an application’s navigation type during creation, users select between standard or console options based on their needs.

• Supported form factors allow customization based on device compatibility; personalization settings enable control over user experience within the app.

This structured summary provides insights into managing records within Salesforce along with steps involved in creating applications tailored to specific organizational needs.

Creating a Custom Application in Salesforce

Adding Utility Items and Navigation

• The process begins with adding a utility item, such as a chatter feed, to the application. This can include custom components like Lightning components or flows.

• During app creation, navigation items (tabs) are added. In this case, tabs for "Students" and "Instructors" are included, which can be done at any stage of app development.

User Profile Selection

• It is crucial to select the System Admin profile when creating the application. This ensures that users have access to view and manage the application effectively.

• If the System Admin profile is not selected, users may miss out on accessing their applications. Emphasis is placed on ensuring this step is not overlooked by beginners.

Launching the Application

• After saving the application settings, refreshing the page allows users to launch their new app from the UI via the App Launcher.

• Upon opening the application, two tabs ("Students" and "Instructors") will be visible in the user interface.

Object Accessibility Across Applications

• Objects created in Salesforce can appear as tabs across multiple applications. For example, an object available in both a custom school app and a sales application retains its records across these platforms.

• Access control for these objects can be managed through user profiles, which will be discussed further in future sessions.

Understanding Navigation Styles

• The session transitions into explaining standard versus console navigation styles within Salesforce applications. Users can edit their apps to modify navigation settings.

• A brief discussion occurs regarding potential technical issues affecting screen visibility during editing processes.

Creating Objects and Field Definitions

• Future sessions will cover creating objects using Schema Builder; questions about specific features like starting labels with vowel sounds are addressed.

• External IDs serve integration purposes while unique IDs identify individual records; API names denote unique identifiers for objects or fields within Salesforce.

Navigation Types Explained

• Two main types of navigation styles are highlighted: standard navigation (all tabs displayed at once), and console navigation (dropdown style).

• The session concludes with confirmation that all planned topics were covered regarding object creation, tab setup, field definitions, and navigating between different styles within Salesforce applications.

Creating Records and Applications in Salesforce

Overview of Today's Session

• The session focuses on creating records and applications, emphasizing the importance of understanding all fields to ensure proper implementation.

• Participants are encouraged to ask questions at the end of the session, with a commitment to address as many inquiries as possible within 30 minutes.

Application Creation Process

• A question about file formats is addressed; resources will be available in the video description for further reference.

• Best practices for creating objects include sequential steps: first create an object, then a tab, followed by fields, culminating in application creation where objects can be added.

Custom Object Creation

• Custom objects can be created from spreadsheets using a specific button found under object manager. This involves setting up column headings as fields and importing data from Excel.

• The process includes selecting the appropriate sheet during importation to facilitate object creation.

Navigation Types Explained

• Clarification on different navigation types: Lightning app vs. Connected app. Lightning apps are created within this context while Connected apps allow integration with other applications.

• Differences between standard navigation (where previous tabs disappear when switching) and console navigation (which allows multiple records to remain open side by side).

Object Management Insights

• Participants are directed to check the object manager for a list of standard objects available within their environment.

• Discussion on interview questions related to object creation will occur later; participants are advised that limitations exist regarding metadata XML files for object creation.

Personalization Settings and User Queries

• Personalization settings allow users to manage what options are visible or editable in their applications, enhancing user experience based on preferences.

• Emphasis is placed on maintaining focus during Q&A sessions; irrelevant questions may hinder effective communication and learning outcomes.

Future Sessions and Additional Resources

• Standard objects will be discussed in future sessions; participants should prepare by reviewing relevant materials beforehand.

• Official documentation is recommended for understanding limits on object creation based on licensing agreements.

This structured summary provides an organized overview of key points discussed during the session, facilitating easier review and comprehension.

Can We Convert Standard Objects to Console Applications?

Key Insights on Object Conversion and Navigation

• The speaker confirms that standard objects cannot be converted to console applications, emphasizing the importance of deciding the type at creation.

• A trail mix for admin certification is available on the Trailhead website, which can be accessed freely in a developer org.

• The external ID is explained as being primarily used for integration purposes; custom objects can be created through various methods including UI and Excel spreadsheets.

Understanding Navigation Types

• Once an object is created as standard or console, it cannot be changed between these types.

• Console navigation can be applied to custom objects but is determined at the app level rather than object level.

Managing Tab Visibility and User Access

Tab Management Features

• Users can create tabs with specific visibility settings; options include hiding tabs from certain profiles while allowing access to others.

• Two visibility options are discussed: "default on" means availability in the navigation bar, while "default off" restricts access.

Profile-Based Access Control

• Different logins will have varying object access based on user profiles, which will be elaborated upon in future sessions regarding profiles and permission sets.

Creating Custom Objects and Their Fields

Custom Object Creation Methods

• Custom objects can have labels similar to standard objects, but their API names must remain unique.

• Schema Builder is mentioned as an additional option for creating custom objects through a user-friendly interface.

Record IDs vs. External IDs

• Clarification provided that record IDs are not external IDs; record IDs are unique identifiers tied to specific records within URLs.

Standard Fields in Custom Objects

Essential Standard Fields Explained

• When creating custom objects, four standard fields are automatically included: Owner, Created By, Last Modified By, and Auto Number field.

Conclusion of Session Insights

• The session wraps up with thanks to participants; recordings will be made available along with scheduling details for future sessions.