Thank you both! I generated another ID and pushed it to form. Didn't think about using a GUID. Now I know it for the future!
Regards, Jose Manuel Huerta http://theremedyforit.com/ On Thu, Oct 11, 2012 at 10:50 PM, benny shell <xosi...@gmail.com> wrote: > ** To be honest you'd probably be better off just push a GUID to a field > and using that a a key for whatever relationship between the different > forms. You can generate using a run process command. Sorry to be so breif > but I'm in a hurry. Will send additional information if you need it. > > On Thu, Oct 11, 2012 at 9:50 AM, Jose Manuel Huerta Guillén < > arsl...@theremedyforit.com> wrote: > >> ** I have the next development problem. >> >> I make a PUSH to a form with `! to force it. >> >> This for has workflow that creates more requests at other forms. >> >> If I use $LAST_ID$ keyword I obtain the ID of the last created request, >> but not the one I just created. >> >> I mean: >> >> I create request EPL000000000042 >> This request, creates request JIK000000000132 and LLM000000000822 >> >> When I use $LAST_ID$ just after the PUSH I would like to read >> EPL000000000042, but instead of it, I obtain LLM000000000822 >> >> And this request doesn't have any reference to the original request >> EPL000000000042. >> >> Any solution? >> >> >> Jose Manuel Huerta >> http://theremedyforit.com/ >> >> >> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ >> > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
