Ok, here's my scenario that I'm unclear of how to solve:

Table A has n number of transactions that I need to load all of into my target B. This file has a field on it that needs to be updated to a 'Y' for each record successfully added to B.

Table B has a surrogate key that assigns a one-up number for each individual transaction that gets inserted into it, allowing duplicates.

Here's what I dont know how to do; after the record gets added to the file, how do I go back to the original source and indicate that the record should be updated with a 'Y?' I was thinking about making a temp table that just stored all of the records that were successfully processed by DM, but if I do that, I have no way of ensuring the ON MATCH didnt fail for some reason.

Any suggestions?

I am restating your issue to make sure I understand.

quote:

When the record from table A is successfully put into table B update the table A record with a "Y"

Assuming you have access to servers/databases/tables the easiest way to do this is straight SQL. Actually, as I think about it I wonder why you are using DM for this. So before I blather on about my answer, and look more ignorant than I am in things DM, please explain to me the architecture of your system and why DM is used versus straight SQL to accomplish moving data from one table to another.

If there are key fields in common between table A and table B, then just do another DM data flow with table A inner joined to table B as the source and just table A as the target. Where you find records in both table A and table B, then do an update to table A to set the updated indicator to a "Y".

Related to my last post, I am curious why the whole thing wouldn't be done in SQL in the first place? Is it the proverbial "When you have a hammer ..."?

It just occurred to me that perhaps DM would allow single insert failures while allowing the rest to succeed. Is that where my ignorance of DM is stopping me?

BTW: Jewssica's answer is where I was going in my SQL only thread.