Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Murari Sreenivasulu (MurariSreenivasulu)
Accenture

Accenture
IN
MurariSreenivasulu Member since 2020 7 posts
Accenture
Posted: May 17, 2022
Last activity: May 18, 2022
Posted: 17 May 2022 1:36 EDT
Last activity: 18 May 2022 6:51 EDT
Closed

Column heading and column value is not aligning properly.

https://collaborate.pega.com/question/column-alignment-issue-table-layout-progressive-pagination

 

 

Same issue happening in 8.5.6.

How to Reslove issue.

***Edited by Moderator: Pooja Gadige to move from Pega Academy to Product, add capability tag***
To see attachments, please log in.
Pega Platform
User Experience

Posted: 2 years ago
Posted: 17 May 2022 7:22 EDT
Marije Schillern (MarijeSchillern)
MOD
Senior Knowledge Management Specialist
Pegasystems Inc.
GB

@MurariSreenivasulu  can you confirm  you applied the settings as per the article you quoted?

"There is a setting called "Align column heading with column data" in the properties panel of every row heading."

Can you test and confirm how it looks in the UI Gallery behaviour?

Are you using Theme Cosmos?

Please provide the screenshots illustrating symptoms and the  configuration

Please include details such as Default style of Grid,  Responsiveness checkbox etc.

Are you using a section with multiple dynamic layout with each dynamic layout containing  tables?  If so what is the display if you move the tables out of dynamic layout or section include the tables into the main section?

 

To see attachments, please log in.
Posted: 2 years ago
Posted: 18 May 2022 6:51 EDT
Marije Schillern (MarijeSchillern)
MOD
Senior Knowledge Management Specialist
Pegasystems Inc.
GB

@MurariSreenivasulu

I found some previous scenarios where the behaviour sounds similar (BUG-304989 Alignment Issue in Repeatgrid layout with Progressive Pagination) but was unable to find any current suggested workarounds.

Progressively paginated grids use the freeze header option by default, which makes use of two HTML tables (one for the fixed header, another for the data / body of the table). We use JavaScript to keep the column widths of these two tables in sync. However, if there are not enough space, browser takes over and decides the column widths (as table-layout: auto is used here).

If you do not use progressive pagination, a single table is used and the whole JavaScript width calculation is avoided.

This is a "known" issue with progressively paginated grids logged under BUG-515780 but regarded as working as designed.  Can you please confirm whether making the changes suggested here makes a difference?. 

It sounds like you need to log a support incident for this if you require further help  . 

Please can you provide the INC id here so that we can help track it?

To see attachments, please log in.

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

Pega Collaboration Center 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