Thanks Guys seems to be working perfectly now after last update 
Was this in the most recent update that went out or still to be released? Asking because I’m having a similar issue. Trying to set a dateTime variable via URL and it’s messed up my app that I can’t open it. Format I’m using and error shown below. Thanks!
…/trigger/setGlobalVariable=returnDateTime:2021-11-30T22:46:42.539-05:00?access_token=…
When I remove all colons, I get this in the logs (with the colons the unparseable date ends at the first colon:
java.text.ParseException: Unparseable date: "2021-11-30T224642.539-0500" on line 9133 (method mainPage)
It's the colon in the -05:00 that is the problem. That should be -0500.
I have tried a number of different ways. Just tried this and still getting the below error when trying open the app. Also tried removing all colons and that doesn’t work either.
…/trigger/setGlobalVariable=returnDateTime:2021-11-30T22:46:42.539-0500?access_token=
It looks like the data is pulling up to the first colon. With all colons removed, I get:
Error: Unparseable date: "2021-11-30T224642.539-0500"
I can confirm that the dateTime string is getting mangled in the handler, and that is the cause of the error. Working on a fix...
Fixed. This fix will be in an upcoming release.
2 Likes
Thank you
I updated to 2.3.0.115 last evening, and confirm I'm now able to set the global variable. I am seeing an issue with the actual time that is populated. I'm pushing value shown, but the variable displays 3 minutes ahead as shown below... but as you can see when I manually open the dateTime, it shows the value that I posted. Maybe just a display issue?
EDIT: I did some more testing, and it looks like the values after the seconds decimal are somehow being pulled into the display of the minute. It seems a bit random what value is being used, but if I leave the decimal values at ".000" the correct minute value displays. Ok for me because I don't need such precision for what I'm doing.
...setGlobalVariable=testGlobalDateTime:2021-12-04T22:22:22.222-0500?access_token...
