Thanks Ben and Lyle. I tried what you suggested Lyle and I think that will work for us.
Thank you, James On Apr 6, 12:09 pm, Lyle Taylor <[email protected]> wrote: > You could easily do this using a join form between PBM:Known Error and > PBM:Known Error Associations. Create the form as an outer join with the > associations form on the right. You join criteria will be $Known Error ID$ = > 'Request ID02' AND 'Request Type01' = "Infrastructure Change". Add the Known > Error ID field and Request ID02 fields to the form. > When you do a search, it will show a record for each Known Error record. If > there is a match in the associations table, it will also bring that > information in as well. If there is no match, then any fields from the > associations table that you put on the join form (Request ID02 in this case) > will be NULL. So to find all Known Errors that don't have a corresponding > change, just search for all the records in the join form where one of the > association fields (Request ID02) is $NULL$. That will show all Known Errors > that don't have a corresponding relationship record to a Change. > Lyle > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Benedetto Cantatore > Sent: Tuesday, April 06, 2010 7:48 AM > To: [email protected] > Subject: Re: Find Known Errors that are NOT related to a Change > > ** > Here's a quick stab at how I'd do it. > > I'm not sure if you're trying to show this info in a report or in a form, but > basically you want to compare records in PBM:Known Error against PBM:Known > error Associations. Then search against Request ID02 where it does not match > Known Error ID and Request Type equals Infrastructure Change. > > Ben Cantatore > Remedy Manager > (914) 457-6209 > > Emerging Health IT > 3 Odell Plaza > Yonkers, New York 10701 > > >>> [email protected] 04/06/10 3:08 AM >>> > > I am trying to figure out how to find Known Errors that are not > associated to a Change request. We are using Known Errors to track > bugs and enhancements to in-house software. We associate corrected > KEs to change requests as a Release. I am trying to find KEs that are > not associated to a change (release) to make sure that they are > addressed and don't fall through the cracks. > I can easily find which ones are associated to a change by looking at > the Associations forms, but I am stumped on how to find ones that are > NOT associated. > We are on ARS 7.1 and ITSM 7.03. > > Thanks, > James > > ___________________________________________________________________________ > ____ > UNSUBSCRIBE or access ARSlist Archives > atwww.arslist.org<http://www.arslist.org> > attend wwrug10www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers > Are" > _attend WWRUG10www.wwrug.comARSlist: "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. > > ___________________________________________________________________________ > ____ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > attend wwrug10www.wwrug.comARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
