By using this website, you agree to our Terms of Use (click here)
I have these parameters defined in the GI:
In our current live system (2018.1) the defaults work as expected:
(our dates are dd/mm/yyyy for those Americans reading this)
In our 2019.1 sandbox, the GI displays as below:
Any ideas?
I tested using System Management -> Localization -> System Locals (SM200550)
Look how funny that makes my date look now!
It seems to be a MYOB related issue - not sure what they did wrong but somehow they managed to break these variables and also @Today.
Our Locale settings are correct.
@royce-lithgo
I have tested this also and have the same result in MYOB Advanced, exporting the GI and importing into a local Acumatica instance running on 2019 returns the correct data, ie Sept 1 - October 31.
Could you advise your business partner and they can log it with us and we will add it to our known issues list, I am sure we will get a few more of these queries.
I have raised this internally but the severity will increase as more repeated requests from affected clients are raised.
Thanks
Carl
@royce-lithgo
I have tested this also and have the same result in MYOB Advanced, exporting the GI and importing into a local Acumatica instance running on 2019 returns the correct data, ie Sept 1 - October 31.
Could you advise your business partner and they can log it with us and we will add it to our known issues list, I am sure we will get a few more of these queries.
I have raised this internally but the severity will increase as more repeated requests from affected clients are raised.
Thanks
Carl
Hi Carl,
It was logged last week and has been escalated to MYOB. The scary thing is we have 2 weeks to go before we are upgraded and no news as to whether this will be resolved before then.
our dates are dd/mm/yyyy for those Americans reading this
Royce,
I chuckled reading this part. Thanks for clarifying for us Americans. We really are pretty clueless about non-American dates. Although the way you Australians (and many others) do it makes a lot more sense.
I have found similar, but worse as it is not using the date advertised, in Acumatica 202R2 Build 20.207.0012. While the correct/expected dates show in the header/parameters, outputting those fields to the grid shows the next day. This is happening with all of the @____End values. Not shown here, but I have verified that the next day (incorrect) value is also being used in any filters utilizing the parameters.
GI Output
GI Parameters
GI Results Grid
P.S I used PX.SM.Users Where Usename = 'admin' to get my single row output for lack of better solution.