Dates in Sage 100 are string data types (YYYYMMDD), not numeric, with a date format command but I don't have it handy...

Hi Kevin!  Thank you for your reply.  Does this also apply to UDFs?  I have several that I'm setting in this script (aside from this one) that take the format of YYYY-MM-DD and populate their respective fields with no issues.

I will give this change a try and let you know what comes of it

Thank you again!

I changed the format of the date in the front end (Angular) to YYYYMMDD but no luck there.  I tried setting the script to the format of `DateTime.Parse(PhasePayLines[1])).ToString("yyyyMMdd");` but that didn't work either.

I commented out all of the other code in my script and only left the "UDF_PAY_DATE" field parts and I get an error back "The column is not in the IOList" although I clearly see the field in the data base.

I'm at a loss lol

Are you on Premium/SQL version? Even if not, the solution is most likely to go into Sage itself, change into the same Company that you did nSetComany for, click into Custom Office / Main / User Defined Field & Table Maint / select SO Sales Order Detail, Edit Fields, and on that dialog click Update. However, this pretty much requires all users be out of Sage so you may have to do it in off hours.

I was finally able to get it to populate the field with the code below:

Not sure why I had to do it this way but glad it was solved - thank you for all of the feedback!

Thank you Alnoor!  I was going to try this solution tonight but was able to get the field to populate with the code in my response below :)

Hi js-goose, thanks for sharing what worked! Please do mark this as verified if it worked for you

In the first code snippet, it appears that you are missing the $ on the variable name (UDF_PAY_DATE), whereas the one you recently posted included it (UDF_PAY_DATE$).

I tried both ways with the first code snippet and was surprised when my solution worked because the field is set to `datetime` format in the DB but it looks like it's accepting a string

Yeah, that's just how the Sage API works.  There's really only two variant types (string and numeric) in the ProvideX language, so DateTime Columns are treated as strings in the yyyyMMdd format.

Glad it's working for you.