I'm doing several constituent imports today from txt files and in Review mode I'm seeing something I haven't seen before. It looks like there are some potential duplicates (which is normal), but for this particular file, there is no data telling me the potential account number and the new account number as I normally see. Has anyone else had this before and if so, what does it mean and how can I get the account information for the duplications?
Thanks in advance for any insight!!!
What constituent type is it for? I vaguely remember seeing something like this when we were importing something other than individuals.
Ok, that would help explain it then…..I’m importing Corporations.
Teresa
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Kjersten Schladetzky Sent: Wednesday, October 05, 2011 3:32 PM To: Teresa Dean Subject: Re: [Tessitura Technical Forum] Constituent Import
From: Teresa Dean <bounce-teresadean9276@tessituranetwork.com> Sent: 10/5/2011 3:26:27 PM
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!
I found this defect was discovered while enhancing the Constituent Import for v11. This is fixed now!
The issue was the NULL first name value was causing the potential duplicate message to be NULL in its entirety.
+Ryan Creps
+Tessitura Network
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Teresa DeanSent: Wednesday, October 05, 2011 1:37 PMTo: Ryan CrepsSubject: RE: [Tessitura Technical Forum] Constituent Import
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Kjersten SchladetzkySent: Wednesday, October 05, 2011 3:32 PMTo: Teresa DeanSubject: Re: [Tessitura Technical Forum] Constituent Import
From: Teresa Dean <bounce-teresadean9276@tessituranetwork.com>Sent: 10/5/2011 3:26:27 PM
Thanks Ryan.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Ryan Creps Sent: Wednesday, October 05, 2011 4:22 PM To: Teresa Dean Subject: RE: [Tessitura Technical Forum] Constituent Import
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Teresa Dean Sent: Wednesday, October 05, 2011 1:37 PM To: Ryan Creps Subject: RE: [Tessitura Technical Forum] Constituent Import
Here’s one common issue that I see.
If fields in the import format file have been rearranged, make sure that the last field (and no other field) in the RECORD section defines the EOL terminator (\r\n):
<FIELD ID="eaddress" xsi:type="CharTerm" TERMINATOR="\r\n" MAX_LENGTH="80" COLLATION="SQL_Latin1_General_CP1_CI_AS"/>
<!-- The last line of the record node should have a TERMINATOR="\r\n" to indicate the end of the import row. -->
=>Ryan Creps
@Tessitura Network
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of David Geoffrey Hall Sent: Wednesday, December 18, 2013 11:37 PM To: Ryan Creps Subject: Re: [Tessitura Technical Forum] Constituent Import
Hi Aaron, that error is what happens when the columns in the XML file do not match the columns in the import file, and vice versa. Have you forgotten to remove the comment tags at the beginning and END of the line in your XML file?
If you can post a copy of your XML file and the headers from your text file I'll happily have a look.
Cheers,
dgh
From: Aaron Waapu <bounce-aaronwaapu3789@tessituranetwork.com> Sent: 12/18/2013 10:21:39 PM
Hi Debbie, how did you overcome the access rights issue? I am experiencing the same error message and its driving me bonkers!
I am also getting an Error 7330? Ring a bell?
Thanks!!
---
Error getting data from \\svrfile01\Tessitura\ImportLists\8967.txt - Cannot fetch a row from OLE DB provider "BULK" for linked server "(null)". The import file data may be out of sync with the specified format file.
Error 50000, Severity 0, State 0, Procedure , Line 0, Import failed. AP_CONSTITUENT_IMPORT halted.
We have also been working with the standard import utility.
Just $0.02. You have likely already looked at this.
We have seen problems like this when you do not have a space in the last column of data exported.
This can be impacted by the way we exported from MS Excel. (Presuming you are using Excel to cleanup your data.) Highlight copy and paste may not work well depending where you past the results. Notepad ++ seems to be better than some options.
If I remember correctly we like the option “Save as” and choose “Text (Tab delimited) (*.txt)” as the save as type.
--Tom
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Wendell BaskinSent: Monday, January 13, 2014 5:34 PMTo: Thomas BrownSubject: [Tessitura Technical Forum] Constituent Import
Several months ago I imported many constituents from using legacy data. Referencing the Help system I configured the .xml file and the input (.txt) file. The import process worked as expected, with no errors.Now, I'm experiencing a problem importing constituent data.When I attempt to import constituent data in Review mode (in Test), this error appears:Error #515. Cannot import NULL into column "message" in T_IMPORT_SESSION_LOG.This error didn't appear during earlier imports. So, I ran the import process referencing those earlier files (the files were not changed). The same error message now appears using these older files.Data is being loaded into TW_CONSTITUENT_IMPORT, but that data is not imported into Tessitura.And, for each import attempt, data is being written to T_IMPORT_SESSION_LOG (including data in the "message" column). I'm puzzled.I found some references to T_IMPORT_SESSION_LOG on the network, and continue to look for possible solutions.Reviewing previous posts it appears constituent imports can be a challenge. I would be grateful if someone could point me in a better direction.Thanks, everyone, and Best RegardsWendell Baskin (wbaskin@basshall.com)Bass Hall - Fort Worth
Thanks for everyone’s comments.
After contacting TASK, it appears the problem may be related to database permissions.
Best regards
Wendell Baskin
Bass Hall – Fort Worth
From: Wendell Baskin <bounce-wendellbaskin7249@tessituranetwork.com> Sent: 1/13/2014 4:20:51 PM
Several months ago I imported many constituents from using legacy data. Referencing the Help system I configured the .xml file and the input (.txt) file. The import process worked as expected, with no errors. Now, I'm experiencing a problem importing constituent data. When I attempt to import constituent data in Review mode (in Test), this error appears: Error #515. Cannot import NULL into column "message" in T_IMPORT_SESSION_LOG. This error didn't appear during earlier imports. So, I ran the import process referencing those earlier files (the files were not changed). The same error message now appears using these older files. Data is being loaded into TW_CONSTITUENT_IMPORT, but that data is not imported into Tessitura. And, for each import attempt, data is being written to T_IMPORT_SESSION_LOG (including data in the "message" column). I'm puzzled. I found some references to T_IMPORT_SESSION_LOG on the network, and continue to look for possible solutions. Reviewing previous posts it appears constituent imports can be a challenge. I would be grateful if someone could point me in a better direction. Thanks, everyone, and Best Regards Wendell Baskin (wbaskin@basshall.com) Bass Hall - Fort Worth
Hi, Amanda:
I think, when I got that error, it was because my import file didn’t match the format file I had selected.
When you import, you have a number of fields (prefix, fname, mname, lname, suffix, prefix2, fname2, mname2, lname2, suffix2, etc.) that are in your imput file. You also have an xml file selected in the Format File Path parameter of the report that provides an import template. The fields in the xml file need to match the fields in your import file.
The example below shows the first two fields as described in the the xml file, first in the section with field id, then in the column source section, with the prefix column commented out:
<!-- <FIELD ID="prefix" xsi:type="CharTerm" TERMINATOR="\t" MAX_LENGTH="30" COLLATION="SQL_Latin1_General_CP1_CI_AS"/> -->
<FIELD ID="fname" xsi:type="CharTerm" TERMINATOR="\t" MAX_LENGTH="20" COLLATION="SQL_Latin1_General_CP1_CI_AS"/>
<!>
<COLUMN SOURCE="fname" NAME="fname" xsi:type="SQLVARYCHAR"/>
If I use that xml file in the Format File Path parameter, my import file can’t have a prefix field.
I set up my import files in Excel and then save them, after deleting the first row with field headers, as a txt file. I use the following column headers:
A: prefix
B: fname
C: mname
D: lname
E: suffix
F: prefix2
G: fname2
H: mname2
I: lname2
J: suffix2
K: street1
L: street2
M: street3
N: city
O: state
P: postal_code
Q: country_desc
R: phone1
S: phone2
T: eaddress
U: attribute
V: constituent_type
W: customer_no
X: space
I get my data organized and edited, then, in column X, put a space to indicate the end of a row of data. I copy that space down for the entire column.
Lucie
______________________________Lucie SpielerIT Development and Training Manager
Florida Grand Opera
Just trying this out now.
Lucie,
Do you comment out the local use 0-9 in the XML? Do you move the TERMINATOR ="r\n" to the customer_no line?
Thanks
Hi, Nick:
I just added the xml file I use to my documents: http://www.tessituranetwork.com/Community/members/luciespieler8144/files/default.aspx
The txt file has columns in the same order as those referenced in the xml file. In the customer_no field, I put a space, copied down for all data rows.
Lucie Spieler Florida Grand Opera
Also make sure your 'prefix' has a full stop/period so 'Mr' MUST be 'Mr.'
Are you using any of the 'local_use' fields and realigning the data after import?