Constituent Import

Hello everyone,

I have a problem with the Constituent import process which is driving me crazy. I have created a new Format file and have a data file with a small amount of records in to use for testing - 9 records only.

I'm getting the following error message:

Error 50000, Severity 0, State 0, Procedure , Line 0, Import failed.  AP_CONSTITUENT_IMPORT halted.
Error getting data from \\kriostess\pub\OVIC\Test\Impftp\Ind.txt - Expected row count is less than 1 or is undefined.

We are a RAMP client so I don't have sa rights to the server, but the folder structure is correct and the files are all there. Tessitura support have looked at the files and used them to do an import on one of their systems, so I know there is nothing wrong with the files.

My question: has any other RAMP client experienced this problem and got this error message?

Thanks

Debbie

Parents
  • Hi Debbie,

    We're on RAMP as well, and I remember having some issues with importing constituents via the client utility, but was able to do it successfully via SQL using the following:

    EXEC	[dbo].[AP_CONSTITUENT_IMPORT]
    		@sFileName = '\\kriostess\pub\wool\live\Impftp\Import\au.txt',
    		@lSourceNumber = 20,
    		@cMode = 'I',
    		@lDefaultCustType = 7,
    		@sDefaultCountry = 'USA',
    		@cStripPhone = 'Y',
    		@lSessionId = 0,
    		@cValidateCustomerNo = 'N',
    		@cCreatePotentialDuplicate = 'N',
    		@defaultHouseholdCustType = 8,
    		@formatFilePath = '\\kriostess\pub\wool\live\Impftp\Import\format\import.xml',
    		@attributeKeywordNo = 407,
    		@Debug = 'Y',
    		@ValidateForDuplicates = 'Y'

    I don't know which way you were trying, but this seems to handle and weird folder permissions issues.



    [edited by: Paul Kappel at 8:14 AM (GMT -6) on 8 May 2013]
Reply
  • Hi Debbie,

    We're on RAMP as well, and I remember having some issues with importing constituents via the client utility, but was able to do it successfully via SQL using the following:

    EXEC	[dbo].[AP_CONSTITUENT_IMPORT]
    		@sFileName = '\\kriostess\pub\wool\live\Impftp\Import\au.txt',
    		@lSourceNumber = 20,
    		@cMode = 'I',
    		@lDefaultCustType = 7,
    		@sDefaultCountry = 'USA',
    		@cStripPhone = 'Y',
    		@lSessionId = 0,
    		@cValidateCustomerNo = 'N',
    		@cCreatePotentialDuplicate = 'N',
    		@defaultHouseholdCustType = 8,
    		@formatFilePath = '\\kriostess\pub\wool\live\Impftp\Import\format\import.xml',
    		@attributeKeywordNo = 407,
    		@Debug = 'Y',
    		@ValidateForDuplicates = 'Y'

    I don't know which way you were trying, but this seems to handle and weird folder permissions issues.



    [edited by: Paul Kappel at 8:14 AM (GMT -6) on 8 May 2013]
Children
  • Hi Paul,

    Thanks for the suggestion. Unfortunately I'm getting the same result when I try running the SQL from Management Studio. Will post the solution when I finally get one!

    Debbie

  • Hi Debbie,

    I've been going round in circles for the last few days with a similar issue, my error was a format mis-match.  I asked for advice from the UK bods and Dara helped me get two records correctly formatted.  Now that I try to apply that to more records I'm getting the 'expected row count...' error.  It's driving me mad because it should be so simple!

    Suzanne

  • Hi Suzanne,

    My problem was to do with access rights, so I don't think my solution will help you. It's worth checking that the folder you where you have your import file is accessible by the import process. The error messages don't always match the problem, I have noticed.

    Check for spirous carriage returns at the end of your rows as these could be producing the effect of having more, but empty, rows.

    Once its up and working, its all lovely. Just a pain in the proverbial to get to that point.

    Debbie

  • I often find that my issue with constituent imports is when there is an unexpected character (like a line break, or the proper apostrophes) and the only way is to manually take a look at the text file that you save down (without word wrapping) and check that every constituent starts on a new line.

    Laborious... and yes Debbie, often the error has nothing to do with the actual problem! Very frustrating.

    dgh

  • 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.

     

     

  • 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 

  • Hello,

    We are new to Tessitura and are trying to do our first import. We are getting this same error message:

    Error getting data from ***our file path***- 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.

    I have been over everything ten times and it looks right but it keeps failing. I have ticket in but still waiting to hear. We have a gala invite going out this week so we are trying to get the data into Tess as soon as possible.

    Can you clarify what you mean by the comment tags at the beginning and end of the line?

    Thanks!

    Amanda

  • Hi Amanda,

    I'm sure you will have the correct format if you are using the Tessitura supplied examples, but the lines should all have the correct format:

    <FIELD ID="order_paid_amt" xsi:type="CharTerm" TERMINATOR="\t" />

    but the last field specification must have the "\r\n" code to terminate it properly:

    <FIELD ID="price_type" xsi:type="CharTerm" TERMINATOR="\r\n" MAX_LENGTH="30" COLLATION="SQL_Latin1_General_CP1_CI_AS" />

    Any lines which are purely comments have to start with <!-- and finish with -->otherwise they will be interpreted as code.

    Hope that helps a bit.
    Debbie