Andrew, This is actually easier than you think, see below. The key is to reverse your thinking about how a "LIKE" operator could be used. Read through the entire setup before focusing too hard on the qualifications. Also, you may want to add other clauses to your qualfications, such as a check on a status field. Real life example: : ( 'Status' = "Enabled") AND ( $RequestedList$ LIKE (( "%;" + 'Request ID') + ";%" ))
FIELDS: Button: Add Button: Remove ----- Temp char field: tmp_SelectedList ----- Table A - list of options Column: col_A_ID Qualification: NOT(tmp_SelectedList LIKE "%;" + col_A_SelectedID + ";%") ----- Table B - list of selected options Column: col_B_ID Qualification: tmp_SelectedList LIKE "%;" + col_B_SelectedID + ";%" WORKFLOW Active link: Add Fire on Click of Add button or double click on Table A: Action 1: set tmp_SelectedList = tmp_SelectedList + ";" + col_A_ID + ";" (note: this adds the selected record to the list, including delimiters) Action 2: Call TableRefreshGuide ----- Active link: Remove Fire on Click of Remove button or double click on Table B: Action 1: set tmp_SelectedList = REPLACE(tmp_SelectedList,col_B_Selected_ID,"") (note: this removes the selected record from the list) ----- ActiveLink Guide: RefreshTableGuide ActiveLink (put in guide): RefreshTable Action 1: set tmp_SelectedList = REPLACE(tmp_SelectedList,";;",";") (note: this gets rid of double semi-colons) Action 2: Refresh Table A Action 3: Refresh table B Action x: anything else you want done on a table refresh, perhaps updating count indicators. ----- Hopefully that helps, Thad Esser Remedy Developer On Tue, Sep 20, 2011 at 1:54 PM, Andrew C Goodall <ago...@jcpenney.com>wrote: > ** > > I’m not sure how to put a succinct title on this…I’ll try to explain**** > > ** ** > > I want 2 tables on a display form with “add” and “remove” buttons where I > can:**** > > ** ** > > 1. Add item 1 from Table A to Table B, but then also remove from Table > A so it does not show up as an available selection again – since user just > added it. **** > 2. Remove item 1 from Table B and add back to Table A.**** > > ** ** > > At the end of the Add / Remove process then I will process that data in > Table B.**** > > ** ** > > I can get 90% for what I’m looking for using real forms associated with the > tables, however in this design the issue I have is that all the original > available selections are always listed– I do not really want to delete the > record from Table A only hide it from selection view again.**** > > ** ** > > So far it looks like I can only associate a table to a form and I’m not > able to add custom columns to the table outside of that form.**** > > ** ** > > **** > > This is so easy to do in .Net with temp datasets L **** > > Currently, I’m thinking the only way I can do this is if I append to an > External qualification for Table A - where not like items in table B.**** > > ** ** > > ** ** > > Regards,**** > > **** > > *Andrew Goodall***** > > Software Engineer 2 | Development Services | jcpenney . www.jcp.com > <http://www.jcp.com/> > **** > > ** ** > > > The information transmitted is intended only for the person or entity to > which it is addressed and > may contain confidential and/or privileged material. If the reader of this > message is not the intended > recipient, you are hereby notified that your access is unauthorized, and > any review, dissemination, > distribution or copying of this message including any attachments is > strictly prohibited. If you are not > the intended recipient, please contact the sender and delete the material > from any computer. > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
