Hello,

 

I keep getting the below error message when trying to import:

Line 1: Index was outside the bounds of the array. [CImport_Process_02.5]

 

Please can you tell me what this is and how to rectify this?

 

Thanks 

 

Steve

This older thread also has some more details about this problem.

I had a fairly complex import where I was creating a Gift and linking to an existing Participant as an "Other Donation" - this was working fine, but then I needed to extend it to link some Gifts as Registration Fees instead, so I added a new virtual field called "RegistrationID" and copied the existing Participant Import ID field into it. Then, in the API code, I added a new statement to the BeforeComputedColumns subroutine to blank out whichever Participant Import ID wasn't applicable.

Unfortunately, the import started giving me this error whenever I tried to reference the new virtual field, whether by field name (Import.Fields.GetByName) or by column reference (Import.Fields.GetByExcelName) - if I commented out the line mentioning the column, then it would run fine, but that defeated the purpose of it. It was definitely not a profile matching or numbering issue.

I did actually get it working at one stage after remapping all of the fields from the same file and re-entering all of the details, but shortly afterwards it stopped working again with the same error. Very occasionally I would get multiple dialog boxes with lots of technical messages about "Out of Memory" errors when starting the Code Editor - most of the time I could close the error dialogs and work in the Code Editor normally, but once nothing came up in the Code Editor at all and it hung. I had to kill the RE7.exe via the Task Manager directly in that case.

In the end, I got it working by deleting the virtual field I'd created and using an existing field in the Field Map that wasn't being used for anything else, and getting my code to copy the Participant Import ID into that field if the Gift was an Event Registration.

If you're interested, I could copy my now-working import, change that copy to use the virtual field, and send all of the relevant files: although I found a workaround, there may be a bug in IOM that needs to be fixed.

Posted By David Seeto on 04 May 2016 02:28 AM
This older thread also has some more details about this problem.

I had a fairly complex import where I was creating a Gift and linking to an existing Participant as an "Other Donation" - this was working fine, but then I needed to extend it to link some Gifts as Registration Fees instead, so I added a new virtual field called "RegistrationID" and copied the existing Participant Import ID field into it. Then, in the API code, I added a new statement to the BeforeComputedColumns subroutine to blank out whichever Participant Import ID wasn't applicable.

Unfortunately, the import started giving me this error whenever I tried to reference the new virtual field, whether by field name (Import.Fields.GetByName) or by column reference (Import.Fields.GetByExcelName) - if I commented out the line mentioning the column, then it would run fine, but that defeated the purpose of it. It was definitely not a profile matching or numbering issue.

I did actually get it working at one stage after remapping all of the fields from the same file and re-entering all of the details, but shortly afterwards it stopped working again with the same error. Very occasionally I would get multiple dialog boxes with lots of technical messages about "Out of Memory" errors when starting the Code Editor - most of the time I could close the error dialogs and work in the Code Editor normally, but once nothing came up in the Code Editor at all and it hung. I had to kill the RE7.exe via the Task Manager directly in that case.

In the end, I got it working by deleting the virtual field I'd created and using an existing field in the Field Map that wasn't being used for anything else, and getting my code to copy the Participant Import ID into that field if the Gift was an Event Registration.

If you're interested, I could copy my now-working import, change that copy to use the virtual field, and send all of the relevant files: although I found a workaround, there may be a bug in IOM that needs to be fixed.

Hi David,

 

Would it be possible for you to send an email to support@omaticsoftware.com with the profile and the import file you were using that kept giving you the error? We'd love to test it further.  Instructions for exporting a profile can be found here.