Use PDIs? Take our 5-minute survey to help shape the PDI roadmap.

Reference field autocomplete dropdown options not highlighting on hover in PROD

amcintyre
Giga Expert

Hello,

 

We are seeing an issue in our PROD instance where some reference field autocomplete dropdown options are not visually highlighting when hovering over them.

 

Example behavior:

 

When typing into a reference field, the autocomplete dropdown displays matching records. The values are still selectable, but when hovering over the dropdown choices, the row does not visually highlight.

 

A few details:

  • This is only happening in PROD
  • The same field works as expected in TEST and DEV
  • The affected reference field configuration appears to match between PROD and TEST
  • The lookup popup opened from the magnifying glass works normally
  • It does not appear to affect every reference field
  • We tested in InPrivate/Incognito and the issue still occurs
  • We tested with another user and the issue still occurs

Has anyone seen this behavior before? Any suggestions on what to check next would be appreciated.

2 ACCEPTED SOLUTIONS

Support has confirmed this issue was identified as PRB1926469 and fixed in Australia Patch 4.

View solution in original post

Hello @SteveR781314613 — Zurich Patch 10 Hotfix 3 fixed this issue

View solution in original post

15 REPLIES 15

@ismaelwismann - Same thing on our end.

@NikethK We tested it on the Assignment Group and we are still experiencing the same issue.

I am not sure if this helps anyone. But I did see that there is a difference in the HTML layout of the assignment group (not working) and the assigned to (working) dropdowns. But I thought I will attach the screenshots anyways

CyrusM
Tera Expert

I have identified the cause for the issue.
The HTML used to store the options for AJAXReferenceCompleter uses a <div>, while AJAXTableCompleter uses a <tr>.

But the CSS selector in css_includes_polarisberg.cssx used to do the highlighting is ".ac_dropdown tr[role=option].ac_highlight". So it doesn't target the <div>.

Support has confirmed this issue was identified as PRB1926469 and fixed in Australia Patch 4.

Are you aware if it’s fixed in any Zurich patches?