"Err in Sub CognosDependentFormsRequery. No current record." when clicking "Close with updates" after entering from CSS: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
{{ | {{Fixed bug}} | ||
The following error intermittently happens: | The following error intermittently happens: | ||
"Err in Sub CognosDependentFormsRequery. No current record." | "Err in Sub CognosDependentFormsRequery. No current record." | ||
| Line 7: | Line 7: | ||
* When the “exclude patient button” was clicked upon in a patient profile entry using CSS on the S4 laptop; the error message popped up, and when "OK" is clicked the collector was booted to main page. Upon reentry to the CSS list, all remaining unentered profiles were missing. | * When the “exclude patient button” was clicked upon in a patient profile entry using CSS on the S4 laptop; the error message popped up, and when "OK" is clicked the collector was booted to main page. Upon reentry to the CSS list, all remaining unentered profiles were missing. | ||
The error was not reported by any other sites, even as discussed at Task. | |||
No way to consistently replicate the problem was provided, even as discussed at Task. | |||
=== Work-around === | === Work-around === | ||
The missing CSS records show back up if you close and open the CSS form. | The missing CSS records show back up if you close and open the CSS form. However, it was also reported that the records don't reappear. No clear info was available. | ||
=== Possible cause/pattern - bug adds to exclusion list === | === Possible cause/pattern - bug adds to exclusion list === | ||
When we looked into a recent record where Pagasa found a missing continued admission, we ended up finding it in [[SL Cognos2 Service exclusions table]]. There was discussion whether this bug could have put it in there. Since I don't know how the bug works yet, it is ''possible'' but seems very unlikely. Adding a record to the exclusion list requires building a line and adding it to the exclusion table, one for each record that should disappear. The only place I run that from is from clicking the exclude button. So somehow the bug would have to either click that button or otherwise run that code for each of the remaining records on the CSS list. I can’t think of a mechanism that would do that. | When we looked into a recent record where Pagasa found a missing continued admission, we ended up finding it in [[SL Cognos2 Service exclusions table]]. There was discussion whether this bug could have put it in there. Since I don't know how the bug works yet, it is ''possible'' but seems very unlikely. Adding a record to the exclusion list requires building a line and adding it to the exclusion table, one for each record that should disappear. The only place I run that from is from clicking the exclude button. So somehow the bug would have to either click that button or otherwise run that code for each of the remaining records on the CSS list. I can’t think of a mechanism that would do that. | ||
No further info was provided. | |||
== Log == | == Log == | ||
* 2022-06-22 Discussed at TASK meeting, doesn't seem to be a problem any longer; setting to "resolved bug" to keep history in case this comes back up. | |||
* 2022-04-21 A bunch of similar errors showed up over edits over the last few days. Hopefully fixing those will have fixed this as well. Those errors were showing up in places that had not been edited, making me wonder if an Office update brought some of them up. The problem might be fixed now, so let me know if it happens again for sure. | * 2022-04-21 A bunch of similar errors showed up over edits over the last few days. Hopefully fixing those will have fixed this as well. Those errors were showing up in places that had not been edited, making me wonder if an Office update brought some of them up. The problem might be fixed now, so let me know if it happens again for sure. | ||
* 2022-03-13 FIrst reported this was occasionally happening on the S4 and S5 laptops. | * 2022-03-13 FIrst reported this was occasionally happening on the S4 and S5 laptops. | ||
Revision as of 13:03, 2022 June 22
The following error intermittently happens:
"Err in Sub CognosDependentFormsRequery. No current record."
It intermittently happens in the following scenarios:
- Following entry of an admission profile using CSS, when the "close with updates" button was clicked the error message popped up, and when "OK" is clicked, the collector is returned to the main CSS list; however, any remaining unentered admissions all disappeared. This has occurred on both S4 and S5 laptops.
- When the “exclude patient button” was clicked upon in a patient profile entry using CSS on the S4 laptop; the error message popped up, and when "OK" is clicked the collector was booted to main page. Upon reentry to the CSS list, all remaining unentered profiles were missing.
The error was not reported by any other sites, even as discussed at Task.
No way to consistently replicate the problem was provided, even as discussed at Task.
Work-around
The missing CSS records show back up if you close and open the CSS form. However, it was also reported that the records don't reappear. No clear info was available.
Possible cause/pattern - bug adds to exclusion list
When we looked into a recent record where Pagasa found a missing continued admission, we ended up finding it in SL Cognos2 Service exclusions table. There was discussion whether this bug could have put it in there. Since I don't know how the bug works yet, it is possible but seems very unlikely. Adding a record to the exclusion list requires building a line and adding it to the exclusion table, one for each record that should disappear. The only place I run that from is from clicking the exclude button. So somehow the bug would have to either click that button or otherwise run that code for each of the remaining records on the CSS list. I can’t think of a mechanism that would do that.
No further info was provided.
Log
- 2022-06-22 Discussed at TASK meeting, doesn't seem to be a problem any longer; setting to "resolved bug" to keep history in case this comes back up.
- 2022-04-21 A bunch of similar errors showed up over edits over the last few days. Hopefully fixing those will have fixed this as well. Those errors were showing up in places that had not been edited, making me wonder if an Office update brought some of them up. The problem might be fixed now, so let me know if it happens again for sure.
- 2022-03-13 FIrst reported this was occasionally happening on the S4 and S5 laptops.