[Nikita]

Hi Saddam,

If a user has only Read access on particular record but he wants to change the owner name of that record, then in profile level Transfer Record enables he can able to change the owner.

[Nikita]

Hi Saddam,

You can check the User License Information by

• From Setup, enter Company Information in the Quick Find box, then select Company Information.
• See the User Licenses related list.

Thank Nikita

[Nikita]

Hi, Saddam

An external lookup relationship ios used when a parent is an external object.

[Nikita]

Hi Saddam,

Component events are used to do communication between child and parent. They use bubbling and capture the same as used in DOM events. A change in a child component can be communicated to the parent component via the component event.

Application events are used to communicate any change in the component to a broader audience. Any component who has registered for this event will get a notified.

[Nikita]

Hi Saddam,

To refresh a view, run $A.get('e.force:refreshView').fire();, which reloads all data for the view.

 

Thanks Nikita

[Nikita]

Hi Saddam,

It is an event which is fired to show the Full Record Create panel.This event opens a page to create a record for the specified entityApiName, for example, "Account", or "myNamespace__MyObject__c".

To display the record create a page for an object, set the object name on the entityApiName attribute and fire the event. recordTypeId is optional and, if provided, specifies the record type for the created object. defaultFieldValues is optional and, if provided, specifies values to use to prepopulate the create record form.

This example displays the record create panel for contacts.

createRecord : function (component, event, helper) {
var createRecordEvent = $A.get("e.force:createRecord");
createRecordEvent.setParams({
"entityApiName": "Contact"
});
createRecordEvent.fire();
}

[Nikita]

Hi Achintya,

ReRender- This is to reload some fields or sections after some operation. Advantage of it is that the whole page is not refreshed and only a portion(the one which is ReRendered) is refreshed.

[Nikita]

Hi Achintya,

It has a Boolean value that specifies whether the Salesforce tab header is included in the page. If true, the tab header is displayed. If not specified, this value defaults to true.

Note: In Lightning Experience and the Salesforce app the value of this attribute is overridden, and is always false.

Thanks

[Nikita]

Hi Achintya,

No, it is not necessary to create an App Bundle first to develop the lightning component. After you create a component, you will want to display it somewhere. So to display it you may create a standalone Lightning App.

 

Thanks Nikita

[Nikita]

Hi Deepak,

A lightning:accordion component groups related content in a single container. Only one accordion section is expanded at a time by default. When you select a section, it's expanded or collapsed. Set allowMultipleSectionsOpen to allow more than one section to be opened. Each section can hold one or more Lightning components.

This component inherits styling from accordion in the Lightning Design System.

To additionally style this component, use the Lightning Design System helper classes.

• This reply was modified 5 years, 3 months ago by  Nikita.

[Nikita]

Hi Prachi,

To abort a scheduled job went to Setup > Jobs > Apex Jobs or Setup > Jobs > Scheduled Jobs There was Abort option 🙂

[Nikita]

Hi Laveena,

Audit Trail allows security admin users to view Marketing Cloud access and activity records. View Audit Trail records either through Marketing Cloud Automation Studio data extracts or through REST API extracts.

Audit Trail applies to all messaging and journeys to customers.

Thanks

[Nikita]

Hi Laveena,

Manual sharing is sharing via a button on the record. This is only available to the record owner or users above that user in the hierarchy. For example, if the record is only visible by me as the owner but I need to give access to someone else to review the opportunity for example, I can grant them access using this button.

Thanks

[Nikita]

Hi Saddam,

Add the force:hasRecordId interface to a Lightning component to enable the component to be assigned the ID of the current record. The current record ID is useful if the component is used on a Lightning record page, as an object-specific custom action or action override in Lightning Experience or the Salesforce app, and so on.

The force:hasRecordId interface does two things to a component that implements it.

1. It adds an attribute named recordId to your component. This attribute is of type String, and its value is an 18-character Salesforce record ID, for example: 001xx000003DGSWAA4.If you added it yourself, the attribute definition would look like the following markup:
   •  <aura:attribute name="recordId" type="String" />
   • Note If your component implements force:hasRecordId, you don’t need to add a recordId attribute to the component yourself. If you do add it, don’t change the access level or type of the attribute or the component will cause a runtime error.
2. When your component is invoked in a record context in Lightning Experience or the Salesforce app, the recordId is set to the ID of the record being viewed.

[Nikita]

Hi Achintya,

Lightning Component can be used as

• Aura Component Bundle Design Resources
• Use Aura Components in Lightning Experience and the Salesforce Mobile App
• Navigate Across Your Apps with Page References
• Get Your Aura Components Ready to Use on Lightning Pages
• Use Aura Components in Community Builder
• Use Aura Components with Flows
• Add Components to Apps
• Integrate Your Custom Apps into the Chatter Publisher
• Using Background Utility Items
• Use Lightning Components in Visualforce Pages
• Add Aura Components to Any App with Lightning Out (Beta)

For more detail, you can refer https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/components_using_intro.htm

[Nikita]

Hi Achintya,

Use <aura:method> to define a method as part of a component's API. This enables you to directly call a method in a component’s client-side controller instead of firing and handling a component event. Using <aura:method> simplifies the code needed for a parent component to call a method on a child component that it contains.

For more detail you can refer https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/ref_tag_method.htm

[Nikita]

Hi Laveena,

Transfer record is a type of permission in salesforce. If a user is given access to transfer a record then the user will have the ability to transfer the records which have Read access.

A record owner, or any user above the owner in the role or territory hierarchy, can transfer a single record to another user. With some objects, like cases, leads, and campaigns, a user may be granted access to transfer records through sharing. Depending on the type of object, there may be multiple ways to transfer records to another user.

[Nikita]

Hi Achintya,

Please check this if it works for you.

@isTest
private class TriggerTestClass {

static testMethod void autoTasktest() {
// TO DO: implement unit test

Account acc = new Account(
Name = 'Test Account 1',
Phone = '07123123123',
Toolsberry_new_tech_installs__c = 'null',
Toolsberry_removed_tech_installs__c = 'null');
insert acc;

acc.BillingCity = 'Test Area 2';
update acc;

}
}

[Nikita]

Hi Deepak,

Benefits of asynchronous processing are following

• Higher governor and execution limits
• Unlimited number of external callouts
• Override organization-wide sharing defaults
• Enabling turbo mode for transactional processing

[Nikita]

Hi Somendra,

Salesforce treats an object as a database tables, and fields as columns, and records as rows.

Salesforce differentiates custom object and custom field with “__c” suffix at the end of every custom field and custom object.

[Nikita]

Hi Hariom,

A custom controller is an Apex class that implements all of the logic for a page without leveraging a standard controller. Use custom controllers when you want your Visualforce page to run entirely in system mode, which does not enforce the permissions and field-level security of the current user.

A controller extension is an Apex class that extends the functionality of a standard or custom controller. Use controller extensions when:

• You want to leverage the built-in functionality of a standard controller but override one or more actions, such as edit, view, save, or delete.
• You want to add new actions.
• You want to build a Visualforce page that respects user permissions. Although a controller extension class executes in system mode, if a controller extension extends a standard controller, the logic from the standard controller does not execute in system mode. Instead, it executes in user mode, in which permissions, field-level security, and sharing rules of the current user apply.

Thanks Nikita

[Nikita]

You cannot have more than 10 columns on a related list.

[Nikita]

Hi Achintya,

I think the following ways do the deployment in salesforce:-

1. Change Set (if you want to keep track of what has been deployed & when)

2. Using Eclipse

3. ANT

Apart from the above three, there are multiple tools available in the market too. But the above three are used mostly.

for more detail, you can refer https://help.salesforce.com/articleView?id=code_tools_ant.htm&type=5

[Nikita]

Hi Achintya,

Fields that are automatically indexed in Salesforce are:

• RecordTypeId
• Division
• CreatedDate
• Systemmodstamp (LastModifiedDate)
• Name
• Email (for contacts and leads)
• Foreign key relationships (lookups and master-detail)
• The unique Salesforce record ID, which is the primary key for each object.

Salesforce also supports custom indexes on custom fields, with the exception of multi-select picklists, text area (long), text area (rich), non-deterministic formula fields, and encrypted text field

[Nikita]

Hi Deepak,

For Salesforce Professional and Enterprise, each organization receives a total of 1,000 API calls per user in a 24-hour period, up to a maximum of 1,000,000 API calls (for organizations with 15,000+ Salesforce licenses).

Salesforce Unlimited has a 5,000 API calls per user limit, up to a maximum of unlimited API calls.

for more detail please refer https://developer.salesforce.com/docs/atlas.en-us.salesforce_app_limits_cheatsheet.meta/salesforce_app_limits_cheatsheet/salesforce_app_limits_platform_api.htm