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

Search Text field pops out of the Filter overlay in Grids

SA-23515

Summary



'Search Text' textbox in length exceeds beyond in filter overlay in repeating grid.

Error Messages



No error message, the 'Search Text' textbox exceeds the width of the filter over lay, appears on Repeating grids.

Steps to Reproduce



1. Add a Repeating Grid.
2. Populate grid with some values.
3. Try filtering on the grid.

Root Cause



A software use or operation error User has modified the Default format-Dynamic layout style Label settings - Label position from top to left in their application skin
The GridFilterRangeFields section (Final rule) renders the filter section, the search text field is in the dynamic layout which uses the Default format. Hence the label and text box render in a single line and also the field has a fixed width of 196px is causing it to exceed the filter area.

Resolution



Perform the following local-change:

 If the change must be applied across application, add the code snippet in UserWorkForm rule.
[OR]
 Add for some areas, then wherever grid is used, in that section drop a non-auto generated section with the code snippet.

Code Snippet:
<style>
div[node_name="pzGridFilterRangeFields"] .content-inner{
display:inline !important;
}
 
div[node_name="pzGridFilterRangeFields"] .content-inner > label{
width:25% !important;
}
 
div[node_name="pzGridFilterRangeFields"] .content-inner > div input{
width:85% !important;
}
</style>

Suggest Edit

Published May 23, 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