Here is the script I use on purchase order header to write the date. It should give you clues.

retVal=oBusObj.GetValue("RequiredExpireDate$",sDate)
retVal = oSession.FormatDate(sDate, newDate, "%M/%D/%Y")
newDate = DateAdd("D", 25, newDate)
newDate = oSession.GetFormattedDate(CStr(newDate))
retVal = oBusObj.SetValue("UDF_HOUSTON_DATE$", newDate)

Hi BigLouie

I tried usig the above script, however since the Invoice Date is defaulted on the form load, it didnot pick up the value and returned for the new udf date field. Is there a way we can get the system date ?

Please advise and confirm. Thanks

AJ

Hi BigLouie

I tried usig the above script, however since the Invoice Date is defaulted on the form load, it didnot pick up the value and returned for the new udf date field. Is there a way we can get the system date ?

Please advise and confirm. Thanks

AJ

You can use either the SystemDate or ModuleDate properties of the oSession object. They will be in the required YYYYMMDD format.

Regarding the event firing, if you attach your script to the post read event and check the EditState property being 2, you can set the value on new records. If you don't need the value to be visible to the user while entering a new record, you could always attach the script to the pre write event.

For something like an invoice date for a new invoice, you might try one of these events instead of looking at the column... or try PreTotals (but I am not sure how that works for AP invoices).

I don't think script initialization will work for this purpose since I believe it only executes once when the task is first launched. Which is when the code is first read and added to the MSScriptControl object.

Set default values should work but it only executes when a new record is created and sage 100 processes the default values logic whereas post read or pre write gives you a little more flexibility.

yes, the Post-Read event on the header table captured it and worked exactly how we wanted. 

Thanks/AJ

Thanks Kevin M, I had the same doubt, but the Post-Read recommended by David, just did work exactly how we expected. Appreciate your response and guidance.

For completeness sake, if you are always going to use either the module date or system date for a Date UDF for new records, you can just set the default value to either when maintaining the UDF.

A script is useful when you want to calculate a new date value based on something else or need to have the date value changed due to another event occurring. Which i thought is what you were wanting to do since you were wanting this to trigger if someone changes the invoice date field.