cancel
Showing results for 
Search instead for 
Did you mean: 

Erratic behaviour map operation after table comparison

Former Member
0 Kudos

BODI XIR2 11.7.3.6

We want to detect and store changes in source data and store these changes in the target table.

After the table comparison the row has got an update operation code flag and goes to a Map operation that converts Update row types to Normal and discards all other row types.

normal -> discard

update -> normal

insert -> discard

delete -> discard

The map operation behaviour is erratic: sometimes the update row is mapped to normal and sometimes the update is discarded.

Accepted Solutions (0)

Answers (1)

Answers (1)

werner_daehn
Active Contributor
0 Kudos

I would be surprised if that is the case. You could run the dataflow in debug mode, 'cause there you can see the data and the OPCode flag of insert/update/delete after the TC transform.

Former Member
0 Kudos

We are trying to do the same.. and the table comparison is not showing any of records with opcode as update or delete.. it is marking all the records as add and normal..

werner_daehn
Active Contributor
0 Kudos

What is the primary key of source and comparison table? And what columns did you list in the Table Comparison transform as "input keys"?