Daniel Shanahan Posted June 7, 2007 Posted June 7, 2007 (edited) I have three date fields where a client can choose three dates for a tour. The fields are 1st choice, 2nd choice, and 3rd choice. I want a fourth field to have the date that the client actually gets. I tried using the List function, but I cannot choose or select one of the dates. I want a drop down list, but can't figure out how to use a value list in this instance. Any suggestions? Thanks. daniel Edited June 7, 2007 by Guest
comment Posted June 7, 2007 Posted June 7, 2007 (edited) You can do this, but it's going to take quite a few resources. First, the three dates have to be in the same field, as a return-separated list. So you need a calculation field (result is Text) = List ( Choice1 ; Choice2 ; Choice3 ) This calculation would not be required if the choices were made in a repeating date field with three repetitions (or in three related records in another table*). Next, you need a self-join one-on-one relationship with the same record, so put another occurrence of the table on the graph and define a relationship to it by matching on SerialID field. Now you can define a value list using values from the calculation field (or the repeating field) of the new TO, showing only related values. Instead of all this, you could make the user enter the three choices into a repeating date field, then put three buttons next to it to select the repetition. --- (*) If these dates need to be used for finding or sorting, this would be the correct approach to take. Edited June 7, 2007 by Guest
Daniel Shanahan Posted June 7, 2007 Author Posted June 7, 2007 Thanks Comment. I chose the repeating field option and it works very well. I created three different scripts using the shorthand version of the GetRepetition Function: Set Field [individual::Tour Date; Individual::Tour Date Request [1]]. I think if I name the buttons I can have just one script with a conditional clause. Is that correct?
comment Posted June 7, 2007 Posted June 7, 2007 You CAN have one script, without naming the buttons or adding conditions: Set Field [individual::Tour Date; Individual::Tour Date Request [Get (ScriptParameter)]] Now just define the script parameters for each button as 1, 2 and 3. And you should probably add a Commit Record[] step at the end of your script.
Recommended Posts
This topic is 6379 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now