- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-02-2023 10:09 AM
Hi all -- I have noticed some odd behaviour in my instance and I'm wondering if this is a "servicenowism" or if it is something I can fix myself...
This is in a production instance running Tokyo 9_2a using the "traditional" UI16 interface.
As it seems, if you go to a list view of any table (https://<instance>.service-now.com/nav_to.do?uri=%2Fincident_list.do - for instance) and sort descending on Reference number (or some other unique, sequential, non-date field) and then open the first record on the list, you'll have the "up/down" navigation buttons in the top right of the main record frame. You can navigate through the list, where "down arrow" goes to the next record (sequential, based on the sort done previously) and "up arrow" goes to the previous...normal, intuitive, useful.
HOWEVER - if you further filter the list on a date field (like "opened" or "updated" or "created") such that it only lists records "after" a specified date (right click on date in list and select "show after"), then open a record on the list, the up/down arrows are totally borked.
I can replicate this in multiple browsers and on my PDI (also Tokyo)...and it only seems to affect these buttons when the filter applied contains a condition for "{date field} >= YYYY-MM-DD HH:MM:SS".
If you apply the same logic and filter to "show before", it works as expected (filter condition is "{date field} <= YYYY-MM-DD HH:MM:SS") and the up/down arrow buttons navigate through the list as expected.
I'm thinking this is a made-at-servicenow issue that I'm just discovering for myself, now. I'm not really looking for a solution yet, just looking for validation and/or insight that may help guide my next actions.
Solved! Go to Solution.
- Labels:
-
User Experience and Design
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-02-2023 10:24 AM
I just tested this in my Utah PDI and it works fine there, so this was most likely a bug that got fixed:
You can see the Previous arrow is greyed out there as expected. Unfortunately I don't think this is something you would have access to be able to fix yourself, but you could confirm this with someone in Support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-02-2023 10:24 AM
I just tested this in my Utah PDI and it works fine there, so this was most likely a bug that got fixed:
You can see the Previous arrow is greyed out there as expected. Unfortunately I don't think this is something you would have access to be able to fix yourself, but you could confirm this with someone in Support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-02-2023 11:31 AM - edited ‎08-02-2023 11:34 AM
awesome, thanks!
EDIT -- sorry the issue only happened when you tried to go from record 2 onward either to record 3 or back to record 1...I found that the first down arrow action worked fine. @Mr Anderson
I don't really want to release my PDI and go to Utah just yet....could you please do me a favour and check again on record 2...see if it says "next 3 of 48" and no "-1" on the up arrow...
No worries if not, this was still helpful!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-02-2023 11:56 AM
Yep, still works, and regardless of whether I click the 2nd record straight from the list or use the arrows:
Previous arrow shows 1 as expected.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-02-2023 01:59 PM
Thank you, again!