Unit-4, Data Modeling
Unit-4, Data Modeling
DATA MODELING
Data Modeling is a process that involves the structuring of the data in the database by creating
tables(objects), and columns(fields). So, to learn Data Modeling in Salesforce, the first thing
one should learn is Database.
About Database
It is simply a base of data, and can also be defined as an organized collection of structured
information, or data, typically stored electronically in a computer system. A database is usually
controlled by a database management system (DBMS).
Databases are widely divided into two major types or categories namely, Relational or
Sequence Databases and Non-relational or Non-sequence databases or No SQL databases. An
organization may use them individually or combined, depending on the nature of the data and
its required functionality.
Databases often store information about people, such as customers or users. For example, social
media platforms use databases to store user information, such as names, email addresses, and
user behavior. Such data can be used to recommend content to users and improve the user
experience.
In Salesforce
• Databases use objects to store data.
• Each object comprises several fields that correspond to columns in a database.
• Data is stored in records of objects which correspond to the rows in a database.
• Objects can be related to other objects using relationship fields.
These apps are a collection of items that include everything from the Classic apps list, plus
Lightning page tabs, and utilities like Sales Dialer. In Lightning apps, you can customize the
app’s logo and enhance its branding by customizing the color of the navigation bar.
3. Web Tabs
Web Tabs display any external Web-based application or Web page in a Salesforce tab.
6. Visualforce Tabs
Visualforce Tabs display data from a Visualforce page.
Tab Visibility
1. Default On
Show the tab by default for users with this profile. Individual users can override this setting for
their login.
2. Default Off
Hide the tab by default for users with this profile. Individual users can override this setting.
If the tab visibility is default off then the user will still be able to access the tab by clicking on
the “+” symbol at the end of all visible tabs on the top bar or in the App Launcher.
3. Tab Hidden
Hide the tab and do not allow individual users to override this setting in their customization.
If the tab is hidden then it will neither be visible on the top bar nor by clicking on the “+”
symbol or by going into the App Launcher.
Note:
1. However, users can edit this according to their preferences.
2. Whenever we delete any custom tab then the object associated with that is not deleted.
3. When we delete a custom object then the tab associated with that object is deleted.
For standard objects, the fields which are present by default in them cannot be deleted.
Imagine there are three picklist fields f1, f2, and f3. Below are the scenarios mentioned to
explain the possibilities.
b) f1 can be dependent on f2. f2 can be dependent on f3. then now, f3 cannot be directly
dependent on f1 or f2.