There Are No Errors in Salesforce Funny

2. Change a User's Email Address Without Sending a Confirmation Request:

Usually, when you change the email address on a user record, an email is sent to the new value asking the user to confirm the change. Only when the confirmation link in the email is clicked will the change be reflected in Salesforce. This happens regardless of how you update the email address; manually, API, etc. There is no way around it…or so I thought!

Turns out, if you change the email address AND check the "Generate new password and notify user immediately" checkbox (all the way at the bottom of the edit screen) then the email address gets committed right away, no confirmation needed! Obviously the catch is that the user then gets sent a new password…so it's not any better in some situations. I use this trick a lot in sandboxes.

You know how it is, you tell a user what their username is in the sandbox and tell them to use whatever password they were using in production when the sandbox was last refreshed… and they don't remember and ask you to reset it. So, you have to explain that they need to confirm a change to their email first (you get the picture). Now you can update the email and get them a new password in one shot.

3. Mass Email Activity Ghostbusting:

The scenario: you send a mass email to leads or contacts and you select the option to "store an activity for each mail". Then, after the email sends, you check out the activity history on one of the recipients and see the subject of the task shows as "Mass Email:" as illustrated below. The colon in there lets you know that something is meant to be there, but didn't quite make it there. Spooky…

So the secret (I found out years later) is that the activity stored reflects the description of the email template you send. Strange right? So give your email templates descriptions from now on before you send any mass mail… your activity histories will thank you.

4. Id Growth Formula:

This one is an oldie but goodie. Salesforce gives all records an 18 character Id, but sometimes they show up only as 15 characters. This is because if you are working in a case-sensitive system, the first 15 characters is enough for it to be a unique Id… but if you have the last three characters also, then even if you ignore the case the Id is still unique. Here's the cool part: if you have the 15 character Id, you can generate the last three characters to compose the 18 character Id.

5. The Secret Tab Trick:

This is a neat trick that came to me from Arrowpointe. As you know, when you create custom objects you can easily create a custom tab which allows you to create views from which you can view and manage the records in the object. Well, it turns out you can do this even if you haven't created a tab. All you have to do is go to your URL bar, and after the ".com/" enter the 3 character prefix of the object. The prefix is easy to find, it is the first three characters in the Id of any record in the object. You do this, and you'll be on a "secret" tab that otherwise you can't navigate to. Here is an example, note the cool little cube logo that shows up.

But in order for your Salesforce to work the most efficiently, you have to have a system in place to clean up, standardize and optimize your data. RingLead Data Management Solutions is the leading data management platform that can capture, clean, protect and enrich all of the data inside your Salesforce org in real time. Our cloud-based technology makes it easy to dedupe your entire database in minutes, and then prevent more duplicates from entering.

severinbefordents.blogspot.com

Source: https://www.ringlead.com/blog/salesforce-admin-tricks-you-didnt-know/

Share this post