That seems like a reasonable idea. I'll need to give that some thought.
Joe _____ From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Joel Sender Sent: Tuesday, September 30, 2014 8:04 PM To: arslist@ARSLIST.ORG Subject: Re: Automated use of the Data Wizard to rename multiple Companies.. Joe, Perhaps a staging form is needed: 1. Instead of trying to submit into DLD:SYS:DataWizAction, create a Staging form that can accept all the rename requests generated. It should contain the data you would push. 2. An Escalation on DLD:Lock runs if the Lock is OFF; to push a trigger [i.e. Status(7)="Go"] to the 'first record found' in the Staging form. 3. Pushing the trigger to the Staging form starts the rename process filters, including the Lock that will prevent the next escalation from firing too soon. HTH, Joel Joel Sender jdsen...@earthlink.net 310.829.5552 From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Joe D'Souza Sent: Tuesday, September 30, 2014 4:12 PM To: arslist@ARSLIST.ORG Subject: Automated use of the Data Wizard to rename multiple Companies.. ** Has anyone attempted this? Here is the challenge. I had attempted to use that Data Wizard to automatically rename a bunch of companies if the name in the AR System did not match the name for the same company from another system - both these systems related the Company records by the Corporate ID, which is the PK between the two systems for Company records. Just for the records the other system is not an AR System based system. So I have a AIE job looking up that other system, reading new company records or modifying existing company records. All this works fine except for the Company name (which is not a simple update to just the COM:Company form only. To update the bunch of other forms that may contain a Company field, for Company name changes I was using the Data Wizard in my workflow. However, the design of the Data Wizard is to process a single rename at a time and to lock the Wizard until that rename is done by creating a record in the DLD:Lock form. This lock record does not allow another record to be created in the DLD:SYS:DataWizAction form, if a lock record exists in the DLD:Lock form. The only way to rename a bunch of companies then is to individually rename each qualifying record. So obviously, I have to reconsider my previous attempt to push a record in the DLD:SYS:DataWizAction form, as after the first record is pushed there, if there is another that the AIE job encounters that qualifies for a rename, it would fail to push a record in the DLD:SYS:DataWizAction form. How would you'll handle this if you'll were tasked to do the same thing considering that I cannot have it done simultaneously as the AIE job runs, but build a list of renames that need to be done, and then work individually on each record. Escalations would probably not be a mechanism to accomplish this as an Escalation would run over the whole list of companies to be renamed and attempt to create DLD:SYS:DataWizAction records one after the other and all records after the first record, subsequent records would fail. I was then thinking of some sort of a Filter loop or a server side table walk but have not got through that whole thought process yet... Any other possibilities I might be not looking at? My last option would be manually triggering each rename because I would like as little human intervention in the process as is possible - IF possible.. Cheers Joe _ARSlist: "Where the Answers Are" and have been for 20 years_ _____ <http://www.avast.com/> This email is free from viruses and malware because avast! Antivirus <http://www.avast.com/> protection is active. _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"