I am trying to write a Validation Rule on the Lead object. I have two pick list fields, 'Status' and 'Reason for Closing'. When the 'Status' is selected 'Closed' I need there to be a value selected for 'Reason for Closing'. This is what I have so far:
Any help would be much appreciated, thanks in advance.
When you say None is a text value, do you mean have you created None as an picklist value in the system.
In any case I would go with Dependent picklist options as suggested by Hybin and make the Reason for Closing field mandatory on pagelayout.
Steps to follow
1. Create a Dependent Picklist
Status as the Controlling field
Reason for Closing as the Dependent field
2. Create a Field Dependecy Matrix so that the Reason for Closing Value are only included for Closed Status
3. Make the Reason for Closing field required on the page layout.
If the Delivery Date is >30 days from the Closed Date I want to set the reminder date to 14 days after the closed date.
If the Delivery Date is <30 Days I want to set the Reminder Date to be based off the Effective date
I can't seem to figure out the formula
But in Classic mode,how to create folder?
Can anybody please guide me on this?!
I have a question regarding multi-select picklists and checkbox. I need to know the pros and cons of using either multi-select picklist and checkbox. My client does not recommend using multi-select picklist as they are worried of reporting. Hence they are sticking to checkboxes because of reporting.
I recently heard that in Spring/Fall 2016 there were few updates that were implemented to multi-select picklist. I am not quite sure though. My client has asked me regarding the best practices either to implement multi-select picklists and checkbox.
Can anybody suggest me based on the above scenario what must be implemented either the multi-select picklist or checkbox?
Thanks a lot !!!
- MSP's suck for reporting
- Pose challenges for merges
- Pose challenges for automation like workflow rules, process builder
- Pose challenges for formula writing
Roles are one of the ways you can control access to records. They also impact reports (e.g. "My Teams" filter). Roles come into play if your security model (OWDs) are set to private. A little more on Roles and how they impact security:
Profiles help determine record privileges. Assuming the User can see the record, Profiles determine what the User can do, view or edit on that record. Profiles control other system privileges as well (mass email, export data, etc)
I've researched my question in Help, and almost everything I've tried has not worked. the email button in Summer '17 Sandbox is missing from the opportunity. I checked email deliverability, set to "all". checked global layout for email, it's there. checked opportunity page layout. "send email" is already in the lightning section. checked to make sure the correct layout is assigned. not until I created the "action" and added it to the opportunity layout did it appear...in the page layout editor, it appears right next to the "send email" button. So, long story longer, it's fixed, but not sure why the original button is not displaying.
any direction is appreciated!
-Erik "always marks best answer" Peterson
If lead source equals Trusted Referral, then the Referral field must be filled out. Values below in Referral are the only options available.
ISPICKVAL ( LeadSource , 'Trusted Source(Referral)'),
NOT( ISPICKVAL(Referral__c, 'Partner Referral')),
NOT( ISPICKVAL(Referral__c, 'Board Referral')),
NOT( ISPICKVAL(Referral__c, 'Other Trusted Source Referral'))
Thank you for your help.
This way it will be enforced only when a value is chosen in the Controlling Field(even if you see the Red Mark next to the Dependent Field with Controlling Field still empty). This will impart the best User Experience as opposed to a Validation Rule.