Date_Add Caution

vinsnash

Using 4.9 #1301

I've just discovered that a syntax error is not caught and the function returns a null value. For instance I'd been using a variable number of days using a number of months times 30.42.

Example:

OBJ.EndDate=Date_Add(Obj.StartDate),(Obj.Months*30.42))

I keyed the rule into another process and made an error leaving out the second set of parenthesis.

OBJ.EndDate=Date_Add(Obj.StartDate, OBJ.Months*30.42)

The syntax checker did not catch the error and the process executes with out error except that OBJ.EndDate remains undefined.

rocketman

Although the user guide doesn't say, I'm fairly certain from a past experience that DATE_ADD requires an integer as the second argument.

It adds the specified number of days the the date in the first argument.

can you add .42 of a day?

Might be wrong on this but just a thought - and actually, both syntax look wrong unless its a typo. Try

OBJ.EndDate=Date_Add(Obj.StartDate,(Obj.Months*30.42))

vinsnash

Your right. I botched the syntax again. However, I have it right in a process and the calculation doesn't work there in a "CREATE OBJ WITH" function but will work when the rule is attached to an object. Haven't figured that out yet.

We have situations where enrollments can be for various periods. We let graduating high school seniors enroll for the summer months after graduation, some units attached to schools like to initially "pro rate" enrollments such that all expired enrollments occur on the same date, and adult volunteers can be enrolled for periods up to 3 years. Number of months * 30.42 returns a correct number of days for the Date_Add function, works nicely for this purpose, and allows using the same algorithm for all situations. The purpose of trying it as process rule was to not update a members expiration date until the transaction is confirmed and fees recorded as paid and the membership is activated.

rocketman

Then can you not put it in the BO rules - something like (I don't know your BO name

If OBJ.Status WAS CHANGED TO 'Confirmed' then enrollment.Endate = DATE_ADD( (Obj.StartDate,(Obj.Months*30.42))

Preceding rules could then test for the necessary requirement of the confirmed status and set it to confirmed

rocketman

oooops sorry, having re-read your post looks like you may have already tried that.