[Nikita]

Hi laveena,

Yes, there is a limit based on the license you owned.

From Setup, in the Quick Find box, enter Users and then select Prospector Users. In the Data.com Users section, find your name and see what your monthly limit is and how many records you’ve already added or exported during the month. Your administrator sets the monthly allowance, which expires at the end of each month, regardless of whether you’ve met your limit.

[Nikita]

Hi Laveena,

Here are examples of common non-deterministic formulas. Force.com cannot index fields that:

• Reference other entities (i.e., fields accessible through lookup fields)
• Include other formula fields that span over other entities
• Use dynamic date and time functions (e.g., TODAY, NOW)

A formula is also considered non-deterministic when it includes:

• Owner, autonumber, divisions, or audit fields (except for CreatedDate and CreatedByID fields)
• References to fields that Force.com cannot index
  • Multi-select picklists
  • Currency fields in a multicurrency organization
  • Long text area fields
  • Binary fields (blob, file, or encrypted text)
• Standard fields with special functionalities
  • Opportunity: Amount, TotalOpportunityQuantity, ExpectedRevenue, IsClosed, IsWon
  • Case: ClosedDate, IsClosed
  • Product: Product Family, IsActive, IsArchived
  • Solution: Status
  • Lead: Status
  • Activity: Subject, TaskStatus, TaskPriority

[Nikita]

Hi Hariom,

• REST API has no official standard at all because it is an architectural style. SOAP API, on the other hand, has an official standard because it is a protocol.
• REST APIs uses multiple standards like HTTP, JSON, URL, and XML while SOAP APIs is largely based on HTTP and XML.
  As REST API deploys multiple standards, so it takes fewer resources and bandwidth as compared to SOAP that uses XML for the creation of Payload and results in the large-sized file.
• The ways both APIs exposes the business logics are also different. REST API takes advantage of URL exposure like @path("/WeatherService") while SOAP API use of services interfaces like @WebService.
• SOAP API defines too many standards, and its implementer implements the things in a standard way only. In the case of miscommunication from service, the result will be the error. REST API, on the other hand, don't make emphasis on too many standards and results in corrupt API in the end.
• REST API uses Web Application Description Language, and SOAP API used Web Services Description language for describing the functionalities being offered by web services.
• REST APIs are more convenient with JavaScript and can be implemented easily as well. SOAP APIs are also convenient with JavaScript but don't support for greater implementation.

[Nikita]

Hi Saddam,

Notification Builder is used to Sending customized notifications when important events occur. For example, alert an account owner if a new support case is logged while trying to close a deal. Or, send a notification for a unique workflow built entirely with custom objects. Previously, you could send only standard notifications for use cases predefined by Salesforce. Notification Builder puts you in control of who needs to know what and when.

[Nikita]

Hi Saddam,

A fieldset is a grouping of fields. Adding fields, removing and reorder fields can be possible only with FieldSets only. FieldSets are used to display fields in VF pages. These are very useful in managed packages.

For example, you could have a fieldset that contains fields describing a user's first name, middle name, last name, and business title.

[Nikita]

Hi Saddam,

SetUp Objects:Setup objects are objects that are used to interact with the metadata. Common example is the User, Profile, Layout object.

Non-SetUp Object: Every other objects like those which are native(Standard Objects) and Custom Objects fall into the category of Non-Setup Objects.

One important note is that we cannot perform DMLs on setup and non-setup objects in the same transaction. Workaround is that you need to use asynchronous requests (@future) or use batch as it runs in its own system context.

In the test class, you can use System.RunAs with two different users to separate out transactions for setup and non-setup objects.

[Nikita]

Hi Hariom,

A lightning:outputField component displays the field value in the correct format based on the field type. It represents a read-only display of a label, help text, and value for a field on a Salesforce object.

[Nikita]

Hi

Profile with “Transfer Record” permission will allowed profile to transfer ALL records for the object, as long as profile have Edit access to the object. Read again here “edit on object”, NOT “edit on record”, so this mean, profile will be able to transfer record owner even user do not have Edit access to that record.

[Nikita]

Hi Piyush,

In the Master-Detail Relationship, once you delete Master Record all corresponding Child Records get deleted.

[Nikita]

Hi Piyush,

Sandboxes are isolated from your production org, so operations that you perform in your sandboxes don’t affect your production org. Sandbox is a copy of your production organization. You can create multiple copies of your organization in separate environments for different purposes.When you create a sandbox, Salesforce copies the metadata from your production org to a sandbox org.

SandBox are following type

1. Developer Sandbox: A Developer sandbox is intended for development and testing in an isolated environment. A Developer Sandbox includes a copy of your production org’s configuration (metadata).
2. Developer Pro Sandbox: A Developer Pro sandbox is intended for development and testing in an isolated environment and can host larger data sets than a Developer sandbox. A Developer Pro sandbox includes a copy of your production org’s configuration (metadata).
3. Partial Copy Sandbox: A Partial Copy sandbox is intended to be used as a testing environment. This environment includes a copy of your production org’s configuration (metadata) and a sample of your production org’s data as defined by a sandbox template.
4. Full Sandbox: A Full sandbox is intended to be used as a testing environment. Only Full sandboxes support performance testing, load testing, and staging. Full sandboxes are a replica of your production org, including all data, such as object records and attachments, and metadata. The length of the refresh interval makes it difficult to use Full sandboxes for development.

[Nikita]

Hi Achintya,

WhoID in Salesforce refers to people things. So that would be typically a Lead ID or a Contact ID. The WhoId represents a human such as a lead or a contact. WhoIds are polymorphic. Polymorphic means a WhoId is equivalent to a contact’s ID or a lead’s ID. The label is Name ID.
WhatID in Salesforce refers to object type things. That would typically be an Account ID or an Opportunity ID. The WhatId represents nonhuman objects such as accounts, opportunities, campaigns, cases, or custom objects. WhatIds are polymorphic. Polymorphic means a WhatId is equivalent to the ID of a related object. The label is Related To ID.

[Nikita]

Hi Laveena,

The main differences between @future methods and Queueable Apex jobs are:

• When you enqueue a new job, you get a job ID that you can actually monitor, like batch jobs or scheduled jobs!
• You can enqueue a queueable job inside a queueable job (no more “Future method cannot be called from a future or batch method” exceptions). As for Winter ’15 release, you can chain a maximum of two queueable jobs per call (so a job can fire another job and that’s it!). With Spring ’15 release, this limit has been removed.
• You can have complex Objects (such as SObjects or Apex Objects) in the job context (@future only supports primitive data types)

[Nikita]

Hi Laveena,

Firing the force:createRecord event tells the app to use the standard create record page. You can’t catch errors that occur there, or alter the create page interface or behavior, for example, to show an improved error message. For this reason, it’s essential to perform access checks in your own code, before firing the event.

You can’t prepopulate system-maintained fields, such as Id or record modification time stamps. Default values for these fields are silently ignored.

So, You can't override the behaviour. You can build your own form and control the behaviour.

[Nikita]

Hi Achintya,

A perspective is a predefined layout of panels in the Log Inspector.

To manage your perspectives, click Debug | Perspective Manager.

• To switch to a different perspective, double-click the perspective name, or select it and click Open.
• To change the default perspective, select the perspective name and click Set Default.
• To delete a perspective, select the perspective name and click Delete.
• To create a custom perspective,
  • In the Developer Console, open a log in the Log Inspector.
  • Click Debug | View Log Panels and select the panels you want to include in the perspective.For a list of available panels, see Log Panels. If you modify a perspective, an * is appended to the perspective name until it is saved.
  • To save your changes, click Save Perspective. To create a new perspective, click Save Perspective As and enter a new name.

[Nikita]

Hi Laveena,

Salesforce record Id uniquely identifies each record in salesforce. Salesforce record Id can either be 15 digit or 18 digit. 15 digit salesforce record id is case sensitive and 18 digit salesforce record id is case insensitive.
15 digit case-sensitive version is referenced in the UI and also visible in the browser
18 digit case-insensitive version which is referenced through the API

[Nikita]

Hi Hariom,

You must specify a rerender attribute in the <apex:actionFunction> tag! Without this, the generated function does take any parameters

[Nikita]

Hi Laveena,

Steps for approval process are

1. Navigate setup -> Create -> Workflow & Approvals -> Approval Processes.
2. Select Object for the new approval process.
3. Click on  Create New Approval Process and choose Use Standard Setup Wizard from the drop-down button
4. Enter the Process name, Unique Name and description for your process.
5. Specify the Entry criteria.
6.  When you define approval steps, you can assign approval requests to different users. One of your options is to use a user field to automatically route these requests. If you want to use this option for any of your approval steps, select a field from the pick list below. Also, when a record is in the approval process, it will always be locked– only an administrator will be able to edit it. However, you may choose to also allow the currently assigned approver to edit the record.
7.  Define initial submission actions.New field update / email / task -> Conditions -> save.
8.  Define approval steps.Manager step -> click on new approval step button -> provide the name -> all record should enter this step -> select approver manually and save.
9.  Final approval steps.New field update / Task / Email according to the field provides the condition and save.
10.  Final Rejection actions.New field -> provide the conditions and save.

Once the salesforce approval process is activated no more steps can be added.

[Nikita]

Hi Achintya,

You can have only one standard object controller and multiple controller extensions.

[Nikita]

Hi Piyush,

DashBoard support Summary and Matrix report type and dashboard support tabular also if the tabular report has limited rows (maximum 10).

 

[Nikita]

Hi Achintya,

From Setup, in the Quick Find box, enter Users and then select Prospector Users. In the Data.com Users section, find your name and see what your monthly limit is and how many records you’ve already added or exported during the month. Your administrator sets the monthly allowance, which expires at the end of each month, regardless of whether you’ve met your limit.

If adding a set of records causes you to exceed your addition limit, you’ll see a message that tells you how many additions you have remaining. If you still need to add more records, contact your administrator.

[Nikita]

Hi Achintya,

Actions available in workflow rules are following

• Email Alert
• Field Update
• Flow Trigger(Immediate Action)
• Outbound Message
• Task

[Nikita]

Hi Prachi,

You can request and review the Email Log. It will list all emails sent through Salesforce.com. Email logs can be found under Setup -> Monitor -> Logs -> Email Log File. Use the "Request a Log" button to determine the time frame for the log and list yourself as the Notification Recipient. You'll receive an email when it's complete and you can download and review the file. If the email was sent for the approval it'll be listed in the log.

[Nikita]

Hi Prachi,

When you create the Link using URLFOR() in Email Template, it creates a link in “http” format instead of “https” and thus causes end-user to logged into salesforce again.

So instead of

<a href='{!URLFOR(‘/apex/SomePage’, null, [id=Some_Object__c.Id,retURL=”/apex/SomeOtherPage”])}’>Go to SomePage here!</a>

We can use something like :

<a href='{!SUBSTITUTE(URLFOR(‘/apex/SomePage’, null, [id=Some_Object__c.Id,retURL=”/apex/SomeOtherPage”]),’http:’,’https:’)}’>Go to SomePage here!</a>

[Nikita]

Hi Prachi,

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,

Aura Components: Using Aura Framework We can build apps completely independent of the Data present in our Salesforce org.When we use Lightning Components  Framework We do not need to worry about the optimization of our apps for different devices as  Components take care of that by themselves.

SLDS: By Using SLDS We can make our apps responsive and can also provide Look and feel similar to the Lightning Experience. It provides a robust grid system because of which It is easier to build responsive layouts that work elegantly across different screen sizes.

Thanks.