Skip to main content
Solved

Report Designer: CanGrow Not Working for Text Box

  • February 27, 2025
  • 5 replies
  • 54 views
S
Freshman I

Hi, 

I have a field to display PO#, and I’m trying to make its size dynamic, but despite trying all possible properties, it still only displays as much as fits in the original field size.

I tried CanGrow first, then also ticked WordWrap, CanSplit, and Multiline, and as a last attempt, I also ticked CanShrink—none of them worked.

The Report Designer version matches the Acumatica version, and the text field is not inside any other panel.

I know I can manually increase the field size, but I’m trying to understand if these properties are actually functional. Any insights?

Thanks!

 

Best answer by BenjaminCrisman

​@smajida Are you printing the report in PDF format or HTML? the CanGrow/CanShrink functions don’t really work with PDF, so HTML would be preferred. If you are using PDF you may need to make the field as big as the largest value to populate the field so that it will be sure to get it all, then if it’s at the bottom of the section it is supposed to appear in you can tuck the next section up over part of the field and I believe it should still work to hide the space if it isn’t used. Might help to see the report output also

View original
    Did this topic help you find an answer to your question?

    Samvel Petrosov
    Jr Varsity II
    Forum|alt.badge.img+5

    Are you trying to get it increased in width (horizontally) or height (vertically)?

    As far as I know, CanGrow automatically adjusts the field height (vertically).

    Samvel Petrosov | www.iigservices.com | https://www.linkedin.com/in/samvel-petrosov-096880107/
    Chris Hackett
    1 person likes this
    • Chris Hackett
      Chris Hackett
    S
    Freshman I
    • smajida
    • Freshman I
    • February 27, 2025

    ​@Samvel Petrosov , my first attempt (ticked CanGrow) was to increase the width, that didn’t work, and the second attempt (ticked WordWrap, CanSplit, and Multiline) was to increase the height. 
    it would be nicer to display the field in one line but if that is not possible, displaying in more lines is acceptable. 

    Samvel Petrosov
    Jr Varsity II
    Forum|alt.badge.img+5
    smajida wrote:

    ​@Samvel Petrosov , my first attempt (ticked CanGrow) was to increase the width, that didn’t work, and the second attempt (ticked WordWrap, CanSplit, and Multiline) was to increase the height. 
    it would be nicer to display the field in one line but if that is not possible, displaying in more lines is acceptable. 

    Usually I try to set the width to what the layout allows me to use for the field, then I configure the aligning of the text to be “left” in this example, so that the data of the field is always displayed from the beginning of the field. Then I set the CanGrow to true, so that it pushes it down to the next line in the case the data in the field is longer than the width. CanSplit makes sense in the scenario where the data is expected to be very long and there may be a need to split the control between multiple pages. I usually leave the WordWrap with the default value (true).

    Samvel Petrosov | www.iigservices.com | https://www.linkedin.com/in/samvel-petrosov-096880107/
    Chris Hackett
    1 person likes this
    • Chris Hackett
      Chris Hackett
    S
    Freshman I
    • smajida
    • Freshman I
    • February 27, 2025
    Samvel Petrosov wrote:
    smajida wrote:

    ​@Samvel Petrosov , my first attempt (ticked CanGrow) was to increase the width, that didn’t work, and the second attempt (ticked WordWrap, CanSplit, and Multiline) was to increase the height. 
    it would be nicer to display the field in one line but if that is not possible, displaying in more lines is acceptable. 

    Usually I try to set the width to what the layout allows me to use for the field, then I configure the aligning of the text to be “left” in this example, so that the data of the field is always displayed from the beginning of the field. Then I set the CanGrow to true, so that it pushes it down to the next line in the case the data in the field is longer than the width. CanSplit makes sense in the scenario where the data is expected to be very long and there may be a need to split the control between multiple pages. I usually leave the WordWrap with the default value (true).

    Thanks, Samvel. That’s the solution I used, but I was trying to understand how these properties work. Is there a bug preventing the function from working, or is there something I missed?

    This is an option I always use in other report designer tools I work with.

    BenjaminCrisman
    Acumatica Employee
    Forum|alt.badge.img+4

    ​@smajida Are you printing the report in PDF format or HTML? the CanGrow/CanShrink functions don’t really work with PDF, so HTML would be preferred. If you are using PDF you may need to make the field as big as the largest value to populate the field so that it will be sure to get it all, then if it’s at the bottom of the section it is supposed to appear in you can tuck the next section up over part of the field and I believe it should still work to hide the space if it isn’t used. Might help to see the report output also

    Chris Hackett
    S
    2 people like this
    • Chris Hackett
      Chris Hackett
    • S
      smajida

    Reply


    Most helpful members this week

    Terms & ConditionsCookie settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings
    About Acumatica ERP system
    Acumatica Cloud ERP provides the best business management solution for transforming your company to thrive in the new digital economy. Built on a future-proof platform with open architecture for rapid integrations, scalability, and ease of use, Acumatica delivers unparalleled value to small and midmarket organizations. Connected Business. Delivered.
    © 2008 — 2024  Acumatica, Inc. All rights reserved