Technical Instructor Force.com
Robert Foy
Managing Partner
Stony Point LLC
admin@df11qualityB071.com
df2011
Dirty Data.......Incomplete, inconsistent, duplicate, or outdated data
Four common use cases for validation rules
-- Conditionally required data
-- Ensuring proper data format
-- Enforcing data consistency
-- Preventing changes to data
Go get whitepaper from developer.force.com . Useful Validation Rules
Exercise 1.
Conference_Campaign_14_Days_or_Less
ISPICKVAL ( Type , "Seminar / Conference") && EndDate - StartDate > 14
Error: Campaigns of type Seminar/Conference can be no longer than 14 days.
Validation Tip: Time goes forward, so if you are counting up in time, Later is Greater
Formula fields
-- Performs a calculation when records are read
-- Outputs a read-only number, text, or data value
-- Can access related data
-- In the context of data quality, formula fields
> Derive values from other fields
> Prevents redundancy
Exercise 2.
Formula field on case object to show Account support level. Pulls from Account object
TEXT (Account.Support_Level__c)
** We could use this
Exercise 3.
Makes sure that Contact on Case is an Contact on the Account
Contact Name: Account Name IDEQUALSCase: Account Name ID
Limits result on lookup on Case
Exercise 4.
Define uniqueness across two or more fields. Good ways to use "unique" in field attribute and workflow.
Good Session. Will be employing some of these methods at Avalara on Solutions and will suggest for Cases.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.