Setup>Task Record Types>Record Type>Subject :
- Remove any values from the 'Selected Values' over to 'Available Values'
- Re-add the removed values from 'Available Values' back to 'Selected Values'
Hope this helps!
I have found an Idea which could be the behavior you are referring to:
I'm trying to figure out how to set a lookup field to a contact automatically. When an opportunity meets certain requirements, we have a lookup field that is always populated with the same ID on the related account. I know that workflows can't acheive this and it seems that I can't statically assign a value to the lookup through orocess builder. Am I correct to assume that some development work would be needed to achieve this or is there a way to make it work through an autolaunched flow?
Thanks in advance
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?
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 Database.com Editions
Standard Objects are not available in Database.com
|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
- Tracking Field History for Custom Objects
- History Tracking Implementation Tips
- Service contracts
- Contract line items
To set up field history tracking:
- Click and select the object you want to configure.
- Click Fields.
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.
- 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.
- Choose the fields you want tracked.
- Click Save.
To track field history for custom objects:
- Click and click Edit next to the name of the custom object.
- 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.
- Click Save.
- Select the name of the custom object.
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.
- Choose the fields you want tracked.
- Click Save.
- 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 Force.com API.
- Field updates are tracked in the History related list if you have set history tracking on those fields.
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.
IF( AND( MONTH( date ) = 2, DAY( date ) = 29, NOT( OR( MOD( YEAR( date ), 400 ) = 0, AND( 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 ) ) )
I'm currently using another Chrome extension, Gmelius, for snoozing emails. It would be great to replace this completely with Inbox.
Its a product of ChoudHq, they have various range of Gmail, Google drive productivity tools: https://www.cloudhq.net/chrome_extensions#index
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?
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.
But you can use custom code to achieve that:
"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."