Scripting

Is there any BOI bug anyone knows of (Sage 100 Premium 2014, possibly introduced with SP6) with the order date field on sales orders entered through BOI? I have a VB dotnet app bringing in web store orders and all the orders since 7/30 have been coming into Sage with a 7/30 order date, even though the source has the correct date. I cannot replicate the issue on my test system. Code snippet: If IsDate(dr.GetValue(dr.GetOrdinal(""date_purchased""))) Then dtVal = CDate(dr.GetValue(dr.GetOrdinal(""date_purchased""))) Else dtVal = Today End If oSOOrder.nSetValue(""OrderDate"", dtVal) Any ideas?

Phil, are you doing this before or after you set the customer number? It should be after.

It is after the customer number is set

Are you collecting the return value on that SetValue method? Maybe it's not actually writing it at all (user login permissions?), although I don't know why 7/30 would default in either way.

And are we sure that dtVal is not finding a date_purchased of 7/30 each time (maybe the issue is coming upstream)?

I checked the source data and it is correct. I will start logging the retVal on the SetValue command.