Ask Search:
Liz MarshallLiz Marshall 
on the standard object called 'activities' there is a standard field called 'subject' which is a picklist field. We have added some custom options to the picklist. Half of them seem to have vanished over the weekend.  When I edit the picklist they are all listed, how do I make them visible again to users from the usual 'log a call' button?
Best Answer chosen by Liz Marshall
Michael VillegasMichael Villegas
This is spooky! The same issue happened today with our org! I wonder if there's a bug or if Salesforce is making backend updates? However, I was able to "jiggle the handle" to return my missing subjects.

Setup>Task Record Types>Record Type>Subject :
  1. Edit
  2. Remove any values from the 'Selected Values' over to 'Available Values'
  3. Save 
  4. Re-add the removed values from 'Available Values' back to 'Selected Values'
  5. Save

Hope this helps!
Sam MeraSam Mera 
I have enabled Lightning Knowlege and added the files related list to the page layout however this does not show in the community. Is this a limitation or am I missing something? 
Best Answer chosen by Sam Mera
EdEd ( 
Hi Sam,

I have found an Idea which could be the behavior you are referring to:

Tracey AdamsTracey Adams 
Is there a way to know additional last modified information on individual fields on the account.

Say for example - Joe entered the original # of providers and then 2 months down the road - mary came in and changed it to another #?  is there a way to keep stacking and view the changes that were made on each field?  Like having a hover image pop up?
Best Answer chosen by Moderator ( 
Dan WoodingDan Wooding
You want field tracking. You can run a report and see when it was changed and who made the change. You can see the previous and current value in the report. I am not really sure you can add this to a single record to see the changes. Unless you check the record history at the bottom like on a case or you make a workflow rule that populates a text field with the priorvalue everytime it changes.

Actually you could probably make a few custom fields and update them with workflows but that's a lot of work for something that you can do with the report and it's already built in.

Tracking Field History

Available in: Contact Manager, Group, Professional, Enterprise, Unlimited, Developer, and Editions

Standard Objects are not available in

User Permissions Needed
To set up which fields are tracked: “Customize Application”

You can select certain standard and custom fields to track the history of related list of accounts, cases, contacts, contracts, leads, opportunities, solutions, and custom objects. Modifying any of these standard or custom fields adds a new entry to the History related list. All entries include the date, time, nature of the change, and who made the change. History data does not count against your organization’s storage limit. Note that not all fields types are available for history tracking. .

For more information on tracking field history, see the following:

Tracking Field History for Standard Objects

You can track field history for:
  • Accounts
  • Cases
  • Contacts
  • Entitlements
  • Service contracts
  • Contract line items
  • Contracts
  • Leads
  • Opportunities
  • Solutions

To set up field history tracking:

  1. Click Your Name | Setup | Customize and select the object you want to configure.
  2. Click Fields.
  3. Click Set History Tracking.
    • For accounts, contacts, leads, and opportunities, select the Enable Account History, Enable Contact History, Enable Lead History, or Enable Opportunity Field History checkbox. Deselect the checkbox if you do not want to track any changes. If you deselect the checkbox, the History related list is automatically removed from associated page layouts.

      This checkbox is not available for cases, solutions, or contracts because you cannot disable their history tracking. Certain changes, such as case escalation, are always tracked.

    • When you choose the fields you want to track, Salesforce begins tracking history from that date and time forward. Changes made before that date and time are not included. Note that some case, solution, and contract fields are preselected for history tracking, so changes to those fields are automatically tracked from the time your organization began using Salesforce.
  4. Choose the fields you want tracked.
  5. Click Save.

Tracking Field History for Custom Objects

To track field history for custom objects:

  1. Click Your Name | Setup | Create | Objects and click Edit next to the name of the custom object.
  2. Select the Track Field History checkbox. Deselect the checkbox if you do not want to track any changes. If you deselect the checkbox, the History related list is automatically removed from the custom object's page layouts.
  3. Click Save.
  4. Select the name of the custom object.
  5. Click Set History Tracking in the Custom Fields & Relationships section. This section allows you to set a custom object's history tracking for both standard and custom fields.

    When you choose the fields you want to track, Salesforce begins tracking history from that date and time forward. Changes made before that date and time are not included.

    If you deselected the Track Field History checkbox, the Set History Tracking button does not display.

  6. Choose the fields you want tracked.
  7. Click Save.

History Tracking Implementation Tips


  • You can select a combination of up to 20 standard and custom fields per object.
  • You cannot track the following fields:
    • History of formula, roll-up summary, or auto-number
    • Created By and Last Modified By
    • Expected Revenue field on opportunities
    • Master Solution Title or the Master Solution Details fields on solutions; these fields display only for translated solutions in organizations with multilingual solutions enabled
  • Field history is stored for 18 months.
  • To archive field history, you can:
  • If you use both business accounts and person accounts, review the following before enabling account field history tracking:
    • Field history tracking for accounts affects both business accounts and person accounts.
    • A maximum of 20 account fields can be tracked. This limit includes fields on person accounts and business accounts.
    • Enabling field history tracking on person accounts does not enable field history tracking on personal contacts.
    • To report on person account history, run the Account History report.
  • You can report on activated contracts whose fields are tracked by clicking New Custom Report on the Reports tab, selecting Contract Reports as the data type, and choosing Contract History.
  • If you disable field history tracking on an object, you can still report on its history data up to the date and time you disabled tracking.
  • You cannot disable field history tracking for an object if a field on the object is referenced in an Apex script. For more information, see Apex Code Overview.
  • If the parent record in a lookup relationship is deleted, the field history tracking for the child record does not record the deletion. For example, if a parent account is deleted, the Account History related list for the child account does not show the deletion.


  • When you enable history tracking for an object, be sure to customize your page layouts to include the object's history related list. For more information, see Customizing Page Layouts.
  • You cannot customize which opportunity fields are tracked in the opportunities' Stage History related list; however, you can choose which opportunity fields are tracked in the Opportunity Field History related list.
  • You cannot customize the History related list because it does not store data. The History related list links to data stored elsewhere.
  • When you delete a custom field, all of the field history data is deleted and changes are no longer tracked.
  • If you disable field history tracking on a custom object, then you cannot report on its field history.


  • Changes to fields with more than 255 characters are tracked as edited, and their old and new values are not recorded. For example, changes to long text area fields are tracked as edited.
  • Tracked field values are not automatically translated; they display in the language in which they were made. For example, if a field value is changed from Green to Verde, Verde is displayed no matter what a user's language is, unless the field value has been translated into other languages via the Translation Workbench. This also applies to record types and picklist values.
  • Changes to date fields, number fields, and standard field labels are shown in the locale of the user viewing the History related list. For example, a date change to August 8, 2005 shows as 8/5/2005 for a user with the English (United States) locale and as 5/8/2005 for a user with the English (United Kingdom) locale.
  • Changes to custom field labels that have been translated via the Translation Workbench are shown in the locale of the user viewing the History related list. For example, if a custom field label is Red and translated into Spanish as Rojo, then a user with a Spanish locale will see the custom field label as Rojo. Otherwise, the user will see the custom field label as Red.
  • Changes to the Amount and Quantity fields on opportunities are tracked even when the field is updated as the result of a change to an opportunity's products or schedules.
  • Changes to the Closed When Created field on cases are only tracked when the field is updated via the API.
  • Field updates are tracked in the History related list if you have set history tracking on those fields.
Max CamposMax Campos 
I'm sure this is easy but I'm not good with formulas. I have a date field and a picklist field, the picklist field contains the values (5, 10, 15, 20, 25, 30) I want to create a formula field that looks at the date, for example, 01/01/2017, then looks at the picklist field value, for example, 5, and adds the value to the number of years of the date field, so it would show 01/01/2022. Thank you for your help.
Best Answer chosen by Max Campos
Steve MolisSteve Molis
Here's what you'll need for Leap Years

Adding Days, Months, and Years to a Date
If you want to add a certain number of days to a date, add that number to the date directly. For example, to add five days to a date, the formula is date + 5.
Adding years to a date is fairly simple, but you do need to check that the future date is valid. That is, adding five years to February 29 (a leap year) results in an invalid date. The following formula adds num_years to date by checking if the date is February 29 and if the future date is not in a leap year. If these conditions hold true, the formula returns March 1 in the future year. Otherwise, the formula sets the Date to the same month and day num_years in the future.
    MONTH( date ) = 2,
    DAY( date ) = 29,
        MOD( YEAR( date ), 400 ) = 0, 
          MOD( YEAR( date ), 4 ) = 0,
          MOD( YEAR( date ), 100 ) != 0
  DATE( YEAR( date ) + num_years, 3, 1),
  DATE( YEAR( date ) + num_years, MONTH( date ), DAY( date ) )

Chris CollierChris Collier 
I'm trying out Inbox for my team, both the Android app and Chrome extension.  The Android app allows me to snooze an email to come back to my inbox later.  Is there any way to do this with the Chrome extension?

I'm currently using another Chrome extension, Gmelius, for snoozing emails.  It would be great to replace this completely with Inbox.
Best Answer chosen by Chris Collier
Deepak DwivediDeepak Dwivedi
Hi Chris, Please check out below link :

Its a product of ChoudHq, they have various range of Gmail, Google drive productivity tools:
Best Answer chosen by Ali Malla
Pritam ShekhawatPritam Shekhawat
No right now you can't disable global search for particular user or profile. You can promote and upvote this idea here Turn off Global search function for particular user or profile (
Aaron PersichAaron Persich 
I have built a flow and a button which is on the contact object.  When the user selects the button the flow will be kicked off and will create a custom related object record.  In the flow I need to map the OwnerId of the new record to the person who selected the button (Current User).  I am able the map the OwnerId to the Contact Owner Id but this is not ideal.  Is there a way I can map the OwnerId to the person who selected the button or the current user?  If so how can I accomplish this?
Best Answer chosen by Aaron Persich
Mayank SrivastavaMayank Srivastava

Create a formula field within the Flow as shown below:

User-added image

And then within the Record Update element, assign the owner ID to be the above variable. That's it.
G. C.G. C. 

We're using Lightning Sales Cloud, but also have Community Portal. Any ideas how I could display in Lightning if a customer is enabled/disabled as customer user?

We have to go back to Classic to enable/disable the contact, however my Sales and Support team need to be able to see if a contact is enabled/disabled on the contact record. 

I would think it's a formula field of some sorts, but not sure what to reference it to.

Best Answer chosen by G. C.
Ankush DurejaAnkush Dureja
Unfortunately that is not possible using configuration. There is an idea for that

But you can use custom code to achieve that:
Jules NeumerJules Neumer 
Previously, users would click "Select Converted Status" update the opportunity name and a contact and opportunity would be created. Now with the update, users are being prompted to a new screen and it appears as though the system wants them to create a person account, instead of a contact. We do not use person accounts so this is incorrect. Also, the error "Unable to find default record type" is now appearing. Users need to be able to edit the opportunity name and convert to a contact. Please help!

User-added image
Best Answer chosen by Jules Neumer
Naval SharmaNaval Sharma
From the Salesforce Dcoumentation :
"With person accounts enabled, you can convert leads to either person accounts or business accounts. Leads that don't have a value in the Company field are converted to person accounts. Leads that do have a value in the Company field are converted to business account.
We recommend you use different lead record types and page layouts to differentiate leads that will convert toperson accounts from those that will convert to business accounts. Specifically, remove the Company field from the page layouts for leads that will convert to person accounts. Then, make the Company field required on the page layouts for leads that will convert to business accounts.
If you convert a lead and attach it to a person account that someone else owns, that person account owner becomes the contact owner.
If you convert a lead that someone else owns and attach it to a person account that you own, the lead owner becomes the contact owner."
Liron WachsLiron Wachs 
I am going to attend the Admin certification exam this week and wanted to know from someone who attended this exam recently, if there are questions concerning Lightning Vs. Classic edition?
I understood that the questions that are asked are relevant to classic edition only, but I wanted to make sure that this fact is indeed correct and hasn't changed.
Best Answer chosen by Liron Wachs
Ankush DurejaAnkush Dureja
Hi Liron, 
Please check following study guide for salesforce adminstrator exam

Some of my colleagues recently appeared for exam and there was no question related to Lightning Vs Classic. And as per above 2 links as well, its not part of administrator exam.

Good luck for exam. :)