[SalesForce] Validation rule is not working as expecting

Hi i got a requirement like create a validation rule based on probability.

The requirement is user cannot modify some custom field called forecast units If probability is under 70%

So, i write a validation rule like

AND(ISCHANGED( Forecast_Units__c ),Probability < 0.70)

It works fine but when i create any opportunity the validation doesn't work
can anyone help me

Best Answer

According to the docs

ISCHANGED function returns FALSE when evaluating any field on a newly created record.

So your validation will never fire when you are creating a record. You might want to add ISNEW() function which checks if you are creating a new record.

OR(
   AND(ISNEW(), NOT(ISBLANK( Forecast_Units__c )), Probability < 0.70),
   AND(ISCHANGED( Forecast_Units__c ),Probability < 0.70)
)

Related Solutions

[SalesForce] Validation rule to check picklist list values is not working if more than one word in picklist value

PICKVALS have a number of limitations that are often very difficult to work with.

In my experience, a rule that refers to a single value picklist can only refer to the current and previous value PRIORVAL of the picklist in a (valuefield, "textvalue") format. If it's a multi-select picklist, then you can use ISPICVAL(CONTAINS(valuefield, "textvalue1", textvalue2,...) or similar syntax (sorry, but I didn't have time to verify this is the correct way to order this before posting).

If you want the "Does not contain" or Boolean negative", you can use NOT(PICKVAL(valuefield, "textvalue") as an argument in your expression. What I've observed is that if you want if new value AND old value conditions type of validation rule, it's often best to set it up like: AND(ISPICKVAL(valuefield,"textvalue"), PRIORVAL("textvalue")). The editor will expect PRIORVAL to have an ISPICKVAL in front of it, but will only want one ISPICKVAL in the expression if there's two PICKVALS contained in the expression. The help on this is rather vague other than to tell you there are limitations on what you can do with PICKVALS.

Sometimes, it's nearly impossible to create a single validation rule for PICKVALS that address what you're trying to accomplish because they have so many limitations in SF. It can be very trying on one's patience and time-consuming. The syntax is quite different to what we're used to working with in APEX and other languages, or so it seems to me.

[SalesForce] Proper method to get validation rule into Production

While this method of copying it directly into production does technically work, it's generally a good idea to deploy it through a change set or another dev tool (Mavens Mate, Eclipse, IDE, Ant, etc.). The advantage of doing this is that all of your test code is run with the new validation rule, so you can see if the new validation rule causes any test failures in your production environment.

Let's say for instance, you have a trigger on your opportunity object that creates a new case if a certain attribute is set. This trigger passes your test code and works well in your production environment. Lets now assume you have a new Validation Rule on the case object that requires a certain combination of fields. Your Opportunity trigger that is creating this case does not set these fields so your trigger will now fail due to this validation rule. If you simply copy and pasted this rule into production, you will now start to have trigger failures on your opportunity object and you may not know why. This is particular important when you have multiple people maintaining an org. So for instance, you as the admin, created this VR, and the developer who maintains the trigger, had no idea.

If you had used a change set to migrate the VR, then your test code would have failed (assuming you have proper test code in place). Then you would know there was an issue with the trigger prior to it being in production and you can work on the trigger to work well with the validation rule.

So in short, will pasting it work, technically, yes. Is it a good practice, no.

I hope this helps.

Best Answer

Related Solutions

[SalesForce] Validation rule to check picklist list values is not working if more than one word in picklist value

[SalesForce] Proper method to get validation rule into Production

Related Topic