# Pressing tab-key in a decision table jumps two cells (sometimes)

**URL:** <https://forums.pega.com/t/pressing-tab-key-in-a-decision-table-jumps-two-cells-sometimes/5101>\
**Category:** General\
**Tags:** 8-8, pega-academy\
**Created:** [September 28, 2023, 1:58pm UTC](https://forums.pega.com/t/pressing-tab-key-in-a-decision-table-jumps-two-cells-sometimes/5101 "2023-09-28T13:58:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![AxelB16903925](https://avatars.discourse-cdn.com/v4/letter/a/e95f7d/32.png) [@AxelB16903925](https://forums.pega.com/u/AxelB16903925)\
**Post date:** [September 28, 2023, 1:58pm UTC](https://forums.pega.com/t/pressing-tab-key-in-a-decision-table-jumps-two-cells-sometimes/5101/1 "2023-09-28T13:58:19Z")

</div>

Hello, I am following the Challenge: [Automating decisions with decision tables | Pega Academy](https://academy.pega.com/challenge/automating-decisions-decision-tables/v6/in/36626)

I noticed in the Pega instance created for this challenge that pressing the tab-key sometimes skips two columns. In these instances. Another thing on this is that typing a value and pressing the tab-key cleares the typed value from the cell. Is this a know bug that decsion tables are problematic with keyboard inputs?

It’s not consistent but often standing in the marked **0** and pressing tab skips to the 200 and doesn’t stop on the 0.0275. (see attachment)

 ![Annotation 2023-09-28 154937.png](https://pega1.discourse-cdn.com/pega/original/2X/1/17e3d538920204b440d8369bdc7c5c5fe52ed455.png)

 ![Annotation 2023-09-28 154937.png](https://pega1.discourse-cdn.com/pega/original/2X/1/17e3d538920204b440d8369bdc7c5c5fe52ed455.png)

---

<div class="post-metadata">

**Author:** ![Sairohith](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/sairohith/32/23362_2.png) [@Sairohith](https://forums.pega.com/u/Sairohith)\
**Post date:** [April 13, 2026, 4:48am UTC](https://forums.pega.com/t/pressing-tab-key-in-a-decision-table-jumps-two-cells-sometimes/5101/2 "2026-04-13T04:48:07Z")

</div>

This usually happens because the decision table editor does not reliably save the value when you press Tab directly. The clear fix is to enter the value and press Enter first so Pega commits the cell update. After that, move to the next cell instead of using Tab as the save action. When you use Tab before the value is committed, Pega can skip a cell or drop the value you just typed. So the issue is with how the editor handles keyboard focus, not with your decision logic. Using Enter to save the cell first avoids the jump and keeps the value correctly.