# Alarm Journal Scroll up/down

**URL:** <https://forum.inductiveautomation.com/t/alarm-journal-scroll-up-down/111211>\
**Category:** Ignition\
**Created:** [October 6, 2025, 3:52pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-scroll-up-down/111211 "2025-10-06T15:52:59Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [October 6, 2025, 5:36pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-scroll-up-down/111211/2 "2025-10-06T17:36:29Z")

</div>

You've got three sets of up/down buttons - the code behind them is going to be different either way.

Searching these forums for `scroll alarm status table #vision` ([Search results for 'scroll alarm status table #vision order:likes' - Inductive Automation Forum](https://forum.inductiveautomation.com/search?q=scroll%20alarm%20status%20table%20%23vision%20order%3Alikes)) gets a variety of hits, though this is the most useful:  
[Alarm status table: scrollbar width and return to top in marquee mode [vision] - #2 by justinedwards.jle](https://forum.inductiveautomation.com/t/alarm-status-table-scrollbar-width-and-return-to-top-in-marquee-mode-vision/67653/2)

The basic idea is the same, though - reach for the internal Java swing objects and call their internal methods to scroll.

---

_[View the full topic](https://forum.inductiveautomation.com/t/alarm-journal-scroll-up-down/111211)._