[Parul]

The Lightning component framework’s only allow those external JavaScript libraries which was upload in Salesforce static resources. In Spring’15 release Salesforce created a new component called <ltng:require> to load libraries while being secure.
Here is the sample for using external file in Lightning Component:-

<ltng:require
styles=”/resource/path/to/css1[,/resource/path/to/css2]”
scripts=’/resource//path/to/js1.js,[/resource//path/to/js2.js]’
afterScriptsLoaded=”{!c.controllerFunction}”
/>

[Parul]

Standard Profiles which mostly used are:

System Administrator
Standard User
Read Only
Solution Manager
Marketing User
Contract Manager

A profile of which most of the permissions you can't change are standard profiles. Profile is standard which have Custom Profile label unchecked when you open it.

[Parul]

Lightning Experience: It's the new, slick user interface and the Lightning Component framework is a UI framework for developing dynamic web apps for mobile and desktop devices. Lightning makes it easier to build responsive applications for ANY DEVICE. The initial release of the new user interface is geared towards sales reps with an intuitive interface that allows sales reps to work more efficiently. The dashboard and charts in Lightning Experience behave much like Wave where changes in the chart recalculates in real time

[Parul]

For the organizations, which have a very large database CRM designing is a considerable and necessary aspect. They have to maintain hundreds or thousands of records. With database usually, many accounts are associated with the main account and this association of many accounts with a single account is known as data skew. Data skew can impact the performance of your CRM, so it is essential to prevent the data skew to get better performance of CRM by increasing the number of records, which may impact the CRM up to a great extent.

[Parul]

Developer Sandbox
Developer pro sandbox
Partial data sandbox
Full copy sandbox

[Parul]

It denotes No records returned. The list has no rows for assignment shows that the list you are trying to access has no values in it.

[Parul]

We could not change the code once deploy in production because it is fully client based

[Parul]

Visualforce pages are webpages that belong to Salesforce. These webpages are created using a unique tag-based Mark-up language. It is similar to HTML but it's primary use is to access, display and update the organization’s data. The page is accessed by using a URL similar to that of a traditional webserver page.

Each tag in visual force language corresponds to some user interface component like section of a page, a list view or a field of an object. Interestingly, it can be easily mixed up with HTML markup, CSS style and Java libraries, etc.

[Parul]

Master-Detail
Lookup
Many-to-Many
Master-Detail (1:n)

A parent-child relationship in which the master object controls certain behaviors of the detail object.

When a record of the master object is deleted, its related detail records are also deleted.
The Owner field on the detail object is not available and is automatically set to the owner of its associated master record. Custom objects on the detail side of a master-detail relationship cannot have sharing rules, manual sharing, or queues, as these require the Owner field.
The detail record inherits the sharing and security settings of its master record.
The master-detail relationship field is required on the page layout of the detail record.
By default, records can’t be reparented in master-detail relationships. Administrators can, however, allow child records in master-detail relationships on custom objects to be reparented to different parent records by selecting the Allow reparenting option in the master-detail relationship definition.
You can define master-detail relationships between custom objects or between a custom object and a standard object. However, the standard object cannot be on the detail side of a relationship with a custom object. In addition, you cannot create a master-detail relationship in which the User or Lead objects are the master.

Lookup Relationship (1:n)

This type of relationship links two objects together, but has no effect on deletion or security. Unlike master-detail fields, lookup fields are not automatically required. When you define a lookup relationship, data from one object can appear as a custom related list on page layouts for the other object. See the Salesforce online help for details.

Child row not automatically deleted when a parent row is deleted
No inherited sharing.
25 lookup relation relationships allowed per object.
Lookup field on child not necessarily required.
Many-to-Many

You can use master-detail relationships to model many-to-many relationships between any two objects. A many-to-many relationship allows each record of one object to be linked to multiple records from another object and vice versa.

To create a many-to-many relationship, simply create a custom junction object with two master-detail relationship fields, each linking to the objects you want to relate.

[Parul]

Type

A self Relationship is a lookup relationship to the same object. Suppose let's take an object “Merchandise”. Here we can create relationship in between the Merchandise to Merchandise (same object) object. That is called “Self Relationship”.

[Parul]

All the standard profiles out of box from salesforce do not have the custom flag checked. Any profile you see that are not part of the link you have referred here are custom profiles created by someone who uses your org.

[Parul]

It is just a platform limitation and there's no way to get around it (sigh again). And there's no good way to explain that behavior either.

The best that you can do is this:

1. Create a lookup relationship with the User object.
2. Make the field required on the page layout.

That should do it.

[Parul]

Fields you create on standard or custom objects are called custom fields. You can create a custom field on the Contact object to store your contacts' birthdays. Identity, system, and name fields are standard on every object in Salesforce. ... A data type indicates what kind of information the field stores.

[Parul]

Wrapper Class in Apex Salesforce :

[Parul]

Wrapper Class in Apex Salesforce : A wrapper or container class is a class, a data structure, or an abstract data type which contains different objects or collection of objects as its members. A wrapper class is a custom object defined by programmer wherein he defines the wrapper class properties.

[Parul]

The different types of reports in Salesforce are:
Tabular report
Matrix report
Summary reports
Joined report

[Parul]

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.

[Parul]

The optimum size of static resources in Salesforce is 250 MB.Salesforce’s static resource, subscribers can upload zip files, images, jar files, JavaScript, and CSS files

[Parul]

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.

[Parul]

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.

[Parul]

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.

[Parul]

MVC Architecture – Model, View , Controller

[Parul]

Manual Sharing is used to grant one-off access. Manual sharing can be granted by record owner, any one above the owner in role hierarchy and System Administrator. Manual sharing is used to handle exception cases where access to a particular record needs to be given to a specific user. There is a Sharing button on the records page. This is used to provide manual sharing.

[Parul]

Per Salesforce Help:

By default, the Grant Access Using Hierarchies option is enabled for all objects, and it can only be changed for custom objects.

Controlling Access Using Hierarchies
https://help.salesforce.com/apex/HTViewHelpDoc?id=security_controlling_access_using_hierarchies.htm&language=en

It looks like you will need to modify your roles in order to work around this.

[Parul]

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.