Most Popular
Recently Added
Recently Updated

UI 5 Troubleshooting and Known Issues

This article documents current known issues with Colleague UI 5


First, make sure you've done all of the "Before You Start" activities in the UI 5 Introduction & Resources article.

If you continue to have the same problem, review the Known Issues below.

If your issue is not listed there, log out of UI, and try the following. They are listed in order of how common an issue it might be, so you can try them one at a time, in case the most common one solves your problem:

  • Clear your browser cache.
  • Make sure javascript is enabled for

If you continue to have issues, send a message to and please be specific about any error messages you might receive, the form ("mnemonic") you were using, the record(s) you were accessing, etc. Screen shots can be very helpful.

Known Issues

General Issues

  • Tabbing through screens too quickly will result in "freezing" or "processing please wait" message. Please do not leave the form. Wait until it returns. Take a screen shot and send it to, and tell us what mnemonic you were on and what you were updating. The system may take 5-15 minutes to return. You can start a new UI 5 session, but do not try to access the record you were working on until the "frozen" screen returns. (This will be fixed in UI 5.4)
  • Hitting Save or Save All from a form without leaving the field you've modified will not save the changes. (This will be fixed in UI 5.4)
  • Ctrl-Alt-D sometimes does not clear the field content.
  • Adding rows to a numbered window sometimes fails. (This will be fixed in UI 5.4)
  • Calendar button does not always work.
  • Ctrl-F9 key functionality not available.
  • Sorting is not available on a grid-type resolution screen. Try switching to card view to sort your results, if possible. (This will be fixed in UI 5.4)
  • Dropdown lists of codes may extend beyond the size of the screen. You may need to resize or "zoom" the UI form in order to see the full dropdown. (This will be fixed in UI 5.4)
  • When in a lookup on a fresh (empty) screen, hitting the tab key to exit the lookup will bring up the lookup again, rather than canceling to the main menu as it did in UI 4.x. (This will be fixed in UI 5.4)
  • If a name is longer than 20 characters, it will be truncated on the context card, with an ellipse at the end ("..."). However, unlike other elements on the context card that get truncated, there is currently no way to hover or click and view the full name. (This will be fixed in UI 5.4)
  • During lookups on any screen, an error message starting with "Invalid context..." may appear. If this happens, please send an email message to and state that you received the "invalid context" error message in UI 5. There is a process IT will need to run, and then you will be asked to log out of UI and log into a new UI session once that is IT process is complete.
  • In multi-valued (aka "windowed") fields, after entering data in a field in a new row, you may be returned to the first row, rather than advancing you to the next row. This typically happens if you click with your mouse in the field, rather than hitting enter to go to the next row.

Issues with Specific Forms

  • Moving between grade fields and entering grades on the following forms can be slow. (This will be fixed on UI 5.4):
    • FGCL
    • MGCL
    • FGRN
    • MGRN
  • Calendar date picker does not work consistently on the following forms:
    • FGRN
  • Exporting to Excel from the first page of results does not work on the following forms:
    • ACBL
  • Using "partial lookup" (i.e. "...") to look up AR Types causes problems on the following forms (This will be fixed on UI 5.4):
    • CADV
    • PPLN
  • BPUM: Using the Delete key to blank out the Qty Accepted field and then clicking ok can result in the "Please wait... Processing... " message appearing for 3-13 minutes before releasing the form back to the user.
  • DOC: After detailing to DPAR and detailing to enter paragraph text, if you enter a line with no spaces that is longer than the allowed width in the paragraph editor screen, saving out will freeze your UI session. This most typically happens if you're working with an HTML email document, and you're entering a URL hyperlink that is very long. If this happens, call someone in EDS to safely end your UI session before closing your browser and logging in again.
  • FGRN: The final and verified grade will not be saved for the last student in the list.
  • PLDT: Under Response Errors, the detail buttons overlap the field. This is a display issue only. The detail buttons still function, and the error status is still visible behind the detail button.
  • REQM will not retain a customized zoom after detailing to line items or approvals.
  • RGUS, RGUD, RGUT: Cannot detail from RGUD to RGUT even by hitting the F2 detail key. (This will be fixed in UI 5.4)
  • SECT: Certain workflows with changing Min/Max/Incr settings for variable credit courses can fail to update the fields without clearly indicating the change was not made. (This will be fixed in UI 5.4)
  • SOFF:
    • If you enter Y in Rebuild Calendar you must hit the enter key before saving from the form. If you hit Save or Save All without first hitting enter, you will unable to override conflicts correctly on SCCR if you need to do so, resulting in an incomplete rebuilding of the calendar schedules records. Note--If you do forget to hit enter before saving and wind up with conflicts on SCCR that need to be overridden, just go back to SOFF again and enter Y to Rebuild Calendar again. (This will be fixed in UI 5.4)
    • If you need to remove meeting times and days from an existing section, it will not allow you to update from the record after rebuilding the calendar. The workaround is to enter Y to rebuild the calendar, press OK to accept the warning message, detail to SESC, press OK in the prompt without entering anything, Save All from SESC and click Update to return to SOFF, and then Save or Save All from SOFF, and press OK to the warning prompt.
  • TMSS: The "Highest Process Date" field has text that says "was on file" overlaying the field, itself. This is only a display annoyance, and the form can be used as normal. (This will be fixed in UI 5.4)

Note: UI 5.4 is scheduled to be live in late fall.

Properties ID: 000260   Views: 145   Updated: 4 hours ago