I have an order import set of data from an external agency. The data has been formatted correctly but many of the rows are failing.
The Tessitura report details the reason as "50000 Error occurred during import, check log.". If I check the table T_IMPORT_SESSION_LOG the corresponding message is consistently "Duplicate: Potential duplicate for existing ID 61050360: Abbott, Penelope. Match using Name and Primary Address." - obviously with a change of customer_no, lname and fname as appropriate. The report itself does not detail any potential duplicates so the only thing I can think of is that it is the potential duplicate that is causing the row to fail.
Can anyone offer any insight into what is happening here?
Martin
There is a setting on the Import Set called Create Potential Duplicate. When checked, potential duplicates will be allowed to be created. This setting defaults to unchecked (‘N’ in the db).
By default the Order Import will fail for a data row if the constituent data is flagged as a potential duplicate.
=>Ryan Creps
@Tessitura Network
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Martin Keen Sent: Thursday, February 27, 2014 11:58 PM To: Ryan Creps Subject: [Tessitura Technical Forum] Order import failure
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Ryan,
Thanks for pointing this out!
Just so I am clear on this, with "Create Potential Duplicate" ticked, even if the utility identifies a potential duplicate, it creates the duplicate anyway and that there is no switch which causes the order to be attached to the existing constituent record?
Given a data row is not matched to an existing constituent based on constituent id or a matching attribute value (import account id), and the constituent data is a potential duplicate, the constituent record will be created. The utility doesn’t make any attempt at using the potential duplicate as the intended account. The utility is designed to not make any false assumptions.
The warnings in Review mode are intended to let the user take action prior to running in create/update mode, such as changing the incoming data to assign a constituent id based upon the flagged duplicates.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Martin Keen Sent: Wednesday, March 5, 2014 11:55 PM To: Ryan Creps Subject: RE: [Tessitura Technical Forum] Order import failure
From: Martin Keen <bounce-martinkeen9803@tessituranetwork.com> Sent: 3/3/2014 4:07:49 PM
Hi Martin,
As this is an old post so not sure if you have already found an appropriate resolution to this issue. What I do is (in continuation to Ryan) once I get the potential duplicates in review mode, I update the constituent ids to input data by looking up street1, city, fname, lname, eaddress of the constituents which fail for a given session.
At the moment I do this :
1. Get potential duplicate errors in review mode.
2. Get the constituent ids based on fname, lname, email, postal address
3. Update the input data with constituent ids
4. Do the subtraction : Ids to merge/Manually updating constituent id = customer_no of Potential duplicates(get from error log) - customer_nos for input data matching with existing constituents based on fname, lname, email, postal address
5. Execute in review mode to confirm the potential duplicates reduced .
6. Decide whether to do manual update by matching the name/contact info for remaining constituents which are potential duplicates or merge them after import.
So the ids to merge are very few say 40 out of 500 potential duplicates in a file of 5000 orders for instance.
It is important to have address consistency to get the customer_no and reduce the constituents merging process. The other way to reduce the merging procedure is to manually punch the constituent id with update statement one by one for the 40 remaining ones. It's a personal choice if you would like to update customer_no for the remaining unmatched potential duplicate constituents or merge them after import.
Regards,
Renu.