#Validation Rule6 discussing

Hey Andy, 

There are several things... 

First of all, you should consider to use the correct developer names of the record types. Those are the names listed under the 'Record Type Name' for the given record type:

Next your formula is missing one closing parenthesis at the end. However, the logic also needs to use AND () instead of OR () for the record type checks. 

So the correct formula for your VR is the following: 

AND ( 

RecordType.DeveloperName <> 'ACH_Customer_Funds_Movement', 

RecordType.DeveloperName <> 'Direct_Customer_File', 

RecordType.DeveloperName <> 'Fintech', 

RecordType.DeveloperName <> 'Fiserv_Premier_Customer_Funds_Movement', 

RecordType.DeveloperName <> 'Klarivis', 

AND ( 

ISBLANK (Not_Set_as_Pay_Out__c), 

ISBLANK (Set_as_Pay_Out__c) 

) 

) 

Best 

Serkan

Create this validation rule on Contact object. 

AND(

NOT(ISBLANK(AccountId)),

MailingPostalCode <> Account.ShippingPostalCode

)

HI @Samaparimal Reddy

I am from the Trailhead Help Team. Can you please confirm if you're still seeing an issue? If yes, can you please let us know so that we can look into it and can help you further ? 

Thank You! 

++TrailheadHelpFollowUp

@Elissa Stern I've seen this done in an Event App with custom metadata. 

Essentially you create a custom metadata object called "Discount Codes". You add to it a field that stores the code "20OFF". You also can create a field that stores the percentage off, or dollar amount off. (you can do both, but it gets a little more complicated). Then a field for the expiration date.  ( There is no reason you can't do a similar thing with a custom object, particularly if you have a large volume of these.) Something to keep in mind is that you are gonna want the "20OFF"  to be a unique identifier within the expiration timeframe.  

The tricky part is going to be providing a good UX in flow to actually check the discount.  Without a custom LWC, it will be hard to mimic the UX you are familiar with at most checkouts.  Click a button and get immediate feedback. ( It can be done though! but might not scale well if you have a large number of these active at one time.)

Anyway, the sketch of it would be, to take the discount code entered by the end user. Attempt to retrieve the custom metadata object (done using the standard GET records node), check if you found one, and that the expiration hasn't passed. If so apply the discount. If not display a message telling the user that the code doesn't exist or is expired!

Hope that helps!

Here's one I wrote using a CASE function and some basic math that you can hack up and use. 

 CASE( StageName , 

 "Prospecting",1, 

 "Qualification",2, 

 "Needs Analysis",3, 

 "Value Proposition",4, 

 "Id. Decision Makers",5, 

 "Perception Analysis",6, 

 "Proposal/Price Quote",7, 

 "Negotiation/Review",8, 

 "Closed Won",9, 

 "Closed Lost",9,0) 

 < 

 CASE(PRIORVALUE(StageName) , 

 "Prospecting",1, 

 "Qualification",2, 

 "Needs Analysis",3, 

 "Value Proposition",4, 

 "Id. Decision Makers",5, 

 "Perception Analysis",6, 

 "Proposal/Price Quote",7, 

 "Negotiation/Review",8, 

 "Closed Won",9, 

 "Closed Lost",9,0)

Sure, try this.

Start with all the fields that should not be blank - street, city, country.

Then you hvae two conditions. Either there is a Country with states (province), then state should have a value. or a country without states, then you don't need a value.

AND(
    NOT(ISBLANK({!Address.street})),
    NOT(ISBLANK({!Address.city})),
    NOT(ISBLANK({!Address.country})),
    OR(
        AND(
            ISBLANK({!Address.province}),
            CASE({!Address.country},
                "Australia", 1,
                "United States", 1,
                "Mexico", 1,
                0
            ) = 0
        ),
        AND(
            NOT(ISBLANK({!Address.province})),
            CASE({!Address.country},
                "Australia", 1,
                "United States", 1,
                "Mexico", 1,
                0
            ) = 1
        )
    )
)

Hey Mit, 

I wonder if you could do something that checks to see if the To Address and CC Address contains a ;. If so, that would indicate there are multiple addresses. 

You could then have the flow essentially "loop" through that string, parse out each email address and check those individually. I've shared a response here that details how you can use flow to cycle through a comma separated string, or in this case semi-colon separated: https://trailhead.salesforce.com/de/trailblazer-community/feed/0D54V00007BID5hSAH

Thanks,

Mikey