[Parul]

The recordId attribute is set only when you place or invoke the component in a context of a record. For example, when you place the component on a record page, or invoke it as an action from a record page or object home. In all other cases, such as when you create this component programmatically inside another component, recordId isn’t set, and your component shouldn’t depend on it.

A marker interface is a signal to the component’s container to add the interface’s behavior to the component.

[Parul]

Quick Action/Lightning Actions is an Object-specific action. Object-specific actions let users create records that have automatic relationships to other records, make updates to specific records, and interact with records in ways that you define.

Lightning actions are built on the existing salesforce Lightning Component Framework that you may already have adopted. So you can easily convert your existing Lightning components to actions and use them in Lightning Experience and Salesforce1 Application.

<aura:component implements="force:lightningQuickAction">
<center><b>This is a Lightning component </b></center>
</aura:component>

[Parul]

Every component has a unique globalId, which is the generated run=me-­‐unique  ID of the component instance.

• A  global  ID is not guaranteed to be the same beyond the life=me of a component, so it should never be relied on.
• To create a unique ID for an HTML element, use the globalId as a prefix or suffix for the element.
• Use  the  getGlobalId() function in JavaScript to get a component's global  ID.
• Get a component from its global ID.

<div  id="{!globalId  +  '_footer'}"></div>
var  cmp  =  $A.getComponent(globalId);
var  globalId  =  cmp.getGlobalId();

[Parul]

Salesforce introduced Lightning Data Service in Winter 17 as a pilot program. Use Lightning Data Service to load, create, edit, or delete a record in your component without requiring Apex code. Lightning Data Service handles sharing rules and field-level security for you.

It’s built on highly efficient local storage that’s shared across all components that use it. Records loaded in Lightning Data Service are cached and shared across components

[Parul]

refer this page, to study more about the roll up fields.

The Roll up Summary field is basically of 4 types:

Count
Sum
Min
Max
As, per our previous sessions on salesforce, lets create roll up field on object Course because this is the Master object.

I want to calculate total income from a course:

Go to App Setup | Create | Objects and click on New field and Select Roll up summary field.

In Step 2, enter the field name and help text etc.

For step 3, you will see below screen

In above image, at 1 we have to select the child object, at 2 we have to select the field on which it should calculate.

In our case, Fees paid field is of Formula type which works on currency.

And in section 3 you ca specify weather this roll up summary field include all record or any specific record which comes under the criteria you specified.

So, after creation of Roll up field on Master object final look is shown below:

adding some points:

While your formula fields calculate values using fields within a single record, roll-up summary field calculate values from a set of related records, such as those in a related list. You can create roll-up summary fields that automatically display a value on a master record based on the values of records in a detailed record. These detail records must be directly related to the master through a master-detail relationship.

Hope now you got your ans!.

Thanks

[Parul]

No, Roll up cant be created on child object

[Parul]

Yes

[Parul]

Yes, update the field of Parent record using workflow rule

Also By using Triggers

[Parul]

NO, its not possible to  Update of master record can we update the field of child record using workflow rule

[Parul]

These relationship types also determine how they handle record sharing, data deletion capability, and required fields in page layouts. Salesforce provides the following types of relationships that can be established among objects: Master-detail relationship.

[Parul]

It used to summarise a field in child object.
Also you can find min max value.

[Parul]

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.
By using Junction Object we can achieve this relationship, here junction object is having Master- Detail Relationship with different objects (Ex.Students & Courses). Using this Master to Detail Relationship, we can create the Many-to-Many Relationship in between the objects.

[Parul]

Record level security provide record level access to user’s in an organisation

[Parul]

profile is mandatory points that you think while creating User and Role

[Parul]

No, we can not change the settings of child record in Master Detail relationship

[Parul]

At a high level, Lightning Locker uses various technologies and techniques that are intended to do the following:

Prevent:

Components from causing XSS and similar security issues
Components from reading other component’s rendered data without any restrictions
Components from calling undocumented/private APIs
Enable:

Cool new features like client-side API versioning similar to REST API versioning*
Faster security review
Better and more secure JS development practices
Running 3rd party JS frameworks like React, Angular and so on*
Easily adding or removing new security features and policies

[Parul]

The key difference between the two is that the Profile is the users base set of permissions and all users are assigned to one. ... Profiles can be used to give or take away permission from the users assigned to it. Permission Sets can only give or extend permission to the users assigned to it.

I think this the good example to understand better:

Profile is like a Key to House
Permission sets are like keys to individual Rooms.

So if this profile is assigned to user means he can enter in to house but can’t enter in to the rooms
Until and unless permission sets are assigned to user he cant enter in to the rooms

hope this will help you.

[Parul]

Record-level permissions are granted at the entity level, but you may have certain fields associated with an entity that contain data that is more sensitive than the other fields. For these situations, you use field-level security to control access to specific fields.

Field Level Security or FLS gives you the provision to restrict particular individuals from accessing super sensitive and confidential information that are located in the records that they can see. FLS security is configured similar to CRUD but it allows the administrators to be able to pre-define the profiles that can see as well as write to most of the fields of the custom and standard objects.

[Parul]

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

• This reply was modified 6 years, 2 months ago by  Parul.

[Parul]

you can check variables like HasDeleteAccess. If HasDeleteAccess true means user have delete access. If false then user don’t have access..
Based on these accessibility perform DML..

[Parul]

Organization-Wide Defaults, or OWDs, are the baseline security you for your Salesforce instance. Organizational Wide Defaults are used to restrict access. You grant access through other means we will talk about later (sharing rules, Role Hierarchy, Sales Teams and Account teams, manual sharing, etc).

[Parul]

A role hierarchy works together with sharing settings to determine the levels of access users have to your Salesforce data. Users can access the data of all the users directly below them in the hierarchy.

[Parul]

1. OpportunitylineItem is junction object between opportunity and pricebookentry.
As We need PricebookEntry Id and opportunity Id while creating OpportunityLineItems.

2. PricebookEntry is a junction object between Product2 and PriceBook.
As we need Product2 Id and PriceBook2 Id while creating PricebookEntries.

[Parul]

aura:if instantiates the components in either its body or the else attribute, but not both. aura:renderIf instantiates both the components in its body and the else attribute, but only renders one. If the state of isTrue changes, aura:if has to first instantiate the components for the other state and then render them. We recommend using aura:if instead of aura:renderIf to improve performance.

[Parul]

To create a tree, we have to pass in an array of key-value pairs to the items attribute.
Below are the keys:

disabled (Boolean): Specifies whether a branch is disabled. A disabled branch can’t be expanded. The default is false.
expanded (Boolean): Specifies whether a branch is expanded. An expanded branch displays its nested items visually. The default is false.
href (String): The URL of the link.
name (String): The unique name for the item for the onselect event handler to return the tree item that was clicked.
items (Object): Nested items as an array of key-value pairs.
label (String): Required. The title and label for the hyperlink.