topic Re: How can you solve this scenario in Talend ? in Talend Studio

How can you solve this scenario in Talend ?

prabuj — Fri, 15 Nov 2024 21:47:31 GMT

Dear Team, @richard Hall @Shicong Hong @Fred Trebuchet

I have data coming like this. Could you give a solution to solve it. ?

AT DAY-1, I load the data into target. IT's a delta process

BOTH ARE SAME CUSTOMER, BUT HAVE NO IDENTITY TO FIND THEY ARE SAME.

AT DAY N, THE CUSTOMER IS SAYING - DAY-2 RECORD IS GOOD ONE. HOW CAN I KEEP A FLAG "AS THE DAY 1 DATA AS OLD CUSTOMER ID", AND "DAY-2 DATA AS NEW CUSTOMER ID".

THANKS IN ADVANCE.

Re: How can you solve this scenario in Talend ?

Anonymous — Thu, 18 May 2023 08:34:19 GMT

If you can't modify the table, create a new table to store the customer id and add a new flag field? Then, whenever you load the data into target in ETL job, synchronize the related data in this identity table.

Regards

Shong

Re: How can you solve this scenario in Talend ?

LLopeza1682662066 — Thu, 18 May 2023 10:36:28 GMT

Hello, try this steps.

Compare the data from DAY-1 and DAY-2 to identify matching customer attributes such as name, address, or any other relevant identifiers.
Use a suitable algorithm or logic to determine the degree of similarity between the DAY-1 and DAY-2 records. This could involve comparing fields for exact matches or utilizing fuzzy matching techniques to account for slight variations in the data.
Based on the comparison results, if a match is found, assign a flag or a unique identifier (e.g., "OLD_CUSTOMER_ID" for DAY-1 data and "NEW_CUSTOMER_ID" for DAY-2 data) to differentiate between the old and new records.
Ensure that the assigned flag or identifier is included in the target data during the delta process and stored accordingly.

By implementing this approach, you can distinguish between the DAY-1 and DAY-2 data and assign appropriate flags or identifiers to indicate whether the customer is considered old or new. Home Bargains Portal