1 of 1 people found this helpful
Define a calculation field in that table with a Text result type:
List ( Ud_1 ; Ud_2 ; Ud_3 ; "SameValue1" ; "SameValue2" ; "SameValue3" )
Make this calculation field the source of values for your value list.
I've been known to combine "action" values and data values in the same list this way such as:
List ( " All" ; "-" ; Field )
This puts " All" at the top of a value list with a divider line followed by all the values in Field pulled from the specified table. I use this in some cases for filtered portals or scripted finds where selecting " All" is checked for in a script and turned into a scripted process that finds all records or makes all records appear in a filtered portal. Note the leading space used to sort " All" to the top of the list.
Oh this is perfect. Do I create the calculation field in the User table or the related table in which I am adding the drop-down list field (with this new value list)? I am guessing the User table, but just wanted to check. Thank you!
Notice the lack of table occurrence names in my example. You want it in the same table as your three fields as this must be an indexed field.
Okay, ran into a hiccup. The Ud_1, Ud_2, Ud_3 fields refer to Serial_ID numbers for specific contacts (each users selects the 3 specific contacts so is different between users). I have a related table that is Contacts and has the Serial_ID and FullName. Is there a way to make it display the FullName in the list rather than the Serial_ID number? When the User selects the Contact I am using a popup menu to hide the Serial ID and just show the FullName already, but then it translates to the Serial_ID in the Value List.
Could I create 3 additional calculation fields and have each one calculate the name pulled from the related Contacts table based on the serial_id in the Ud_1, Ud_2, Ud_3 field, and then use that in my list? Or is there an easier way?
AND, if that was my route, how do I actually define a calculation field to pull from a table field based on another field in that record?
Not as calculation fields, they would not be indexed. An auto-enter or looked up value field option could copy over the value...
Figured it out. Scripted it into a button so that that button now enters the Serial_Id into the a User table field, and also enters the name into a different User table field. :-)
Crap. I ran into a glitch.
The Contacts table I have related through the Globals table and then a many-to-many relationship from that table to the Contacts.
The Value List is now showing ALL Ud_1, Ud_2, Ud_3 selections by EVERY User in the drop-down.
Should I make a separate TO of the Contacts table and associate it with the User table directly? If so, what relationship should I set up?
Nope. I just figured out an issue I'm not sure I can get over easily. The related table layout for some reason does not keep the User session info. I'm going to need to place the needed items in a $$var. Can I do that and integrate them into the calculation script? Is that possible?
Sorry but you've lost me. I don't have a clear picture of the tables and relationships.
I confused myself on this one. No worries, your initial answer was key!
Yes, but I'd give real consideration to moving those three fields into a related table where you'd have three records instead of three separate fields--might make managing the relationships easier since each appear to match to a record in another table by ID.