1 Reply Latest reply on Aug 15, 2013 11:00 AM by philmodjunk

    Field not translating correctly into new layout

    AdamSchleifer

      Summary

      Field not translating correctly into new layout

      Product

      FileMaker Pro

      Version

      12

      Description of the issue

      We created a new layout that incorporated some core fields defined for the initial layout. Three out of four fields translated the data correctly, but the last one (called "Themes") did not as in certain cases; some piece of data was missing, or it was mixed up with a different field (which was not listed within the new layout), or it added irrelevant info e.g. X. The layout we are using is the List Layout.

      Steps to reproduce the problem

      We tried to duplicate the initial layout and subsequently delete the field we did not need, and yet again the translation of the "Themes" field was not correct.

      Expected result

      The initial layout presents the "Themes" field into a checkbox set, and what we'd expect to see is this field as in a list for the second layout. Furthermore, this second layout should show only the checked themes in the initial layout.

      Actual result

      Some fields within the second layout are correct, some others (most of them) are not because the data is wrongly translated.

      Exact text of any error message(s) that appear

      No error messages appear.

      Configuration information

      If we keep the checkbox list within the second layout, "Themes" translate correctly. As soon as we use the list, data gets mixed up.

      Workaround

      Truly need serious help!

        • 1. Re: Field not translating correctly into new layout
          philmodjunk

               Here are two possible causes for what you are observing:

               1)

               If you format a field to give it two or more check box values, FileMaker will store each value you select as text, separated from other selected values by a return character. The order of the listed values is determined by the order in which the checkboxes were clicked. If you click the last check box and then the first check box value, the last check box value will be listed first if you examine a copy of the field formatted as an edit box.

               In an edit box formatted copy, each such value will be on a different line of text in the field. Thus, an edit box formatted copy of the field may not show all selected values if it is not tall enough to show all rows of text. You may have to click/tab into the field to see all the values entered into it.

               2)

               When you format a field with check boxes, any data present in the field that does not match one of the current values in the value list specified for it will not show in the field when formatted with checkboxes, but will show if you format it as an edit box. Thus, if your field used a value list of two values: apple; orange, you might have "lemon" entered in the field and it won't show in the check box formatted copy of the field.

               Also, if you edit the value list to change the values listed, this does not have any effect on what data is already stored in the field. As just described in the previous paragraph, any such data that no longer matches one of the values in the value list is now invisible in the check box formatted copy of the field, but will still be visible in the edit box formatted copy.