0 Replies Latest reply on Apr 13, 2011 9:20 AM by GregW_1

    Bugs with conditional value lists on Filemaker Go

    GregW_1

      Summary

      Bugs with conditional value lists on Filemaker Go

      Product

      FileMaker Go

      Description of the issue

      1.  Create a conditional value list with the option that only the second field is displayed.  After an option is selected on a conditional value list by a Filemaker Go client, a user viewing the same record from Filemaker Pro client only sees the value of the first field, while the Filemaker Go client that selected the value sees the second field.  Conversely, if a Filemaker Pro client selects the value, the Filemaker Go client only sees the value of the first field.

      2.  In Filemaker Go, conditional value lists in portals are inserting no value or incorrect values after selecting an option

      Steps to reproduce the problem

      1.  We have an app shared through FM Server that is accessed by clients using FM Pro and clients using FM Go for iPad.  There are two value lists populated by records in two respective tables - Area and Item (fk to Area pk).
      The Area value list has the following options:
      -Use values from first field, "pkArea"
      -Also display values from second field, "areaName"
      -Include all values
      -Show values only from second field

      The Item value list has the following options:
      -Use values from first field, "pkItem"
      -Also display values from second field "itemName"
      -Include only related values starting from Area table
      -Show values only from second field

      A layout in the app contains a portal with two pop-up lists.  The user selects the Area list and the values of "Area::areaName" are displayed in alphabetic order, selects an option, and the second Item list displays values of "Item::itemName" in alphabetic order.  The conditional value lists work as they should.  The problem is with how the value is displayed in the Item list in this layout, here are the symptoms I have noticed:
      -FM Go for iPad user enters new record in the portal, selecting an Area value in the first pop-up list and an Item value in the second.  After exiting the new record, it correctly displays the "second field" values for Area and Item.  However, when viewing the exact same layout using FM Pro for Mac, the conditional value list, Item, is displaying the first field (pkItem), instead of the second field itemName as it should.
      -Opposite symptoms occur if the new record is created from an FM Pro client.  The FM Pro client sees the value of the second field in both lists, but the FM Go iPad client sees the value of pkItem in the Item list, instead of itemName


      2.  Create the first related record using the portal,
      -Select an option from the first pop-up list.
      -Select the second, conditional pop-up list - the options displayed are correct based on the first condition
      -Select one of the options in the conditional list, and here is where the issue occurs - Sometimes the selection is momentarily highlighted after selecting, but doesn't get checked and the pop-up list remains up.  Sometimes the option gets checked, the pop-up list goes away, but the selected value is not inserted in the record.
      -Click outside of the portal to refresh/update the records, select the second conditional pop-up list again and select a value, then the correct value is inserted in the record.

      2A.  Create another related record in the same portal
      -Select an option from the first pop-up list that is different from that of the first record in the portal
      -Select the second, conditional pop-up list - the options displayed are correct based on the first condition
      -Select one of the options, and here we see another issue - The option gets checked, the pop-up list goes away, but the value that gets inserted is not the one that was clicked, the field fills in with a value from the conditional value list of the FIRST record, not the current record.
      -After testing further I noticed that the incorrect value correlates to the same number option in the value list.  E.g. The first related record, first value list, had option A selected, thus the second conditional value list had the related options, call them A1 through A15.  Now a subsequent related record had option B selected in the first value list, and selecting the conditional value list gives you the options say B1 through B12.  But when you select B10, the field fills in with the value of A10.