AnsweredAssumed Answered

Conditional value lists - ID# field displaying for users on different platform

Question asked by GregW_1 on Apr 11, 2011
Latest reply on Apr 12, 2011 by GregW_1

Title

Conditional value lists - ID# field displaying for users on different platform

Post

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

Outcomes