Object Relationships in Salesforce

As we know that Objects in Salesforce are nothing but a table which stores information. We can create different custom objects in Salesforce. There won’t be any real use until we connect these objects to build an Application.

The Objects in Salesforce can be connected using 4 relationships. They are:

i) Master-Detail relationship: In this two objects are related where one behaves as a Master and the other object behaves as a Child[Detail]. The Detail object always inherit properties from the Master. In this relationship Parent is always required for a child.

ii) Lookup relationship: In this the two objects are related and there is no Master or Child. Every object has it’s own properties. In this the Lookup field is not required.

iii) Self relationship: A self relationship is a lookup relationship to the same object. Example: If we have a Position object we can create a lookup relationship to the same object.

iv) Many-to-Many relationship: This allows the two objects to be related in a many-to-many fashion. Implementing this relationship we need another object known as Junction Object.

In the above picture two objects [Candidate and Position] has a many-to-many relationship. When doing this we use a custom object to connect the two objects  you want to relate to each other.

The picture given below gives the difference between Master-Detail and Lookup relationships.

Objects, Fields and Records

The basic elements in Salesforce are Objects, Fields and Records. In Salesforce there are standard objects and fields, which are already inside the platform and in addition to that we can also add objects and fields which are known as custom object and custom fields.

Objects: It is basically a table in a database and where it not only stores data but be a interface for the users.

Fields: They represent the column field in a table.

Records: They represent a row in a table.

A Standard Object and Field can be seen inside the platform. We will see more about Custom Objects and Custom Fields.

Example: If we are designing a HR Application then we can create a Object called “Job Application” which takes care of the applications coming in for that organization. In this a person’s name which will be a part of the application is a Field and each person applying is a Record.

 

 

Overview of Salesforce

Hello Guys!!! I’m here to explain some of the basic fundamentals of Salesforce. I think these posts will help the people who want to learn Salesforce or start their career in Salesforce. First of all, Salesforce works on a MultiTenant architecture. It means, all the user’s who are using Salesforce will be working in one cloud.
Now to the lesson, in Salesforce the basics which you need to know are:
i) Objects                iv) Tabs                      vii) Work Flow
ii) Fields                   v) Page Layouts        viii) Validation Rules
iii) Relationships      vi) Record Types         ix) Assignment Rules

We are going to discuss about all the things which are mentioned above in this blog.

There are two roles in Salesforce, they are Administrator and Developer.

Administrator is a person who are going to look after your admin part in the organization. He plays a very important role because he is the person who has access to the entire organization. He is the one who will decide who will be accessing which part of the application.

Developer is a person who is going to take care of the look and feel in Salesforce and will also do the things which cannot be done by the customized Salesforce application. The Developer will be dealing with two things, they are:
i) Apex Language [This is a language based on OOPS concept and takes care of the back-end operations in Salesforce]
ii) Visual Force [This is a language which takes care of the Front end part and is similar to HTML]

We will also discuss about Apex and Visual Force in this blog but little later.

So this is the overall part of Salesforce and this gives a brief idea about how Salesforce works.

Please leave your comments at the bottom of the page.