I'm using LF cloud and experiencing weird behavior all of a sudden. The process is being used for over a year and nothing changed however the behavior of how form fields are storing numeric data has. For example, ZIP Code when entered on the form has leading zero example "0750" but when the field is being referenced in another form field it removes the zero. Under variables tab it is being recorded with the leading zero so not sure why it removes the zero when referenced in another field. Screenshots attached for reference
For context I am using a hidden field to build an API string based on the selections made on the form. This has been like this for almost a year now and was behaving as expected. Before, the leading zero would not get trimmed but now it is. Because of this incorrect data is being transferred through APIs and would be hard to reconfigure all the fields. Has there been any updates on how the form fields are behaving now?
Screenshot 1: How postcode is entered and displayed on the form field where the user enters data
Screenshot 2: How the data is displayed as a variable
Screenshot 3: How it is displayed when being referenced in another field to build the API string (Leading 0 removed)
The calculation formula to build the API string in the above field is as follows (Highlighted section is post code):
IF([Address_Type] = "Choice 1",
CONCATENATE(
"SUNO=", [SUNO],
"&ADTE=" &[ADTE],
"&ADID=" &[ADID],
"&STDT=" &[STDT_2],
IF([Update_] = "Yes", "&SUNM=" & [SUNM2], ""),
"&ADR1=" &[STADR1],
IF([Address_Line_2_1] <> "", "&ADR2=" &[STADR2], ""),
"&TOWN=" &[TOWN],
"&ECAR=" &[M3_State],
"&PONO=" &[Postal_Zip_Code],
"&CSCD=" &[M3_Country]
),
I really hope this is a temporary bug because there are many numeric fields in the form which can have leading zeros and are being referenced in the field which builds the API string and would hate to reconfigure all of them again