That's why Remedy has switched from using the Entry ID to using the Instance ID (i.e. GUID). You can create an Instance ID whenever you want, using a Run process call, and if you don't create it, it's created for you when a record with the proper field in it (ID 179) is created.
Rick -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Thornley Sent: Wednesday, February 28, 2007 10:59 AM To: [email protected] Subject: Re: Entry ID on Submit So I think it's time for me to take a new approach and solicit suggestions on how others would accomplish this goal. So here goes: I have a schema that is setup as a parent/child based on the status field. On this schema is a count field used for counting all the children. I also have a fields for the parent entry id, child id and another field used for sub-status. So the intent is to have the parent count all the children that apply whenever the sub-status equals a certain value. The approach I been taking is whenever the child meets the sub-status criteria I fire a filter that pushes the entry id to the parent records child id field then another filter that fires whenever this child id changes on the parent that does a count on the child records with the same parent id & sub-status. So this all seems to work great whenever the child record gets modified that meets the conditions. The problem is when a child record gets submitted that meets the condition. The entry id does not yet exist so the filter that pushes the child's entry id the parents child id field is null so all the subsequent actions fail. Ideas ? Thanks Kevin -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black Sent: Wednesday, February 28, 2007 3:45 AM To: [email protected] Subject: Re: Entry ID on Submit Kevin, Another approach is to do a push to the current record and include a "signal" that allows the modify filters to "branch" and call a filter guide and not do the full Modify processing. You add a display only field that you set to a value like "FinishSubmitLogic". Then a Modify Filter that checks that filed for that value and calls a guide then does a GOTO 1000 to skip the rest of the modify filters. The only other thing you need is to add a filter on submit that does a push to the current form where '1'=$1$ AND make sure that filter IS phased. (That way you know the Request ID value and their is a record on the DB to "push" to.) However, sometimes these things are actually better dealt with via other processes. Can you be specific about what your doing and why you think you need the 'Entry ID' value during Submit Filters? -- 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 2/27/07, Axton <[EMAIL PROTECTED]> wrote: > Nope, generate a unique value using a guid/instance id. See the > special run process commands section of the basic/workflow guide. > > Axton Grams > > On 2/27/07, Kevin Thornley <[EMAIL PROTECTED]> wrote: > > ** > > > > > > > > All > > > > I need to use the entry id on some filters that execute on submit. > > The problem is that the entry id isn't committed yet. I want to > > remember that there is a way to make this happen by using the "'!" > > naming convention to control the firing order. > > > > Help > > Kevin ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
