• Replies 11 replies
  • Subscribers 337 subscribers
  • Views 265 views
  • Users 0 members are here
Related

Constituent Import

Teresa Dean
$organization

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!!!

Parents
  • $organization

    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 Spieler
    IT Development and Training Manager

    Florida Grand Opera

Reply
  • $organization

    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 Spieler
    IT Development and Training Manager

    Florida Grand Opera

Children