[Parul]

Addin some more points:

Namespace prefixes are used in managed Force.com AppExchange packages to differentiate custom object and field names from those in use by other organizations.

Example:

your field name - test__c

and your Namespace name is "app" then resultant field name will be "app__test__c".

It is a very useful feature so that the API name of the Managed package should not conflict with native fields API Name.

[Parul]

DML operations on certain sObjects, sometimes referred to as setup objects, can’t be mixed with DML on other sObjects in the same transaction. This restriction exists because some sObjects affect the user’s access to records in the org. You must insert or update these types of sObjects in a different transaction to prevent operations from happening with incorrect access-level permissions. For example, you can’t update an account and a user role in a single transaction. However, deleting a DML operation has no restrictions.

[Parul]

You can avoid recursive trigger in salesforce using static variable.

[Parul]

you can perform DML in trigger from future methods with callout=true.you can re-query for them and act on this new reference, then perform an update.

[Parul]

Salesforce is a company andSalesforce.com is a Customer Relationship Management (CRM) application developed based on Software as a Service (SaaS). Force.com is a platform that helps developers and business users to build powerful enterprise applications.

[Parul]

the standard object cannot be on the detail side of a relationship with a custom object. ... To create a many-to-many relationship, simply create a custom junction object with two master-detail relationship fields, each linking to theobjects you want to relate. See the Salesforce online help for details.

[Parul]

Visualforce provides the facility for delivering template-driven web pages and email messages. In addition, developers wishing to simply utilize a basic container and maintain more control over the lifecycle of the request may choose Visualforce pages. Finally, organizations that can’t use Apex code can’t use Lightning Components, but they can use Visualforce.
Thanks

[Parul]

On standard object can not be on detail side of the relationship I think

[Parul]

Aura supports partitioned multi-tier component development that bridges the client and server. It uses JavaScript on the client side and Java on the server side.

The Aura framework. Note that the open source Aura framework has features and components that are not currently available in the Lightning Component framework. We are working to surface more of these features and components for Salesforce developers.

 

Thanks

Thanks.

[Parul]

Some of the limitations of Joined Reports on dashboards include:

The only items on the dashboard that can be modified are the ‘Display Units’ and ‘Drill down To’ (a very cool, often overlooked feature that allows a Dashboard Component to link to another Dashboard instead of a source report).

Joined reports in dashboard view can’t be filtered based on data.
Dashboards that only have Joined reports can’t have a filter added.
Just because a field contains the same data across objects does not mean they are guaranteed to allow grouping across blocks.  For example, if a lookup field to account name in a managed package has a different label than Account, grouping may not be possible.
Joined reports require that the new user interface theme be enabled. Users without the new theme are unable to create, edit, or run joined reports. See Enable New User Interface Theme.

[Parul]

In Field dependency, we have to fields controlling filed and dependent field. When a selection is made the controlling field controls dependent picklist values.

[Parul]

Select the master record (the one you want to keep), and then select any fields in the new record that you want to merge into the master record. Data in these fields may override the existing data inthe master record. Click OK.

Addin More Points Yes it is, although you can only merge contacts within an Account. IN the Account page, navigate to the COntact related list and Click Merge Contacts. You will be presented with Options there.

[Parul]

Adding some points:

Data Loader offers the following key features:An easy-to-use wizard interface for interactive use
An alternate command-line interface for automated batch operations (Windows only)
Support for large files with up to 5 million records
Drag-and-drop field mapping
Support for all objects, including custom objects
Can be used to process data in both Salesforce and Database.com
Detailed success and error log files in CSV format
A built-in CSV file viewer
Support for Windows and Mac

Thanks

[Parul]

Yes, So you need to specify multiple approvers in the Automatically assign to approver(s) option and then choose Require unanimous approval from all selected approvers.

[Parul]

Dynamic approval routing allows you to specify the approvers for each record using User lookup fields on the record requiring approval. The fields are populated using Apex, using data from a special custom object (the "approval matrix") that contains all the information needed to route the record. The approval process then uses the values in the lookup field, rather than the limited pool of users available in the so-called static process. This provides more flexibility: you could route to different people based on region or some other criteria related to the record, rather than having to write multiple static approval processes in order to perform the same functionality.

The steps for dynamic approval routing are:

Create lookup fields on the object being approved.
Create a custom object that will be used as an approval matrix.
Populate the approval matrix.
Create Apex code to fill in the lookup fields on the record, from the approval matrix.
Create or update an approval process to utilize the new lookup fields.

For example: suppose you have a position object and there are 3 levels of approvers. You need to route the record to different approvers based on the department and pay grade. You would:

Add custom lookup fields (to User) on the Position object, called Approver 1, Approver 2, and Approver 3.
Create an approval matrix object that stores all the fields used in routing: pay grade, department, and lookup fields to the User object for each approver.
Create the approval matrix records. For position, one might route records with the department of Engineering to high-level Engineering managers as approvers, whereas the department of Sales would have high-level Sales managers as the approvers.
Use an Apex trigger to populate the lookup fields on the Position record when the record is created, based on the values in the approval matrix.
On the approval process, in the approval steps, set the Assigned Approver to the appropriate lookup field on the record (Approver 1, Approver 2, and Approver 3).

[Parul]

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 then select sum function

[Parul]

Hi
Managed Packages: Managed packages are typically used by salesforce.com partners to distribute and sell applications to customers. Once the components are installed from a managed package, the components cannot be edited in the organization they are installed in.
Unmanaged Packages: Unmanaged packages are typically used to distribute open-source projects or application templates to provide developers with the basic building blocks for an application. Once the components are installed from an unmanaged package, the components can be edited in the organization they are installed in.
Thanks

[Parul]

Some of the limitations of Joined Reports on dashboards include:

The only items on the dashboard that can be modified are the ‘Display Units’ and ‘Drill down To’ (a very cool, often overlooked feature that allows a Dashboard Component to link to another Dashboard instead of a source report).

• Joined reports in dashboard view can’t be filtered based on data.
• Dashboards that only have Joined reports can’t have a filter added.
• Just because a field contains the same data across objects does not mean they are guaranteed to allow grouping across blocks.  For example, if a lookup field to account name in a managed package has a different label than Account, grouping may not be possible.
• Joined reports require that the new user interface theme be enabled. Users without the new theme are unable to create, edit, or run joined reports. See Enable New User Interface Theme.

[Parul]

Here are some use cases and examples for functionality that can easily be build declaratively, without writing a single line of code:

Instead of writing Triggers, we can automate Field Updates using Workflow – automatically populating a field with a default value or updating a field based on the value of another field is a pretty common requirement. Workflow can address the basic use cases just as well as writing an Apex Trigger.

[Parul]

Record Type:

Allows you to define different sets of picklist values for both standard and custom picklists
Record Types help you implement your custom business processes

Use Record Types:
To segment picklist values specific to business needs
Examples: segment by division, product line, or region
Easier administration – fewer fields to maintain.

Sample Scenario:Support Representatives create cases based on the customer reported problems in Case Object.
If the requirement is to fill the different set of fields for the different case types you can create record types and for each record type you can assign a different page layout by including a different set of fields.
After creating the multiple record types, if you click on New case button you will see an intermediate screen where you can choose the type of record type based on that it will show the corresponding page layout.
If you are displaying same picklist field in multiple record types and requirement is to show different picklist values based on the record type then you can configure in record type detail page.
For the following objects, you can see the additional step to create the record type -Lead –> To control Lead Status field picklist values you need to create Lead process additionally to control the picklist values of Lead Status which will decide the lead life cycle.
Opportunity –> To control Stage field picklist values you need to create Sales Process additionally to control the picklist values of Stage which will decide the Opportunity life cycle.
Case –> To control Status field picklist values you need to create Support Process additionally to control the picklist values of Status which will decide the Case life cycle.
Solution –> To control Status you need to create Solution Process additionally to control the picklist values of Status which will decide the Solution life cycle.

[Parul]

There are 3 types of  Salesforce.com Portals:

• Customer Portal
• Partner Portal
• Self  Service Portal

The feature differences are that Partner Portal exposes the Leads and Opportunity objects whereas the Customer Portal does not.

Customer Portal is to support your customers.

Partner Portal is to support your Partners. Partner users are Salesforce users with limited capabilities. They are associated with a particular partner account, have limited access to your organization’s data, and log in via a partner portal. But when compared, Partner portal is costlier than Customer Portal.

Self-Service provides an online support channel for your customers – allowing them to resolve their inquiries without contacting a customer service representative.

A Salesforce.com Customer Portal is similar to a Self-Service portal in that it provides an online support channel for your customers—allowing them to resolve their inquiries without contacting a customer service representative.

[Parul]

Currency format of different countries are different,so we assume here “1,000.00” as currency format because in most of English countries this currency format is used.Let’s try this code-

String i=’2050066.50′;
String s = ( Decimal.valueOf(i==null||i.trim()==”?’0′:i).setScale(2) + 0.001 ).format();
String p = s.substring(0,s.length()-1);
System.debug(p);

 

Thanks

[Parul]

Hi

public static String currency(String i) {
String s = ( Decimal.valueOf(i==null||i.trim()==”?’0′:i).setScale(2) + 0.001 ).format();
return s.substring(0,s.length()-1);
}

Hope it may help

[Parul]

Here’s an example of how you might use ui:scrollerWrapper to make a tab’s content scrollable using the lightning namespace:

<aura:component>

<lightning:tabset>

<lightning:tab label="Item One">

<ui:scrollerWrapper> <div> Tab Content Goes Here </div>

</ui:scrollerWrapper>

</lightning:tab>

<lightning:tab label="Item Two"> Sample Content Two </lightning:tab>

</lightning:tabset>

</aura:component>

 

Thanks

[Parul]

Adding some points:

If you’re developing for Lightning Experience, this badge indicates a component that can be supported on mobile through the use of the ui:scrollerWrapper component. More information about ui:scrollerWrapper can be found in the Lightning Developer Guide. The Lightning Design System scrollable class does not bypass the “Pull to Refresh” scrolling behavior on mobile devices, so using ui:scrollerWrapper allows you to set up scrollable content areas on mobile devices that don’t interfere with other behavior.

 

Thanks