Up until recently, I was working with Connect 2.8.4, and upon installing 3.2.196, got a new bug:
In Connect, an integer question receives the result of a calculation: concat('20', substr(${uniqueID},0,6))
Yields an integer value of 8 digits, example: 20190204.
Worked fine in 2.8.4
In 3.2.196, its putting a comma as to separate thousands, ending up reaching the 9 digit value (its counting the comma as a digit...) giving me: 20,190,20 - thus missing the last digit, 4. It writes it in red indicating bad value type
Just to make sure, I uninstalled 3.2.196, reinstalled 2.8.4 and all worked fine....
Ideas ?