Bug Workaround

When a discrepancy is raised against a field in the last row of a Grid, I am unable to close the discrepancy and the form. What’s the workaround?

Comments

  • willilx9willilx9 Posts: 40
    Are there workarounds besides upgrading for the issues listed below?

    Data Entry in Repeating Groups
    * There are problems with adding/ saving data on the last displayed row in a repeating group whether the data item is a part of rules target or not. An example of an issue is during the administrative editing phase; entering discrepancy note(s) on the last added row will cause the discrepancy note(s) to get saved to the first row. Also, saving data on the last row of the displayed repeating group that is a part of rules target triggers an alert that prevents user from going to the next section. The following issues fall under this category: Issue 12108, 12190, 12191, 11827, 12091, 12174
    Sent: Thursday, May 30, 2013 1:39 PM
    To: [email protected]
    Subject: [Developers] Bug Workaround

    When a discrepancy is raised against a field in the last row of a Grid, I am unable to close the discrepancy and the form. What’s the workaround?
  • LizRLizR Posts: 60
    Even in the upgrade, it isn't perfect, yet.
    Do not enter data on the last line of a repeating group.
    Liz Robertson
    Director of Data Management and IT
    TRACON Pharmaceuticals, Inc.
    [email protected]
    office: 858.550.0780 ext. 237
    cell: 760.481.5527
    Sent: Thursday, May 30, 2013 1:45 PM
    To: [email protected]
    Subject: Re: [Developers] Bug Workaround
    Are there workarounds besides upgrading for the issues listed below?

    Data Entry in Repeating Groups
    * There are problems with adding/ saving data on the last displayed row in a repeating group whether the data item is a part of rules target or not. An example of an issue is during the administrative editing phase; entering discrepancy note(s) on the last added row will cause the discrepancy note(s) to get saved to the first row. Also, saving data on the last row of the displayed repeating group that is a part of rules target triggers an alert that prevents user from going to the next section. The following issues fall under this category: Issue 12108, 12190, 12191, 11827, 12091, 12174
    Sent: Thursday, May 30, 2013 1:39 PM
    To: [email protected]
    Subject: [Developers] Bug Workaround

    When a discrepancy is raised against a field in the last row of a Grid, I am unable to close the discrepancy and the form. What’s the workaround?
  • ccollinsccollins Posts: 376 admin
    Hi Lance,
    Where there are workarounds they are noted in the tickets. Most of the workarounds are not great ones, unfortunately. The most serious of these bugs are resolved in 3.1.3 and 3.1.3.1, which (along with performance and system stability improvements) is why we so strongly recommend upgrading.
    Your initial question is I believe specifically related to https://issuetracker.openclinica.com/view.php?id=12190, as noted in the ticket the workaround is to 'click "add" on the repeating group section so that you are not "entering" data on the last row. For example,if the CRF displays 3 repeating rows by default, you should click "Add" so that there are a total of 4 repeating rows, and then enter data on the third row that triggers the rules. You will be able to be prompted to the next section.'
    Best,
    Cal
    On Thu, May 30, 2013 at 4:45 PM, Williams, Lance L wrote:
    Are there workarounds besides upgrading for the issues listed below?

    Data Entry in Repeating Groups
    * There are problems with adding/ saving data on the last displayed row in a repeating group whether the data item is a part of rules target or not. An example of an issue is during the administrative editing phase; entering discrepancy note(s) on the last added row will cause the discrepancy note(s) to get saved to the first row. Also, saving data on the last row of the displayed repeating group that is a part of rules target triggers an alert that prevents user from going to the next section. The following issues fall under this category: Issue 12108, 12190, 12191, 11827, 12091, 12174
    Sent: Thursday, May 30, 2013 1:39 PM
    To: [email protected]
    Subject: [Developers] Bug Workaround

    When a discrepancy is raised against a field in the last row of a Grid, I am unable to close the discrepancy and the form. What’s the workaround?
  • willilx9willilx9 Posts: 40
    Are you creating another instance and entering the rest of the
    Sent: Thursday, May 30, 2013 1:57 PM
    To: [email protected]
    Subject: Re: [Developers] Bug Workaround

    Even in the upgrade, it isn't perfect, yet.
    Do not enter data on the last line of a repeating group.

    Liz Robertson
    Director of Data Management and IT
    TRACON Pharmaceuticals, Inc.
    [email protected]
    office: 858.550.0780 ext. 237
    cell: 760.481.5527
    Sent: Thursday, May 30, 2013 1:45 PM
    To: [email protected]
    Subject: Re: [Developers] Bug Workaround
    Are there workarounds besides upgrading for the issues listed below?

    Data Entry in Repeating Groups
    There are problems with adding/ saving data on the last displayed row in a repeating group whether the data item is a part of rules target or not. An example of an issue is during the administrative editing phase; entering discrepancy note(s) on the last added row will cause the discrepancy note(s) to get saved to the first row. Also, saving data on the last row of the displayed repeating group that is a part of rules target triggers an alert that prevents user from going to the next section. The following issues fall under this category: Issue 12108, 12190, 12191, 11827, 12091, 12174
    Sent: Thursday, May 30, 2013 1:39 PM
    To: [email protected]
    Subject: [Developers] Bug Workaround

    When a discrepancy is raised against a field in the last row of a Grid, I am unable to close the discrepancy and the form. What’s the workaround?
  • willilx9willilx9 Posts: 40
    What if you have rules that trigger on a blank field in the Grid?
    Sent: Thursday, May 30, 2013 1:59 PM
    To: [email protected]
    Subject: Re: [Developers] Bug Workaround

    Hi Lance,

    Where there are workarounds they are noted in the tickets. Most of the workarounds are not great ones, unfortunately. The most serious of these bugs are resolved in 3.1.3 and 3.1.3.1, which (along with performance and system stability improvements) is why we so strongly recommend upgrading.

    Your initial question is I believe specifically related to https://issuetracker.openclinica.com/view.php?id=12190, as noted in the ticket the workaround is to 'click "add" on the repeating group section so that you are not "entering" data on the last row. For example,if the CRF displays 3 repeating rows by default, you should click "Add" so that there are a total of 4 repeating rows, and then enter data on the third row that triggers the rules. You will be able to be prompted to the next section.'

    Best,
    Cal



    On Thu, May 30, 2013 at 4:45 PM, Williams, Lance L wrote:
    Are there workarounds besides upgrading for the issues listed below?

    Data Entry in Repeating Groups
    There are problems with adding/ saving data on the last displayed row in a repeating group whether the data item is a part of rules target or not. An example of an issue is during the administrative editing phase; entering discrepancy note(s) on the last added row will cause the discrepancy note(s) to get saved to the first row. Also, saving data on the last row of the displayed repeating group that is a part of rules target triggers an alert that prevents user from going to the next section. The following issues fall under this category: Issue 12108, 12190, 12191, 11827, 12091, 12174
    Sent: Thursday, May 30, 2013 1:39 PM
    To: [email protected]
    Subject: [Developers] Bug Workaround

    When a discrepancy is raised against a field in the last row of a Grid, I am unable to close the discrepancy and the form. What’s the workaround?
  • LizRLizR Posts: 60
    Hopefully, you're doing this row by row, so there has to be something in the row before this fires for anything else in the row?
    Liz Robertson
    Director of Data Management and IT
    TRACON Pharmaceuticals, Inc.
    [email protected]
    office: 858.550.0780 ext. 237
    cell: 760.481.5527
    Sent: Thursday, May 30, 2013 3:00 PM
    To: [email protected]
    Subject: Re: [Developers] Bug Workaround
    What if you have rules that trigger on a blank field in the Grid?
    Sent: Thursday, May 30, 2013 1:59 PM
    To: [email protected]
    Subject: Re: [Developers] Bug Workaround

    Hi Lance,

    Where there are workarounds they are noted in the tickets. Most of the workarounds are not great ones, unfortunately. The most serious of these bugs are resolved in 3.1.3 and 3.1.3.1, which (along with performance and system stability improvements) is why we so strongly recommend upgrading.

    Your initial question is I believe specifically related to https://issuetracker.openclinica.com/view.php?id=12190, as noted in the ticket the workaround is to 'click "add" on the repeating group section so that you are not "entering" data on the last row. For example,if the CRF displays 3 repeating rows by default, you should click "Add" so that there are a total of 4 repeating rows, and then enter data on the third row that triggers the rules. You will be able to be prompted to the next section.'

    Best,
    Cal



    On Thu, May 30, 2013 at 4:45 PM, Williams, Lance L wrote:
    Are there workarounds besides upgrading for the issues listed below?

    Data Entry in Repeating Groups
    There are problems with adding/ saving data on the last displayed row in a repeating group whether the data item is a part of rules target or not. An example of an issue is during the administrative editing phase; entering discrepancy note(s) on the last added row will cause the discrepancy note(s) to get saved to the first row. Also, saving data on the last row of the displayed repeating group that is a part of rules target triggers an alert that prevents user from going to the next section. The following issues fall under this category: Issue 12108, 12190, 12191, 11827, 12091, 12174
    Sent: Thursday, May 30, 2013 1:39 PM
    To: [email protected]
    Subject: [Developers] Bug Workaround

    When a discrepancy is raised against a field in the last row of a Grid, I am unable to close the discrepancy and the form. What’s the workaround?
  • willilx9willilx9 Posts: 40
    Once the row is created, values in the row are expected.
    Sent: Thursday, May 30, 2013 3:25 PM
    To: [email protected]
    Subject: Re: [Developers] Bug Workaround

    Hopefully, you're doing this row by row, so there has to be something in the row before this fires for anything else in the row?

    Liz Robertson
    Director of Data Management and IT
    TRACON Pharmaceuticals, Inc.
    [email protected]
    office: 858.550.0780 ext. 237
    cell: 760.481.5527
    Sent: Thursday, May 30, 2013 3:00 PM
    To: [email protected]
    Subject: Re: [Developers] Bug Workaround
    What if you have rules that trigger on a blank field in the Grid?
    Sent: Thursday, May 30, 2013 1:59 PM
    To: [email protected]
    Subject: Re: [Developers] Bug Workaround

    Hi Lance,

    Where there are workarounds they are noted in the tickets. Most of the workarounds are not great ones, unfortunately. The most serious of these bugs are resolved in 3.1.3 and 3.1.3.1, which (along with performance and system stability improvements) is why we so strongly recommend upgrading.

    Your initial question is I believe specifically related to https://issuetracker.openclinica.com/view.php?id=12190, as noted in the ticket the workaround is to 'click "add" on the repeating group section so that you are not "entering" data on the last row. For example,if the CRF displays 3 repeating rows by default, you should click "Add" so that there are a total of 4 repeating rows, and then enter data on the third row that triggers the rules. You will be able to be prompted to the next section.'

    Best,
    Cal



    On Thu, May 30, 2013 at 4:45 PM, Williams, Lance L wrote:
    Are there workarounds besides upgrading for the issues listed below?

    Data Entry in Repeating Groups
    There are problems with adding/ saving data on the last displayed row in a repeating group whether the data item is a part of rules target or not. An example of an issue is during the administrative editing phase; entering discrepancy note(s) on the last added row will cause the discrepancy note(s) to get saved to the first row. Also, saving data on the last row of the displayed repeating group that is a part of rules target triggers an alert that prevents user from going to the next section. The following issues fall under this category: Issue 12108, 12190, 12191, 11827, 12091, 12174
    Sent: Thursday, May 30, 2013 1:39 PM
    To: [email protected]
    Subject: [Developers] Bug Workaround

    When a discrepancy is raised against a field in the last row of a Grid, I am unable to close the discrepancy and the form. What’s the workaround?
  • willilx9willilx9 Posts: 40
    I was able to run the checks in Batch as a workaround.
    Sent: Thursday, May 30, 2013 1:59 PM
    To: [email protected]
    Subject: Re: [Developers] Bug Workaround

    Hi Lance,

    Where there are workarounds they are noted in the tickets. Most of the workarounds are not great ones, unfortunately. The most serious of these bugs are resolved in 3.1.3 and 3.1.3.1, which (along with performance and system stability improvements) is why we so strongly recommend upgrading.

    Your initial question is I believe specifically related to https://issuetracker.openclinica.com/view.php?id=12190, as noted in the ticket the workaround is to 'click "add" on the repeating group section so that you are not "entering" data on the last row. For example,if the CRF displays 3 repeating rows by default, you should click "Add" so that there are a total of 4 repeating rows, and then enter data on the third row that triggers the rules. You will be able to be prompted to the next section.'

    Best,
    Cal



    On Thu, May 30, 2013 at 4:45 PM, Williams, Lance L wrote:
    Are there workarounds besides upgrading for the issues listed below?

    Data Entry in Repeating Groups
    There are problems with adding/ saving data on the last displayed row in a repeating group whether the data item is a part of rules target or not. An example of an issue is during the administrative editing phase; entering discrepancy note(s) on the last added row will cause the discrepancy note(s) to get saved to the first row. Also, saving data on the last row of the displayed repeating group that is a part of rules target triggers an alert that prevents user from going to the next section. The following issues fall under this category: Issue 12108, 12190, 12191, 11827, 12091, 12174
    Sent: Thursday, May 30, 2013 1:39 PM
    To: [email protected]
    Subject: [Developers] Bug Workaround

    When a discrepancy is raised against a field in the last row of a Grid, I am unable to close the discrepancy and the form. What’s the workaround?
This discussion has been closed.