DSXchange

Thanks Ray - But will this approach cover the transformation rules? and also,will the future changes to the transformation rules be captured dynamically or is it required to manually update it every time a rule is modified or implemented?

Hi, I have a requirement to establish data lineage from source to target state using infosphere mwb. this should show quality, classification, data definitions, calculations performed and audit trail from Informatica MDM hub. Is there a way to do this? does anyone have any previous experience with t...

Hi, here is the sample input and output First input Firstname lastname phone primarykey Jack Smith 1234 123 Jack Smith 1234 345 after processing through match specification Firstname lastname phone primarykey QSDataId QSMatchsetId Jack Smith 1234 123 1 1 Jack Smith 1234 345 2 1 I am replacing the qs...

Hi, I am generating a golden record based on the matched record. after the match process I replace the primary key in the qsmatchsetid. the matched record is treated as golden record. This works fine for the same set of records . However, when there is addition to the group this golden record seems ...

rjdickson wrote:Did I answer your question?

Sure, you did - Thanks again!!

I meant the keys were pointing to a single master record instead of multiple different records when they were blocked together.

Hi Robert,

your trick does the job well

the only part I am not clear here is when we are grouping by the key in the last pass how come the keys are re-arranged?

Thank you very much. Appreciate your help!! :D

Hi Robert the sample is as shown below. It needs to be a criss-cross match between 2 sets of address lines. to standardize the 2 sets I could run the standardization twice to generate the standardized fields and then pass the data through the match stage to identify the duplicate customers within th...

Hi, Thanks for your replies, yes there are other fields like the names to identify the customers. even if we split the record then lets say record with key x -1 (with first address) is pointing to record with key z and x-2(with second address) is pointing to the record y merging could be a bit cumbe...

Hi, I was looking for alternatives to perform the match. I have 2 different addresses captured in a single record which I wanted to use to identify duplicates. The ways I figured out is to split the records and have a single set of matching fields and run the matching specifications against it. Howe...

Agree - the job can retain parallel mode with the appropriate partitioning. I was mentioning the testing steps that yielded the results :D

I think I have got the solution. Run the job in sequential mode and sort the data based on the key and the timestamp column so that that latest record is processed as the last record. whenever there is a tie survive stage seems to pick the value from the last record(can't bet my life on this ) but t...

Yes I did. Its strange the functionality is limited to greater than and longest length of the string and not like highest, lowest or median values

I have already tried to define expressions like c.timestamp > c.timestamp and also like b.timestamp > b.timestamp but nothing fetches the desired results. the only options available is greater than but not like greatest in version 8.7 An alternate to this could be to sort the data based on the key c...

Thanks Mate, but my requirement is to survive the best record based on most frequent non blank values in case if it is a tie then the tie breaker should be the date. I was looking for the survive stage solutions. or should I restore to the age old transformer method using stage variables?