Updating Page Two Value on Import
Import Event Triggers were not added with the Event system. If you submit a SR for an Enhancement, I think the most likely improvement will be a single trigger after the Import completes with a list of the objects touched. Import uses a batch system behind the scenes that tries 200 or 400 writes at a time. From the Oracle perspective, the system would completely bog down to throw an event on every object update.
To work around this, you may have to update an extra field that can be used in Search, like “Import Date” or anything to signal this object was just imported against. Then, have a saved or SDK search that identifies this list of objects, and run a SDK program against them (tools menu?) to perform your post import updates. I know this is painful, but it could allow you to create a repeatable user process.
Another alternative is to bypass the Agile Import UI altogether. Throw up a separate Web Page to collect an Excel import file, then use SDK to call Import, then run your post process code. The nice thing about this separate UI is that you can control what the user is importing against.
Thanks for the info. Yes, i see this a limitation.
As a work-around what i did is, i saved a search for the creation date. Then i have written an event and configured it as a batch job which runs on hourly basis and implements the batch job.
I think we thought alike on the work-around. Thank u so much.