• Replies 4 replies
  • Subscribers 338 subscribers
  • Views 63 views
  • Users 0 members are here
Related

Merging from inside SQL - generating 'criteria' column

Former Member
Former Member $organization

Hi all,

I'm wanting to insert several rows into T_POTENTIAL_DUPS based on some customized criteria that the procedure AP_IDENTIFY_DUPES doesn’t pick up.

What is the best way to generate the 'criteria' column? On custom merges, is usually looks like this: !@#$CUSTOM7969 and I can’t find where and how this is generated.

Last time in inserted a large number of rows into a column using a loop I didn’t know about T_NEXT_ID and so temporarily ‘broke’ the table. I want to check this time!

Thanks for any advice,

Tash 

Parents
  • $organization

    Unknown said:

    What is the best way to generate the 'criteria' column?

    I usually generate it based on the type of potential dupe it is, e.g. for potential dupes with street + phone matches, I use

    left('custom_' + left(x.street1,5) + left(x.postal_code,5),100) "criterion",

    For lname + last-4-CC digits:

    'custom_' + c.lname + '_' + convert(varchar,c.act_no_four) "criterion",

Reply
  • $organization

    Unknown said:

    What is the best way to generate the 'criteria' column?

    I usually generate it based on the type of potential dupe it is, e.g. for potential dupes with street + phone matches, I use

    left('custom_' + left(x.street1,5) + left(x.postal_code,5),100) "criterion",

    For lname + last-4-CC digits:

    'custom_' + c.lname + '_' + convert(varchar,c.act_no_four) "criterion",

Children