Sage 100

It appears in v2018 Job Cost, Job Posting Entry, that the Transaction Date defaults to the current system date, not the module date. OK, how about a script to fix this? I am not a serious scripter, but I cannot get this to work. Can anyone see the problem with: mDate = """" sMDY = ""%M/%D/%Y"" retVal = oSession.FormatDate(oSession.ModuleDate, mDate, sMDY) MASDate = oSession.GetFormattedDate(CStr(mDate)) retVal = oBusObj.SetValue(""TransactionDate$"", MASDate) The last line is the issue.

Is this something they are going to fix or are they saying WAD?

Declare MASDate as string in advance?

Try getting the errorMsg: retStrVal = oSession.AsObject(oSession.UI).MessageBox(oSession.LastErrorMsg)

Lee - Thanks for the tip. The error is: ""2/14/2018"" is not numeric. Even though a msgBox on MASDate is 20180214. ?

Jon - No need to convert to VB date then back to MAS date (as you don't need to add or subtract dates). Try this: retVal = oBusObj.SetValue(""TransactionDate$"", oSession.ModuleDate) I presume the script is firing off Table Post-Read or SetDefaultValues event

Thanks Alnoor. However, still no luck. I have discussed the underlying issue with Sage and they agree that it is a bug. (Yeah!). As such, they are going to help with developing a script to fix it. Will keep you posted.

I thought it might not work. Glad you reported it. I'll look into it too.

Slightly off topic here but where do these bogus ""xxxx is not numeric"" errors come from about fields that clearly are NOT numeric? I have done several BOI programs lately and it makes trying to separate real errors from gibberish rather difficult.

From Sage (today 02/28/18): In regards to the other reported issue regarding the TransDate, we were unable to get a script to work. The program fix is currently being tested and we do not expect a hotfix before next week.

Jon I'm trying to duplicate it but not doing something right. On my PU1 system, in EEC, I set J/C Module Date to 2/23/18 (to be different than today's System Date of 2/28/18). Then go into Job Posting Entry (with batch entry enabled), on top left it shows 2/23/2018. When I get to Job Posting Register, Posting Date appears as 2/23/2018 as well. Previewing Register shows same.

I am referring to the Trans Date field in Job Posting Entry.

Refer to Knowledgebase article 89332. Defect ID 108901.

Thanks. This script here works for me. It's set to JC Job Posting Detail > Column PostValidate on JobNo If oScript.UIObj > 0 Then Set oUIObj = oSession.AsObject(oScript.UIObj) retVal = oUIObj.InvokeChange(""TransactionDate"", oSession.ModuleDate, ""GD_LINES"") End If Note this won't work for V/I imports to Posting Entry so you will need the fix for at least that.

Thank you Alnoor. It works! Would you mind telling me how this accomplishes this, and why my previous retVal = oBusObj.SetValue(""TransactionDate$"", oSession.ModuleDate) failed?

You know what your script looks like it will work if you just do this: retVal = oBusObj.SetValue(""DetailTransactionDate$"", oSession.ModuleDate) Sorry I didn't spot that before. Better to do it this way because it will support V/I imports too. Yours was failing because TransactionDate is not the actual field name in JC_JobPostingDetail so a SetValue on oBusObj results in ""column is not in the IOList"" if you were to get the oBusObj.LastErrorMsg. The InvokeChange means I can set a value into a control on the screen with its control name which happens to be ""TransactionDate"". InvokeChange means I'm using the UI object instead of the business object which means among other things any subsequent business logic or validation doesn't get fired off.

Thanks again, Alnoor. Where could I have found this information? The File Layouts that come with 2018 still show the legacy file names and this field is Transaction Date. . . . . . . . . . . . TransactionDate . . . . . . . Date *(29,6)

On my 2018 PU1, I'm seeing the Framework version of the J/C File Layouts. I'm using the Standard Desktop launcher. On the Web Content tab, I choose Resources. Then on the HTML frame in the Launcher off to the right, scrolled down to find File Layouts. This launched the online File Layouts for me in a browser.

Thanks 3x. I found it. Somehow I must have still had an old link to the local. I won't bother you anymore, but may see you tomorrow.....