Re: Creating subfile records from list on submit SOLVED
Field 179 did it! Thanks, Brian, and everyone else who responded. I didn’t know about that feature so for the benefit of anyone equally ignorant, I’ll copy what the manual says: “To auto-populate a field with a GUID, define a character field using field ID 179. A GUID is available through all filter phases. By contrast, the value of Request ID field is not available until an entry has been successfully committed to the database. You can set the attributes of the GUID field, except for field type, length, and ID.” I created a field called “F179” with an ID of 179. I have filters that end with `!, and during phase 1 they do “Push Fields” to create subfile records with a Parent ID equal to F179. Then at the very end a filter does a “Push Fields” to all subfile records where Parent ID = F179. This filter does not end with `!, so the Push Field runs in phase 2 when the Entry ID has been set, so it updates all the subfile “Parent ID” fields to the real Parent ID. One interesting feature of F179, if you look at the field you don't see any value, but if you follow the filter log you see a long string of gibberish getting pushed to other fields. Thanks again, everyone! Dwayne Original message Date: Thu, 16 Oct 2008 12:18:43 -0700 From: Brien Dieterle [EMAIL PROTECTED] Subject: Re: Creating subfile records from list on submit To: arslist@ARSLIST.ORG ** Right, I think Joe and I are trying to suggest using an ActiveLink and not a filter :-) Brien On Thu, Oct 16, 2008 at 11:34 AM, Grooms, Frederick W [EMAIL PROTECTED] wrote: A Filter does not use the @@: syntax (Evidenced by the v7.1.0 filter AR System Email GUID Generator) I pulled the 38 length from Field 179 on the stock ARS form AR System Email Association Dwayne, Out of curosity, try changing the field to 38 characters long (maybe the command does not like fields 255 characters long. Fred -Original Message- From: Action Request System discussion list(ARSList) __Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are html___
Re: Creating subfile records from list on submit SOLVED
Guys, Field 179 is just that. A guid that is autopopulated on creation (at least on submit, not sure about merge). All ARS guid fields are 38 bytes long. Any field (not just 179) can be set with the process Application-Generate-Guid xx. That field should be 38 chars long. With field 179, the process does not need to be called and the field will be auto-populated. A lot of times an InstanceId (as the BMC OOTB Apps like to call thier 179 fields) will be set with a set fields @@ process in an Active link so that dependent records may be built before the paent record exists (therby NOT being able to link to field 1). Of course, if the parent is not saved, you must include workflow to delete the saved child records. Cheers Nem -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Dwayne Martin Sent: October 16, 2008 10:43 PM To: arslist@ARSLIST.ORG Subject: Re: Creating subfile records from list on submit SOLVED Field 179 did it! Thanks, Brian, and everyone else who responded. I didn’t know about that feature so for the benefit of anyone equally ignorant, I’ll copy what the manual says: “To auto-populate a field with a GUID, define a character field using field ID 179. A GUID is available through all filter phases. By contrast, the value of Request ID field is not available until an entry has been successfully committed to the database. You can set the attributes of the GUID field, except for field type, length, and ID.” I created a field called “F179” with an ID of 179. I have filters that end with `!, and during phase 1 they do “Push Fields” to create subfile records with a Parent ID equal to F179. Then at the very end a filter does a “Push Fields” to all subfile records where Parent ID = F179. This filter does not end with `!, so the Push Field runs in phase 2 when the Entry ID has been set, so it updates all the subfile “Parent ID” fields to the real Parent ID. One interesting feature of F179, if you look at the field you don't see any value, but if you follow the filter log you see a long string of gibberish getting pushed to other fields. Thanks again, everyone! Dwayne Original message Date: Thu, 16 Oct 2008 12:18:43 -0700 From: Brien Dieterle [EMAIL PROTECTED] Subject: Re: Creating subfile records from list on submit To: arslist@ARSLIST.ORG ** Right, I think Joe and I are trying to suggest using an ActiveLink and not a filter :-) Brien On Thu, Oct 16, 2008 at 11:34 AM, Grooms, Frederick W [EMAIL PROTECTED] wrote: A Filter does not use the @@: syntax (Evidenced by the v7.1.0 filter AR System Email GUID Generator) I pulled the 38 length from Field 179 on the stock ARS form AR System Email Association Dwayne, Out of curosity, try changing the field to 38 characters long (maybe the command does not like fields 255 characters long. Fred -Original Message- From: Action Request System discussion list(ARSList) __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: Creating subfile records from list on submit SOLVED
Use it with one word of caution though.. It used to not auto populate on 6.3 days and below though it was designed to. You had to use that run process action. They automated the population on release of version 7. Joe - Original Message From: Ben Chernys [EMAIL PROTECTED] To: arslist@ARSLIST.ORG Sent: Thursday, October 16, 2008 5:14:43 PM Subject: Re: Creating subfile records from list on submit SOLVED Guys, Field 179 is just that. A guid that is autopopulated on creation (at least on submit, not sure about merge). All ARS guid fields are 38 bytes long. Any field (not just 179) can be set with the process Application-Generate-Guid xx. That field should be 38 chars long. With field 179, the process does not need to be called and the field will be auto-populated. A lot of times an InstanceId (as the BMC OOTB Apps like to call thier 179 fields) will be set with a set fields @@ process in an Active link so that dependent records may be built before the paent record exists (therby NOT being able to link to field 1). Of course, if the parent is not saved, you must include workflow to delete the saved child records. Cheers Nem -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Dwayne Martin Sent: October 16, 2008 10:43 PM To: arslist@ARSLIST.ORG Subject: Re: Creating subfile records from list on submit SOLVED Field 179 did it! Thanks, Brian, and everyone else who responded. I didn’t know about that feature so for the benefit of anyone equally ignorant, I’ll copy what the manual says: “To auto-populate a field with a GUID, define a character field using field ID 179. A GUID is available through all filter phases. By contrast, the value of Request ID field is not available until an entry has been successfully committed to the database. You can set the attributes of the GUID field, except for field type, length, and ID.” I created a field called “F179” with an ID of 179. I have filters that end with `!, and during phase 1 they do “Push Fields” to create subfile records with a Parent ID equal to F179. Then at the very end a filter does a “Push Fields” to all subfile records where Parent ID = F179. This filter does not end with `!, so the Push Field runs in phase 2 when the Entry ID has been set, so it updates all the subfile “Parent ID” fields to the real Parent ID. One interesting feature of F179, if you look at the field you don't see any value, but if you follow the filter log you see a long string of gibberish getting pushed to other fields. Thanks again, everyone! Dwayne Original message Date: Thu, 16 Oct 2008 12:18:43 -0700 From: Brien Dieterle [EMAIL PROTECTED] Subject: Re: Creating subfile records from list on submit To: arslist@ARSLIST.ORG ** Right, I think Joe and I are trying to suggest using an ActiveLink and not a filter :-) Brien On Thu, Oct 16, 2008 at 11:34 AM, Grooms, Frederick W [EMAIL PROTECTED] wrote: A Filter does not use the @@: syntax (Evidenced by the v7.1.0 filter AR System Email GUID Generator) I pulled the 38 length from Field 179 on the stock ARS form AR System Email Association Dwayne, Out of curosity, try changing the field to 38 characters long (maybe the command does not like fields 255 characters long. Fred -Original Message- From: Action Request System discussion list(ARSList) ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
