Fields that share same storage alias with an edge-encrypted field get a multiple-line input textbox even though the max-length in the dictionary is less then 255 - Known Error

Fields that share same storage alias with an edge-encrypted field get a multiple-line input textbox even though the max-length in the dictionary is less then 255 Description Fields that share same storage alias with an edge-encrypted field get a multiple-line input text box on the form even though the max-length value in the dictionary entry for those fields is less than 255.

Steps to Reproduce

Find a String type field that has a max-length value of more than 255 on task table and a storage alias that is shared by other columns. On the backend, the storage alias should be mapped to a varcher column.

Enable Edge Encryption on the field, which must be done through a proxy.

Note the max-lengh in the dictionary entry remains unchanged, but on the backend, the system converts the column from varchar to mediumtext.

On the form, the encrypted field itself still shows a single-line input box, probably because of the attribute Edge Encryption Enabled.

Check other fields that share the alias.

These fields appear as a multiple-line input box on the form. If a new field with a max-length value of more than 255 is created, it might also be mapped to the medium text field, which is incorrect.

If one of the affected fields is a reference field and the label of the field does not display, see KB0550677 .

Workaround Open the dictionary record of the field and add the attribute "is_multi_text= false" to the record.