Quote:
Originally posted by kinook
Did you also add these attributes to the Item Attributes pane for your custom template item (the item in which you assigned the Form attribute for your custom form)?
|
Oh, OK, this does reslove the issue, but it brings up the question of why I should need to.
This behavior is only affecting text strings that begin with zero(s), no other beginning character is stripped and any Atrribute that is not envisioned to have a leading zero(s) does not need to be added to the Item's Template Attribute Pane.
Update
Never sure whether to bump or update...
It would appear that when UR reads inital data from a Form's field, it writes the data under the conditions noted in the second post by quant. Under these conditions a text String value that contains leading zeros is seen as a Number, and the leading zeros are stripped.
Re-entry of the data forces UR to read the data based on the Attribute Type setting (String (text)), thereby accepting the leading zeros.
The work-around suggested by Kinook:
goto the Template that contains the Form with the Attributes that will contain leading zeros (US Zipcode, Int'l dialing, part numbers...), expose the Attribute Pane (Ctrl-4), Insert (add) the Attributes that will contain leading zeros, close the Attribute Pane.
It would appear that this forces UR to read the initial data (from the Form) based on the Attribute Type setting (String (text)).