Well, one possibility might be to use a table that displays the character values that you care about and then a filter guide to loop over the table that calls a filter that contains a set of push fields actions (one for each value of the selection field) that pushes the currently selected character value and the selection field values to the form in question. For example, if you have the following table that lists the values read from the DB:
C Val Y Z And your selection field has two values, you would have a filter guide to loop over the table that calls a filter with two push fields actions: Push $C Val$, Selection_Value_1 to My_Form Push $C Val$, Selection_Value_2 to My_Form Does that make sense? You would just need a way to trigger the filter guide when you want to populate the other form. The key to that working correctly, though, is that the character values in the table need to be unique (no duplicates). Lyle From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Rick Cook Sent: Thursday, April 16, 2009 10:08 AM To: [email protected] Subject: Re: Form population conundrum ** Basically, you have it right. The drop-down field contains known values. The character field is only populated by reading the metatable for the server in question. I need to read the DB for all of the values in the character field, then create (I don't really care how) the complete list of combinations. I then have workflow that can validate the combinations. Rick On Thu, Apr 16, 2009 at 9:03 AM, Lyle Taylor <[email protected]<mailto:[email protected]>> wrote: ** Let me see if I'm understanding you correctly, you want to create a list of all the possible values (entries) that could be in that form? For example, if you had fields A and B, and A can have the values "Y" and "Z", and B can have the values 1 and 2, you'd have the possible combinations: "Y", 1 "Y", 2 "Z", 1 "Z", 2 Is that what you're trying to get? If so, do you need workflow to generate it (i.e., does the system need to generate it automatically), or are you just trying to find a way to generate the list so that you have an initial set of data, perhaps that could even be imported? Lyle From: Action Request System discussion list(ARSList) [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Rick Cook Sent: Thursday, April 16, 2009 9:57 AM To: [email protected]<mailto:[email protected]> Subject: Form population conundrum ** I am trying to come up with the best way of doing the following: I have a form with two fields: one character field and the other drop-down. Each has a maximum of about 8 unique records. What I want to do is create a cross reference file in that form of all possible combinations of those data values, and I want to populate it automatically from scratch. The trigger isn't all that important - I have some flexibility there. I cannot seed the data in the character field - it is read from the DB via a SQL call to a metatable, and each installation may have different data. I have thought about building a series of guides to read the data and create the data, or doing it directly in SQL. I have the SQL call to read the data for the character field already working in a menu that's attached to that field. The problem is that I can't figure out how to use the SQL to create new records via workflow, unless I also use a direct SQL call to write the data to the form. That's sounding like it might be a farily complex stored procedure that I have no experience in constructing. Anyone done something like this before? I thought it was going to be much easier than its looking like now, and I think I'm getting into analysis paralysis mode. Rick _Platinum Sponsor: [email protected]<mailto:[email protected]> ARSlist: "Where the Answers Are"_ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. _Platinum Sponsor: [email protected]<mailto:[email protected]> ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
