Changing User Email Without Sending Email Notification

In this post we will learn how to change the Email id on User record without sending email notification t the user.

Default Functionality:

In Salesforce user record, if we have to update the email id of the user, we can Edit the user record for that user account and the email notification will be sent to the user on updated email id to confirm the same. Once the user confirm the changed email id via a link in the Salesforce email notification then only the new email id will reflect on Salesforce User record.

Problem:

Many time, if some user leaves the organization or we want to redirect the notifications to some other email id till the time replacement comes or in the Sandbox we want to change the email id to point to some test email id which is not real. Most of the time the Sandbox email are not the real ones so it becomes difficult to confirm new email id after changing it. In these scenario, we don't want to send the email notification to confirm the new email id, the new email id should be reflected without confirmation.


Solution:

Go to the User record for which you want to update the email id. Update/change the email id and then scroll down and click the checkbox "Generate new password and notify user immediately" as highlighted in below screenshot. This will make sure there is no email notification due to change/update of email id and the email change will immediately reflect on user record.

Thanks for reading! See in the next blog post.

Salesforce Community Cloud Consultant Certification: Passing Hacks

How to Pass Salesforce Community Cloud Consultant Certification

I appeared for Community Cloud certification this month and cleared it in the first attempt to become 7X Salesforce Certified. (Sales, Service , Community, App builder, Platform, Admin, Advanced Admin)

In this blog I am going to share the tips and trick to pass the Community Cloud Certification.

As you all know for every certification Salesforce provides you with the study guide which you can go through on the Salesforce Certification site.

Best way to start preparation is to go through the Study guide and get into the mentioned topics; having community implementation experience is key advantage.

Let me describe important points which will help you crack this exam:

1. Sharing Model: This is always has first priority but in terms of Community study:
     - External sharing model
     - Public access setting/ guest access to community
     - Moderation Permissions
     - Portal & community user access

2. Community Implementation: This is crucial as 15-20 questions were focused on this
     - Study different Templates mainly Napili as most of the question were related to this template.
     - Partner Central, VF + Tab & Customer Account Portal has less weightage
     - Community Workspace: go through each menu in this
     - Gamification i.e. Leaderboard,  Contribution points ,levels etc.
     - Community Builder: Very important; 10-12 questions were related to this topic.
     - Community Migration

3. Community Licenses: Understand it really well. 5-6 questions were related to this topic.

Here are the Notes that I made for my own reference and will be very helpful for you as well!

1. Total number of communities: 100 (Active + Inactive)
2. Community Licenses: Customer Community, Customer community Plus, Partner community, Employees community
3. Community template is based on the use case that you are building
4. Topics in Napili Template: 25 main topic and then 10 subtopic, upto 5 level
5. Super User access
6. Delegated Admin: Create & update user, Reset password and deactivate user
7. Sharing Sets to share records in Customer community
8. Moderation rules: Content criteria & Member criteria
9. Guest user access
10. Community Migration: You can update the community but not create one in production.
11. Login to community via social media : Configure Authentication Provider
12. Go through Community Roll out Trailhead 
13. Go through: Community migration with Change set
14. Go through: Ways to deploy communities

Hope above resources will help you to pass the exam.

Wish you a good luck! Please leave comments below!

Salesforce Winter'18 Release: Top Features

Salesforce is bringing cool feature set in it's Winter'18 release:

Lightning Experience Related

• Cool Animation effect on the footer components

• Themes and Branding

• More Global actions in LEX

• New Utility Bar Item - Quip

• Omni Channel is no more a Beta feature

• New Step in the App Creation Wizard to add Navigation Rules

• Lightning Dashboard Tables in Beta

App Cloud Related

• New Standard Objects

• Content Deliveries holds Public Links too

Community Cloud Related

• New Template added

• Ability to create your own template

• More options on CMS Connect functionality

• New Library Component (No Idea about the functionality)

Key Dates:

12 Inspirational Quotes to Kick Off the New Year

sforce.co/1ydtYnA 

Tracking First Response on Case Record

Tracking First Response on Case based on Case Comment 

This is common requirement to track the First Response time on Case based on the first Case comment.

Here is the simple Solution:

1. Create a custom field of type Date/time called first response time on Case object.

2. Create a workflow rule on "Case comment" object"  with criteria where first response time is NULL.

Screenshot:

3. Create a Workflow Field update on this rule to update the first response to NOW().

Screenshot:

4. Finally Activate the Workflow Rule.

Hope this will help you.

Salesforce:View state Best Practices

View state Best Practices

Most of us get error regarding "Maximum view state size limit (135KB) exceeded."

This post talks about the Best Practices to avoid this error& Optimizing size of View State:

1. Minimize number of form on a page: Assume a page contains two forms - form 1 and form 2. Irrespective of which form the user submits and causes a post back, the view state for the page needs to get transferred. To support this, each form on your page will have its own copy of view state.

2. Declare variable as transient: An instance variable declared as transient is not saved and is not transmitted as part of the view state. If a certain field is needed only for the duration of the page request and does not need to be part of the view state, declare it as transient.

3. Refine your SOQL to only retrieve the data needed by the page: Only retrieve (and store) the fields you need and also filter the data to only retrieve data needed by the page.

4. Refactor your pages to make its view stateless: Instead of using apex:commandLink or apex:commandButton components (which needs to be inside a apex:form component) to invoke an action, use an apex:outputLink or other non action method instead and implement the action through an apex:page action attribute - where it makes sense.

5. Use custom objects or custom settings to store large quantities of read only data

Hope this will help you! 

Salsforce Analytic Wave!!!

Salsforce Analytic Wave!!!

Here comes one more exciting Cloud: 

Salesforce Delivers Wave, the Salesforce Analytics Cloud