Use existing import set with a separate transform map?

[leochavez]

We currently have an LDAP import process in place to processes user data, but takes some time to run.   As with most organizations more data was required and so we added another attribute, but the data contained within this particular attribute requires extensive processing (string parsing and DB queries), essentially tripling the import run time.   To mitigate this, I created a separate transform map that processes the new attribute data. Looks good so far.

While scheduling a data import, I saw an option to run 'after parent runs'.   Great option for my situation, but this is where my mind began to wonder..... if the data used by both imports are the same, is there was a way to utilize an existing import set (albeit processed), reducing MID Server/LDAP workloads and whatnot.

I'm sure I could hack together a bit of code that would locate the import set via the 'sys_import_set' table, update the state to 'Loaded', at which point a scheduled data import could take over.....or something along those lines.

All that said, is this possible?   Is there a way an existing import set can be reused by another transform map without having to script around it?

[leochavez]

Update:   After reading through the doc's, I was able to configure my transform maps to run sequentially, but after some testing, overall processing time remained the same.   That said, I learned something new and that is always a plus in my book.    

Thanks again Michael.

- Leo