I can't shed any light on why it is running when it is not supposed. Just to hazzard a guess, it might have to do with an null value vs. and empty string.

My suggestion would be to add an if statement to your script and if the price level is nothing or empty, then exit the script, otherwise continue processing the script. (In case you didn't know it already, the variable `value` is assigned the colum value in column post-validate scripts.)

Example:

If value = "" Then

   Exit Sub

End If

' handle price code here

Interesting issue. It is triggering at the time when the Table Pre (or Post) Validate event should trigger and is in conjunction with other (than the Price Level) fields have been modified.

Dlech,

Thanks for the response. I would agree this could work, however there are cases where we would update the price level from a value, too nothing. For example, the current value could be "E" and the user may update it to "". In this case I would want it fire off my price code logic.

I would like to do something similiar, check to see if the value is edited with something like;

If PriceLevel.current <> PriceLevel.proposed Then

  'execute logic

End If

But I'm not sure on how this can be done in an UDS. Any thoughts?

Connex,

It does appear like this is happening. We have other scripts that run on column-post validate fields on the Sales Order Detail table that work just as intended, however these fields are never empty so we've never had this issue before.

In that case, I would suggest using oScript.SetStorageVar to hold the previous value. You will need to add a script the the table post-read event to get the initial value. Something like...

PriceLevel = ""

oBusObj.GetValue("PriceLevel$", PriceLevel)

oScript.SetStorageVar("PrevPriceLevel", PriceLevel)

Then to retreive that value in your existing script...

PrevPriceLevel = ""

oScript.GetStorageVar("PrevPriceLevel")

And at the end, add a line to update PrevPriceLevel...

oScript.SetStorageVar("PrevPriceLevel", value)

Thanks dlech! This sounds like a very reasonable solution. I'll give it a shot and let you know how it works out for me.

Worked great. Still no answer as to why this problem was occurring to begin with, but at least we have a reasonable work around. Thanks again for all of your help guys.

Isn't it running because pricing is always recalculated after certain events. Change a quantity, warehouse, price level,  all those affect pricing.