New CRF version validation not used on data import

richard.brookesrichard.brookes Posts: 54
Hi,

Has anyone seen this before?

I have a CRF1 (V1) with validation of "func: range(1, 100)" set on a data item. This works as expected for manual and import data.

I created a new version of CRF1 (V2) updated validation to "func: range(0, 100)" for the data item. This works as expected when manually entering data. 
However if I import data the old validation range is used. 

Yes I have updated XML FormOID with the new version...
I tried restarting the instance.

Any ideas? 

Richard

Comments

  • GerbenRienkGerbenRienk Posts: 748 ✭✭✭
    Hi Richard,
    I have similar experiences with codelists/reponse options: between versions I could expand the list of options-value-pairs, but on import only values of the first version are accepted. Therefore I had to create "new" items, by adding a suffix.
    Gerben Rienk
  • richard.brookesrichard.brookes Posts: 54
    Yes, creating a new item seems the only way forward if you run into this.
    Is this a known bug? I couldn't find anything on jira.

    It seems to be only an issue if you have actually loaded data into V1.

    If I upload V1 (but don't enter any data) then upload V2, it works as expected.

    OC seems to store the definition somewhere (or a link to it) and not update it when a new version is created.


    Richard


  • kristiakkristiak Posts: 1,249 ✭✭✭
    via Email
    Have you made sure the new version has been set to be the default version, otherwise it will use the old version.
  • agoodwinagoodwin Posts: 131 admin
    via Email
    Hi all,


    I'm glad that there is some discussion around this. I did some digging in
    Jira and found this issue:

    https://jira.openclinica.com/browse/OC-6245

    This sounds like the issue that you are talking about. If there are other
    issues, please let me know. We are actually doing some work on import right
    now so I'd like to look at issue related to this.

    Just as an FYI - the work we are doing on import is going to be new
    functionality that does 2 things:
    1. Set what status of the event CRF should be after import (i.e. the status
    should remain "data entry started" or "completed")
    2. Describe whether data should be imported / update based on the current
    status of the event CRF (e.g. if the event CRF is complete, skip import /
    do not update )

    Best,
    Alicia





    On Mon, Apr 27, 2015 at 2:03 AM, richard.brookes <
    forums+d15637@openclinica.org> wrote:

    > Yes, creating a new item seems the only way forward if you run into
    > this.Is this a known bug? I couldn't find anything on jira.
    >
    >
    >
    >
    > It seems to be only an issue if you have actually loaded data into V1.
    >
    >
    >
    >
    > If I upload V1 (but don't enter any data) then upload V2, it works as
    > expected.
    >
    >
    >
    >
    > OC seems to store the definition somewhere (or a link to it) and not
    > update it when a new version is created.
    >
    >
    >
    >
    >
    >
    >
    > Richard
    >
    > --
    > To manage your email notifications, please visit:
    > https://www.openclinica.com/forums#/profile/preferences
    >
    > Reply to this email directly or follow the link below to check it out:
    > https://forums.openclinica.com/discussion/comment/16809#Comment_16809
    >
    >
  • richard.brookesrichard.brookes Posts: 54
    kristiak said:

    Have you made sure the new version has been set to be the default version, otherwise it will use the old version.

    Yes I set the default to the new version. It does not help.

    Richard
  • richard.brookesrichard.brookes Posts: 54
    Hi Alicia

    OC-6245 sounds similar to my issue.

    I also found that you cannot remove/archive old versions sometimes. OC says that the old version is still being used despite migrating all event crfs to the new version.

    Thanks,

    Richard
This discussion has been closed.