Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Show Next Error does not work in tabbed layout with AutoComplete



When there are multiple errors on a page, Show Next Error is displayed. Clicking Show Next Error should set the focus on first input containing the error and allow the user to click through to the next error field. Instead, sometimes it highlights no field or skips a field. If a user clicks an input, Show Next Error starts working again.

Error Messages

Not applicable

Steps to Reproduce

  1. In a Section, add an AutoComplete control, source it to a Declare Page, and always make it required. 
  2. Select a Property that belongs to the Declare Page for searching and set the same property to a Property of Work class.
  3. Add a Text Input and refer to the Work class property of Step 2. Also make it required. 
  4. In another Section, drag a Layout Group of type Default/Tab.
  5. Drag a Dynamic Layout in the Layout Group and refer to the Section created in Step 1. 
  6. Refer to the Section created in Step 4 in a flow and run the flow to create the case.
  7. In a new case, click Submit to keep both fields untouched and blank. The form generates the  Show Next Error button because multiple errors are present.
  8. Click Show Next Error and see that the focus gets stuck on the AutoComplete control.

Root Cause

Show Next Error and Error functionality does not work as expected in tabbed layout groups where AutoComplete is present. Show Next Error does not focus on the correct element when users click the Show Next Error button. This happens because Show Next Error focuses on the element whose CSS property display is set to None.


Apply HFix-30720. 


Suggest Edit

Published December 17, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us