I’ve done similar things using a staging form and an escalation. Create the staging form as either a regular form (and import the CSV file to it) or a view form whose source is a database table containing the data. Then create an escalation that runs (once) on the staging form and applies the changes. That should work as long as the associated workflow is in filters, and doesn’t contain an exception for AR_ESCALATOR.
regards, Aaron (Drake) From: ARSList [mailto:[email protected]] On Behalf Of Dave Barber Sent: Tuesday, April 09, 2019 6:28 AM To: ARSList <[email protected]> Subject: [E] Change Cancellations via import? All, We have a large number of open changes, at various stages from draft through to scheduled for approval from years gone by. I'm hoping to cancel them via a "simple" AR Import. CSV file with the change ID, and then map the various fields. For the change request itself, this seems to work fine. But open approvals against them - they don't get touched. But I am getting nowhere with doing a similar import against either CHG:ChangeAPDetailSignature (which seems to do nothing) or against AP:Signature (where you have to use zTmpAppRequest to match the CRQ reference - but the import fails). Has anyone done such an "automation" before? Any suggestions/pointers? Regards Dave Barber
-- ARSList mailing list [email protected] https://mailman.rrr.se/cgi/listinfo/arslist
