Skip to main content
Question

Word Wrap on Line Item Descriptions

  • April 9, 2026
  • 2 replies
  • 15 views

sgaspar72
Jr Varsity III
Forum|alt.badge.img+1

A majority of our clients populate the long descriptions on line items they sell with important descriptive information for each line. They need to be able to view this on the screen without having to hover over each line item description. 

Pre-2025R2 we simply used a customization project to toggle the WordWrap for each of those fields allowing all of the text in the field to show and allowing the field to automatically expand to accommodate it. 

After the 2025R2 update we realized that the WordWrap functionality was removed. Our options now are to create a custom CSS file for each page or to create a global customization in C# to change all of the impacted pages for each customer and deployment. 

I’m curious if anyone else has found a more elegant way to manage for this change? 

2 replies

Forum|alt.badge.img
  • Jr Varsity III
  • April 9, 2026

There are many changes in Modern UI that were much easier to handle in Classic UI. I’m currently facing a small issue—earlier, we could enable WordWrap through customization to display full descriptions without hovering, but now it seems to require custom CSS or global C# changes.

 Custom CSS (only workaround)

You can force wrap, but:

Not perfect

May break layout


sgaspar72
Jr Varsity III
Forum|alt.badge.img+1
  • Author
  • Jr Varsity III
  • April 9, 2026

There are many changes in Modern UI that were much easier to handle in Classic UI. I’m currently facing a small issue—earlier, we could enable WordWrap through customization to display full descriptions without hovering, but now it seems to require custom CSS or global C# changes.

 Custom CSS (only workaround)

You can force wrap, but:

Not perfect

May break layout

There are indeed. Because of this most of our clients are choosing to run the classic AI again. Unfortunately some of the changes made (I assume to accommodate new and upcoming features) have significant impact regardless of what UI is chosen. We are relegated to writing new code instead of using the low-code tools provided by Acumatica. We can do it, it’s just a lot more expensive for the client. 

I’m hopeful that someone has figured out some of these issues, but it seems baked into the design.