Customizable User Defined Fields

unknown

In 6.5.2 we introduced the CUDF fields. In 6.5.3 we are attempting to put the values that you add through the Customizable User Defined Fields into the Browses so that it appears as part of the original system.

A current issue that we are attempting to resolves is the use of the Boolean fields. Currently they are stored in the database as 1 for true and zero for false. So when we display the data in a browse that is exactly what you would see 1 or 0. To computer geeks that is pretty self evident, however to an end user that can be confusing.

Question for the group is should we store in the database (which would require a conversion of the data) the values Y for yes and N for no similar to the other check box fields in Visual (PART.FABRICATED for example).

Has anyone used a CUDF Boolean value in a report and that report will be broken by changing the schema?

unknown

Probably too late for this. But...

My vote: yes convert the data.
Not because I like the Y/N concept. But because it would consistent.

And No CUDF's in reports.