GL date format not correct when creating transactions in GL (7 replies)
Marios, I suspect this is due to the server's regional settings.
Please check the System regional settings on the server to see if they are US.
Thanks
Hi,
I thought abut the server date config and I had checked it. It is correct - EU format. Please see attached image.
I also created another date field called GLDate that is equal to %TradeDate. I left it unformatted. Although it shows correct on pressing Refresh in the last transform before the GL batch generation then it messes up. What I noticed, is that dates that are definitely dd/MM/yyyy are picked up correctly, that is, 26/04/2016. Dates that are ambiguous, like 4/5/2016 will be picked up as MM/dd/yyyy.
I tried also to Format(%TradeDate, "dd/MM/yyyy") . This displays the GLDate fine until the last transform before the GL generation. But Sage 300 transform then messes up.
This leads me to believe that the Sage 300 connector has intelligence to deduce the date format, with MM/dd/yyyy being the default.
So how do I tell the Sage 300 transform to always use dd/MM/yyyy?
Thanks
Marios
Hi Marios,
Are your IMan services running under a specific user?
Hi,
No, default permissions (see image).
Regards,
Marios
Marios, this is 100% a system issue.
Please check your System/Administrative Regional Settings.
Please note that any change of the System Locale requires a restart of the server.
Closed due to inactivity.
Hi,
I am importing from a CSV file and creating GL transactions for Sage 300. In the CSV there is a date field in the format of dd/MM/yyyy that is to be used as entry date in Sage 300. I can see that through the transforms, it propagates in the correct format but when it gets to the point of creating the transactions in GL some of the dates are swapped to MM/dd/yyyy.
How can I stop this from happening?
Thanks
Marios