Hi, I am working with a relatively new NPSP org and trying to use the NPSP Data Importer tool to bring in Contacts, Accounts, Donations and Campaign info using an older version of the template. However, per this post -> https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000Eo8VaSAJ the older templates should still work.
The weirdness:
1. When I use the full older template (see attached as ImportFailure.csv) key fields like Payment Method, Contact 1 Work Email, Account1 City and Alternate Emails (among others) don't even make it into the NPSP Data Import object.
2. When I remove the last two columns with notification data (see attached as ImportNarrow.csv), some of the fields above magically start coming in OK even though they have the exact same values. Only difference between the two files is the last two columns.
3. You can see that the Data Import tool (see mappingOK.png) recognizes the values in the Contact1 Email columns so the data is readable and not borked in any obvious way.
4. importfailure.png shows attempting to import the ImportFailure.csv. Fields highlighted in green failed to import.
5. importnarrow.png shows attempting to import the ImportNarrow.csv file. More fields (but not all) now make it into the NPSP Data Import object. Some fields still fail though.
6. I've opened the CSVs in Notepad and there are no obvious issues. I also tried importing with different character sets but to no avail.
I already checked permissions and have confirmed that I have full access to the NPSP Data Import object (all fields and View/Modify All records). I've also assigned the appropriate Perm Set "NPSP Data Import" but permissions can't be the issue because the same user (me) is able to import the troublesome fields from Narrow but not from Failure.
And just because I don't have enough gray hair, I don't encounter the same issue in another NPSP org for a different client. The NPSP Data Import object is the same but the org having the weirdness has Elevate installed and connected (Power of Us edition) and the org where the import works just fine does not have Elevate installed.
The only thing I can think of is some trigger related to Elevate since Elevate uses the NPSP Data Import object but why it would fail with extra columns on the end but work when those last few columns are removed has me saying "What the F(orce.com) is going on?!"
All help much appreciate, thanks in advance.
Hi @David Smith So both orgs had the same mapped fields and field values? That would be strange but I must admit I am not close to the Wizard issue - I only know of it. From an import perspective there may be no difference between an Elevate NPSP org vs a non-Elevate NPSP org - except possibly that FLS is enabled for the Elevate fields on NPSP Data Import in the Elevate org but not in the non-Elevate org.
On the old template, I think it is fine to still use it but the issue will occur if you map too many fields that contain data. Adding @Sam Knox for thoughts on adding a note to the post
