Trouble Importing Con IDs to existing records

Andrea Nash

Hello!  Our database does not lock the con id field so almost 200 have been erased.  When I try to upload a new con id using the import id as the way to match up records I keep getting this error message:  Invalid field value: Field is read only. Import ID



Anyone have a solution?

Ryan Hyde

Looks like you're telling the import to update the wrong ID field. 



I don't know where your errors are, so I'm just going to describe how I'd do this from beginning to end:



1.) To start, you should have is a .csv file with two columns: import ID and con ID. The import ID is coming from their record in RE, and the constituent ID is either being assigned anew or being matched up with some sort of spreadsheet backup you had. 

2.) In the first tab of your constituent import screen, you want to make sure that you have "update records" selected, and also "validate data only" for the time being (just so you can test without accidentally screwing something up)

3.) Attach your .csv file, and make sure you leave the import method on "import ID"

4.) on the 3rd tab, match up the import ID with Constituent Information > Import ID (shows up as ImportID) and match the Constituetn ID that you're updating with Constituent Information > Constituent ID (shows up as ConsID)

5.) Run the import. It should work fine at this point. If everything checks out, uncheck the "validate only" checkbox in tab 1 of your import screen and run it again to commit your changes.



Let us know if this does or does not work.

Andrea Nash

Thanks for replying Ryan!



That is exactly what I did - and tried it again looking at your check list just to make sure - and I'm still getting an invalid error message.



Is the Import ID set up as read only in config or somewhere?

Andrea Nash

I've uploaded the error log just in case this sheds some light on what I'm doing wrong



And they would not let me upload the CSV file but the PDF called reupdate reflects what I have in terms of columns and headers

Andrea Nash

by any chance would you happen to know how to lock editing on the Con ID field.  We are on version 7.92 and I know they have added the functionality for 7.93 but I was not sure if there was a way to do it in this older version

Ryan Hyde

This is a little strange. Juding by the error log, you have everything set up correctly. The only thing that jumps out at me is that you don't need the key indicator column at all, unless you're trying to change the records from orgs to individuals. Otherwise it's superfluous. 



Are you trying to restore IDs to what they were before they were wiped out? Does it matter if they have exactly the same ID? Do a test run (maybe on a test constituent) using the "next constituent ID in line." Go to Config > Business Rules > Generate IDs > Change Number, then copy the next available ID that it gives you. You have to be sure nobody else creates a new constituent while you're running this test. Then set up your import exactly the same way you have it (minus the key indicator) and see if you can change the constituent ID. 



But that error is weird. Import IDs are always read-only, and it doesn't appear you're trying to update the Import ID. Maybe this is a known issue in 7.92 - your time might be better spent on chat support with an actual RE rep. 

Andrea Nash

Thanks Ryan - if nothing else I feel better knowing it at least looks like it should work.



I tried the test you mentioned and got the same result - exception report



The reason I have the Key Indicator is the import was telling me it was needed - was not sure why



I agree...need to talk to support - also need to get the database updated to a more current release if possible (just started this job 2 weeks ago and this is what I'm inheriting)

Ryan Hyde

Yeah, if it's telling you that you need the key indicator, then that's some funny business related to 7.92. I'd say your first order of business is getting yourself updated to 7.93, or perhaps waiting until 7.95 is released. However, be aware that there are going to be headaches with 7.95, most likely, assuming they're still merging contact data the way they did in 7.94. There will be a fair amount of data cleanup that you'll have to do afterward. 



So yeah, maybe see if you can't update to 7.93. 

Nicole S

Andrea -- not sure if you solved this or not, but is it possible you are trying to import the import ID and not the constituent ID?  Import ID is hard coded and constituent ID is not.

Andrea Nash

Nicole San Miguel:

Andrea -- not sure if you solved this or not, but is it possible you are trying to import the import ID and not the constituent ID?  Import ID is hard coded and constituent ID is not.

Thanks Nicole.  I'm trying to add a Con ID to these records (the Con ID got deleted from the records) and I'm using the Import ID to match up the records.  Is there a way I should be better indicating what I'm trying to do?  Maybe I should be doing a global change on these records instead of an import?