We hope you'll join us for our 4/23 webinar on using data tables to apply reference ranges and AE codes in OC4. For more information and to register, visit https://register.gotowebinar.com/register/2882170018956684555

RE: Reoccuring problem with bulk data import


With the help of a fellow programmer, we have figured out where the problem was.

In ImportSpringJob.java, protected void executeInternal(), we have the following line of code:

StudyBean studyBean = (StudyBean) studyDAO.findByName(studyName);

If we have more than one study/site with the same name, chances are that the above line of code will not return the one we want. I would suggest replacing findByName with findByOid.

To finish my explanation, this potentially incorrect studyBean is passed to processData(), who calls getImportCRFDataService(), where validateStudyMetadata() rightfully returns the message “your_current_study_is_not_the_same_as”.

Please let me know if you need more information about this bug.



From: Mihai Virtosu
Sent: Thursday, July 08, 2010 1:28 PM
To: [email protected]; '[email protected]'
Subject: Reoccuring problem with bulk data import


I know this is a long shot, but has anyone else experienced problems with bulk data imports telling you that your current study is not the one the data is for?

The error message in my emai is:
Your current study is not the same as the Study University of California Los Angeles, for which you are trying to enter data. Please log out of your current study and into the study for which the data is keyed.
This error message repeats for each import file. I have about 25 import files in each batch/study/site. I do not have any other import jobs for other sites running at the same time.

I assure you that I am selecting the correct study when I create the job and the StudyOID is the correct one for this study. This happens to only about 20% of the sites I am currently importing data for.

The most irritating aspect is that if I upload data manually through the Import Data page, the import succeeds.

I would appreciate if someone who has already run into this can provide any help.

Thank you,



  • Hi Mihai,

    You are correct, when you have studies of the same name, you may or may not get the StudyBean you are looking for using only findByName(), I will change this on 3.0-SNAPSHOT, and hopefully this will be released with the rest of the 3.0.4 fixes.

    Note that, since this information is contained in binary form in the database, you will have to drop and re-create the job once the fix is in place.

    Thanks, Tom

    Tom Hickerson - [email protected]
    Senior Developer
    Akaza Research, LLC
This discussion has been closed.