[SalesForce] Validation rule for date is greater than

Hi I am making a validation rule to check if a billing date end is earlier than the billing date start. My syntax appears to be wrong however.

My current validation formula:

DATEVALUE(Billing_Period_Start__c) > DATEVALUE(Billing_Period_End__c)

Error: Incorrect argument type for function 'DATEVALUE()'.

Fixed by removing DATEVALUE from the validation formula.

Best Answer

It seems that your fields Billing_Period_Start__c and Billing_Period_End__c are of type Date, hence the error. Remove the DATEVALUE() function from your formula and you should be good to go.

As mentioned in the DATEVALUE() function documentation

DATEVALUE() - Returns a date value for a date/time or text expression.

Its worth noting and reading the tips section of the article given above, out of which, two are related to your issue

tips

If the field referenced in the function is not a valid text or date/time field, the formula field displays #ERROR!

When entering a date, surround the date with quotes and use the following format: YYYY-MM-DD, that is, a four-digit year, two-digit month, and two-digit day.

Related Solutions

[SalesForce] Validation rule for new record

Try this,

ISNEW() && Service_Date__c <= today()

IsNew doesn't neeed any parameter. It returns true for insert and false for rest.

[SalesForce] Validation rule to restrict record creation/Update for future month and year

Seems like you have a picklist field that contains a month, another picklist that contains a year and a percentage. You want to stop people from changing the percentage field if the month/year are in the future and allow them to change it if the fields are in the past.

I wouldn't use last modified date as I'm not sure how that will behave in the validation rule, instead use Today():

AND(
 ISCHANGED(PercentageField__c),
 MONTH(TODAY()) > VALUE(TEXT(MonthField__c)),
 YEAR(TODAY()) > VALUE(TEXT(YearField__c))
)

Note, that this would require your month field to be a number instead of a string (1, 2, 3, etc instead of jan, feb, dec).

If you absolutely must have jan, feb, dec, etc. as your values. The formula gets kind of crazy (so crazy that I'm not even gonna try to give an example).

You can also consider a workflow that sets a hidden field so that if user picks January, the workflow will set the hidden field to 1 so you can use it in the formula.

Best Answer

tips

Related Solutions

[SalesForce] Validation rule for new record

[SalesForce] Validation rule to restrict record creation/Update for future month and year

Related Topic