Hi. We've noticed this week that the form fields are behaving differently than before. As we are using form fields to pass values into another field which passes those values to API into our ERP, it has caused the APIs to fail.

For example, one of the form fields, named ADR2 (Address Line 2), was usually passed as blank as only ADR1 (Address Line 1) is mostly populated. These fields in combination with other form fields are sent to a hidden field which builds a string for our API call to pass values in our ERP system. Previously, if ADR1 had values like Street 1 and ADR2 was left blank, it would send ADR1=Street 1&ADR2= and in our ERP the ADR1 field would be populated and ADR2 would be blank as expected. But now it is passing 0 if ADR2 is blank which is not accepted by our ERP causing the whole API to fail. Examples attached below

This is just one example and the business processes that we have are heavily dependent on values being passed from one field to hidden fields to build API strings. If they go through a workflow, it seems to be working fine but we have instances where we need to build the API strings in hidden fields depending on selections made on the form. Has there been changes made to the form field behavior?

Screenshot 1 = How the address fields are like

Screenshot 2 = How the API string looks depending on selections made