[shariq]

If we want to give the access to other users we use sharing rules.

[shariq]

 

Add java script file in Static Resource setup -> develop -> Static Resources -> click on ‘New’ -> Name: filename and add file from local desktop and save.

We can use that file as follows in Visual Force page

<apex: includescript values=” {! $Resource.fileName}”/>

[shariq]

A Wrapper class is a class whose instances are collection of other objects.

It is used to display different objects on a Visual Force page in same table.

[shariq]

We can customize different things on page layout like, Fields, Buttons, Custom Links and Related Lists. We can also create sections.

[shariq]

Yes user can upload their custom logo in documents and then they choose that logo for organization.

[shariq]

This type of relationship links two objects together,

Parent is not a required field.
No impact on a security and access.
No impact on deletion.
Can be multiple layers deep.
The lookup field is not required.

[shariq]

We are having four types of relationships, they are

Lookup Relationship

Master-Detail Relationship

Many To Many

Hierarchy Relationship

[shariq]

Since we are working in multitenant environment Sales force is enforcing the limits for all the functionalities.

How many no of fields for an object: 500
No of master detail relationships for an object: 2
No of lookup relationship for an object: 25
No of rollup summery fields: 25
How many external ids we can enable for an object: 7

[shariq]

Create a unique text field and update the field from workflow rule after the update again all the system validations will be performed so error will be displayed.

[shariq]

While creating or modifying the record based on the certain conditions we can display error messages on top of the page or below to the field.

[shariq]

Sharing rules are written to give edit access (public read and write) or public read only access to certain individuals in Sales force org. A classic example is when: – only your managers or superiors need to be given extra credentials to your records in objects as compared to your peers.

By default, all users in your organization will have organization-wide-default sharing settings of either Public Read Only or Private.
To give access to more records, which users do not own, we write sharing rules.
Example: Sharing rules are used to extend sharing access to users in public groups or roles. Hence, sharing rules are not as strict as organization-wide default settings. They allow greater access for those users.

As far as the second part of the question is concerned, the answer is no. We cannot use sharing rules to restrict data access. It is only used for allowing greater access to records

[shariq]

Custom tabs : Its create for objects
Web tabs : Its create to display a website
Visual force tabs: It create to display the visual force page

[shariq]

Whenever user try to create a new record or edit an existing record user can input the values for the fields, this page is nothing but edit page.
After creating a new record or editing an existing record, user can see the information of the record; this page is nothing but detail page.

[shariq]

• A standard field record name can have data type of either auto number or text field with a limit of 80 chars.

  For generating auto numbers, the format needs to be specified while defining the field and after that for every record that is added, the number will get auto generated. For example:-
  Sr No-{1}
  Sr No-{2}
  Sr No-{3}

[shariq]

For an object based on the Record Type, we can show different fields and different pick list values by assigning different page layouts for the record types and profiles.
After creating the record type, on the record type detail page user can see all the pick list data type fields, user can edit the pick list and decide which values should display for this particular record type.

[shariq]

In Salesforce, whenever user create any component or record then sales force will generate an unique id with which user can identify the record or component.
After creating the record, in the URL user can see the id of the record which is of 15 digits length.
Through user interface user always see 15 digit ids which are Cases-Sensitive.
If the user queries the existing records from the database through API, it will always return 18 digit ids which are Case-Insensitive.
Last 3 digits of the 18 digit represent checksum of the capitalization of 15 digit id.
Based on the first 3 digits user can identify the object of the record.
All the record belongs to same object will contain same first 3 digits.

[shariq]

Data loss in Salesforce can be caused by a number of reasons, including:

Changing data and date-time
Migrating to percent, number, and currency from other data types
Changing from multi-select pick list, checkbox, auto number to other types
Altering to multi-select pick list from any type except pick list
Changing to auto-number except from text
Changing from text-area to e-mail, phone, URL, and text.

[shariq]

MVC Architecture – Model, View , Controller
View – It is the user interface
Controller – Business Logic
Model – It is the Database, which stores Schema

[shariq]

A trigger is a lever which, when pulled by the finger, releases the hammer on a firearm. In a database, a trigger is a set of Structured Query Language statements that automatically “fires off” an action when a specific operation, such as changing data in a table, occurs. A trigger consists of an event and an action. Triggers are used to preserve data integrity by checking on or changing data in a consistent manner.

[shariq]

ISNULL (): It works only for number data type fields, if we don’t populate with value for number fields it will return true.
ISNULL (): It won’t support TEXT data type fields because text fields never become null.
ISBLANK (): It supports both number as well as text data types.

[shariq]

Tab name will be decided based on the Plural Label of the custom object, to rename go to corresponding object detail page and rename the plural label.

[shariq]

With Salesforce’s static resource, subscribers can upload zip files, images, jar files, JavaScript, and CSS files that can be referred in a Visual force page. The optimum size of static resources in Salesforce is 250 MB.

[shariq]

To create the Activities, while creating the object, we should check for ‘Allow Activities’ check box then user can add open Activities and Activity History related lists on the Object layout.

There are two types of activities

Task: Task is nothing but work assigned to a particular person, it doesn’t have certain time limit.

Event: It has certain time limit in that time only all persons should assemble after the time limit over, event will get complete.

Once event or task status changed to ‘Completed’ this we can see those records under Activity History Related List

[shariq]

The three types of object relations in Salesforce are:

• One-to-many
• Many-to-many
• Master-detail

The relation types are quite logical once the user becomes familiar with the software program.

[shariq]

While creating the object, we can enable ‘Track Field History’.
If, we enable ‘Track Field History’ user can see ‘Set History Tracking’ button under ‘Custom Fields & Relationships’ section which is available on the object detail page.
By clicking on ‘Set History Tracking’ button, we can enable tracking for the fields whichever we want.
To see the object history, go to object’s record layout and add Object Name History related list to the layout.
Whenever a user changes field value from one value to another value, it will show the history of the field in ‘Object History’ related list.