That serie of videos named: WHO SEES WHAT is excelent:
And the next on line courses:
Online course: Administration Essentials for New Admins and Administration Essentials for the
Other helpful resources:
Online course: Analyze Your Data with Reports
Online course: Configure Salesforce with Custom Fields
Online course: Customizing Profiles to Align with Your Business Needs
Online course: Getting a Head Start with Chatter
Online course: Getting Started with Managing Data
Online course: Managing Users and Troubleshooting Login Issues
Online course: Summarize Your Data with Dashboards
1) Create custom rollup summary field
Create a new custom field
Choose roll up summary as the field type
Give the field a name
Choose to summarize the Opportunities object and Count as the roll up type
Create a new rule
Give the rule a name
Use this formula:
Account.Count_of_Opptys__c > 1Enter the error message your users would see
Test it out!
Im trying to update a field on Case object when the value of a field on its custom child object changes. As per Salesforce help below this is possible in master detail relationship. Unfortunatately i need to use lookup relationship. Does anyone know how to go around it? I cant use cross object formulas either. Frustrating.
'You can use cross-object field updates for custom objects that are children of certain standard objects in a master-detail relationship. The standard objects which support cross-object field updates from custom objects are: Case'
For this you can use Process Builder.
Here is the Trailhead module component on it to get you started
Just in case you are trying to Roll-Up child record values, for this you could use Declarative Lookup Rollup Summaries (https://github.com/afawcett/declarative-lookup-rollup-summaries)
Then I just studied all of the different sections of the study guide.
How can i make a change in address require a change in the geolocation field which shows the LAT and LONG?
I want to keep my data consistent. When addresses change i want to make the user change the geolocation fields so the LAT and LONG are appropriate to the new location.
Please view request below
In the Opportunities object within the Stage picklist field, there are values “Ready” and “Closed”
In a custom object name Loan__c , I have a checkbox field name Uncollectable_On_Receipt__c
Below are the relationships that exist between the 2 objects
- Lookup relationship from Opportunity to Loan
- Lookup relationship from Loan to Opportunity
Request – When a user selects “Ready” or “Closed” in the Stage picklist field in Opportunity, I want the Uncollectable_On_Receipt__c in Loan__c = TRUE.
Question – Can I create a workflow Rule with a field update or can I Process Builder to accomplish my request? If I could use both, which one I should use?
- On the opportunity, create a custom checkbox field
- E.g. field name ‘Field X’
- Create an opportunity workflow rule
- Rule Criteria: ISCHANGED(StageName) && ISPICKVAL(PRIORVALUE(StageName) , "Ready") && OR(ISPICKVAL(StageName, "Closed Won"), ISPICKVAL(StageName, "Closed Lost"))
- NOTE: I used ‘Closed Won’ and ‘Closed lost’ – you need to OR together all the appropriate Stages for your org
- Field Update
- ‘Field X’ to TRUE
- Check the box for ‘Re-evaluate Workflow Rules after Field Change’
- Create a Process
- Object: Opportunity
- Criteria for Executing: Filter Condition
- Field: [Opportunity].Field X
- Operator: EQUALS
- Value: True
- Check the box for ‘Do you want to execute the actions only when specified changes are made to the record?’
- Immediate Action:
- Object: [Opportunity].Loan
- Field: Uncollectable_On_Recepit
- Value: True
Check out this blog post: https://rakeshistom.wordpress.com/tag/two-factor-authentication-for-community-salesforce/
These are typically labels that will appear somewhere else in the system, not necessarily on the Account object.
Take Contacts for example and Contact Roles. This is actually a different object, but the labels are listed under Contacts.
Same logic would apply for Account Team which is another object
Other times they might appear automatically on other objects that are related to Accounts instead of being formula fields