• Replies 1 reply
  • Subscribers 337 subscribers
  • Views 359 views
  • Users 0 members are here
Related

Constituent Import

Former Member
Former Member $organization

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

Parents
  • $organization

    Hi Wendell,

    I've had this error a couple of times - I find the constituent import is really troubling and the error messaging isn't helpful in the slightest. That said, the problems I have are usually related to foreign characters finding their way in to the data file; such as if you're copying and pasting in from another source.

    That particular error message - in my mind - means that the data file contains a cell with no content and it's trying to be inserted in to a data area where nulls aren't allowed. For example, lname.

    I have one theory as to why you trying to import the old files no longer works. Did you close and reopen Tessi after you got the import fail message? When I was getting those fails I had to restart every time as the error seemed to halt the import and it would confuse any subsequent imports in that session.

    Try cutting down your import data file to a couple of rows and see if it imports a small segment of data. That might also help narrow down on to the row that's causing it to fail.

    Good luck,

    David

Reply
  • $organization

    Hi Wendell,

    I've had this error a couple of times - I find the constituent import is really troubling and the error messaging isn't helpful in the slightest. That said, the problems I have are usually related to foreign characters finding their way in to the data file; such as if you're copying and pasting in from another source.

    That particular error message - in my mind - means that the data file contains a cell with no content and it's trying to be inserted in to a data area where nulls aren't allowed. For example, lname.

    I have one theory as to why you trying to import the old files no longer works. Did you close and reopen Tessi after you got the import fail message? When I was getting those fails I had to restart every time as the error seemed to halt the import and it would confuse any subsequent imports in that session.

    Try cutting down your import data file to a couple of rows and see if it imports a small segment of data. That might also help narrow down on to the row that's causing it to fail.

    Good luck,

    David

Children
No Data