"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 |
|||
| Line 11: | Line 11: | ||
** I haven't had this error, for HSC med and ICU[[User:Lkaita|Lisa Kaita]] 11:33, 2022 April 13 (CDT) | ** I haven't had this error, for HSC med and ICU[[User:Lkaita|Lisa Kaita]] 11:33, 2022 April 13 (CDT) | ||
**I have never encountered this either.[[User:Gthomson2|Gthomson2]] 11:52, 2022 April 13 (CDT) | **I have never encountered this either.[[User:Gthomson2|Gthomson2]] 11:52, 2022 April 13 (CDT) | ||
}} | |||
{{Discuss | | |||
* Still looking for a way to consistently replicate this - if we can find out the steps to replicate this error we can likely fix it. [[User:Ttenbergen|Ttenbergen]] 11:25, 2022 April 14 (CDT) | |||
}} | }} | ||
| Line 20: | Line 24: | ||
*** Did they re-appear after the newest dump this morning, then? [[User:Ttenbergen|Ttenbergen]] 09:57, 2022 April 14 (CDT) | *** Did they re-appear after the newest dump this morning, then? [[User:Ttenbergen|Ttenbergen]] 09:57, 2022 April 14 (CDT) | ||
*** Was working on S4 yesterday; S5 today so will not know until next week. If this is the case I would expect to see admissions dated April 12 or so appear on S4. Thanks, [[User:Ppiche|Pamela Piche]] 10:11, 2022 April 14 (CDT) | *** Was working on S4 yesterday; S5 today so will not know until next week. If this is the case I would expect to see admissions dated April 12 or so appear on S4. Thanks, [[User:Ppiche|Pamela Piche]] 10:11, 2022 April 14 (CDT) | ||
}} | |||
=== 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. | |||
{{Discuss | | |||
* Next time this error happens, if you can remember any of the records that were on CSS and then disappeared (or if you can find one out through EPR), please let me know if they ended up in the exclusion list. [[User:Ttenbergen|Ttenbergen]] 11:25, 2022 April 14 (CDT) | |||
}} | }} | ||
== Log == | == Log == | ||
* 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 11:25, 2022 April 14
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.
|
|
|
|
|
Work-around
The missing CSS records show back up if you close and open the CSS form.
|
|
|
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.
|
|
|
Log
- 2022-03-13 FIrst reported this was occasionally happening on the S4 and S5 laptops.