Re: Search on New fields on archived form
The reason for this is that ARS does some funny (strange) things with searches on field 1. Specifically I have never seen the full logic spelled out in the docs, but here is what I think it does if (User input length is less than length of field 1) then LPad the value with the prefix for field 1 I would guess that there is likely more logic involved, but that is at least the part that is important to this thread. So if the user enters 70 into the field 1 QBE then the system automatically searches for 070. (Assuming a 15 digit length for field 1.) It looks like this special tricks were not implemented on the field ID 70 fields in archive forms. It _think_ you can approximate this with Active Links on Search. ( But you may need to have a display only field (or 3) to get the logic just right too.) BTW: There are other *special* tricks that field 1 does too. (Like search on return in the field if the UT is configured to do that.) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap Pick two. On Tue, Mar 18, 2008 at 4:25 PM, Chintan Shah [EMAIL PROTECTED] wrote: ** Hi all, Once you archive the form, two new fields Original Create Date and Original Request ID are created. ...so far so good. Problem starts when end-users start searching on Original Request ID and get a no matching request back. That field is a Character Field. So, request ID 70 on Source Form is not same on Destination Form. I tried all QBE's. None of them work. It only works when you do a search on form like 'Original Request ID'=070. This is frustrating for end- users as they are not able to do search as they used to do previously. Any workarounds to make the new character field work like System field(DB ID:1)??? Thanks for your help in advance. Regards, Chintan Never miss a thing. Make Yahoo your homepage. __Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
Re: Search on New fields on archived form
Thanks Carey. I will try to do it using Active Link. Regards, Chintan. Carey Matthew Black [EMAIL PROTECTED] wrote: The reason for this is that ARS does some funny (strange) things with searches on field 1. Specifically I have never seen the full logic spelled out in the docs, but here is what I think it does if (User input length is less than length of field 1) then LPad the value with the prefix for field 1 I would guess that there is likely more logic involved, but that is at least the part that is important to this thread. So if the user enters 70 into the field 1 QBE then the system automatically searches for 070. (Assuming a 15 digit length for field 1.) It looks like this special tricks were not implemented on the field ID 70 fields in archive forms. It _think_ you can approximate this with Active Links on Search. ( But you may need to have a display only field (or 3) to get the logic just right too.) BTW: There are other *special* tricks that field 1 does too. (Like search on return in the field if the UT is configured to do that.) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap Pick two. On Tue, Mar 18, 2008 at 4:25 PM, Chintan Shah wrote: ** Hi all, Once you archive the form, two new fields Original Create Date and Original Request ID are created. ...so far so good. Problem starts when end-users start searching on Original Request ID and get a no matching request back. That field is a Character Field. So, request ID 70 on Source Form is not same on Destination Form. I tried all QBE's. None of them work. It only works when you do a search on form like 'Original Request ID'=070. This is frustrating for end- users as they are not able to do search as they used to do previously. Any workarounds to make the new character field work like System field(DB ID:1)??? Thanks for your help in advance. Regards, Chintan Never miss a thing. Make Yahoo your homepage. __Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are - Never miss a thing. Make Yahoo your homepage. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
Re: Search on New fields on archived form
So setting the QBE behavior to anywhere didn't work? -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Chintan Shah Sent: Tuesday, March 18, 2008 4:26 PM To: arslist@ARSLIST.ORG Subject: Search on New fields on archived form ** Hi all, Once you archive the form, two new fields Original Create Date and Original Request ID are created. ...so far so good. Problem starts when end-users start searching on Original Request ID and get a no matching request back. That field is a Character Field. So, request ID 70 on Source Form is not same on Destination Form. I tried all QBE's. None of them work. It only works when you do a search on form like 'Original Request ID'=070. This is frustrating for end- users as they are not able to do search as they used to do previously. Any workarounds to make the new character field work like System field(DB ID:1)??? Thanks for your help in advance. Regards, Chintan Never miss a thing. Make Yahoo your homepage. http://us.rd.yahoo.com/evt=51438/*http://www.yahoo.com/r/hs __Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
Re: Search on New fields on archived form
No, it did not. What anywhere did is as soon as i searched for record 70, it gave me 7070, 1070, 2070, 3070 and various other records. thanks Chintan Kaiser Norm E CIV USAF 96 CS/SCCE [EMAIL PROTECTED] wrote: So setting the QBE behavior to anywhere didn't work? -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Chintan Shah Sent: Tuesday, March 18, 2008 4:26 PM To: arslist@ARSLIST.ORG Subject: Search on New fields on archived form ** Hi all, Once you archive the form, two new fields Original Create Date and Original Request ID are created. ...so far so good. Problem starts when end-users start searching on Original Request ID and get a no matching request back. That field is a Character Field. So, request ID 70 on Source Form is not same on Destination Form. I tried all QBE's. None of them work. It only works when you do a search on form like 'Original Request ID'=070. This is frustrating for end- users as they are not able to do search as they used to do previously. Any workarounds to make the new character field work like System field(DB ID:1)??? Thanks for your help in advance. Regards, Chintan Never miss a thing. Make Yahoo your homepage. __Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are - Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
