I have a request that the Description filed on the Sales invoice be fully viewable when looking at the Sales Invoice Screen .
At present if you clone an Invoice and change details (if required) the end of the description field can often only be seen by scrolling to the right ( in this business the month of a recurring invoice is always at the end of the Description is one example of why the field should be seen in full.
At present it is too easy to not remember you have changed everything else and not the description field and so the new invoice can have an error in wording and create confusion ( apart from being very embarrassing ).
Is it possible to have this field be made to show in full? and possibly this is true for all types of forms eg purchases, quotes etc?
I know it is a take more care type of thing , but would be very helpful if this small change could be done.
It sounds like you are using a reasonably small screen resolution. Could you post a screenshot?
My recommendation, if you are using Cloud or Server Edition, is to try zooming out. Use Ctrl+minus / Cmd+minus (Windows / macOS) while viewing a web page to zoom out.
@hayz, please confirm that you are referring to the summary-level Description field just below the billing address. The line-item Description fields already expand to show their full content.
Just as way of clarification, it is only on the screen the field is too small or needs to wrap because once it is viewed you can see it as the field expands on the printed copy to full page width but at time of creating the document , the summary field can hide most of the description and that is the part I am asking if could be changed , as there is always risk you will not see you need to change something in the summary description before sending the Invoice to customer when using the clone invoice option.
Simple: the summary-level Description field on transaction forms doesn’t wrap text and expand. Instead, you have to scroll within the field to see all text once it exceeds the default width.
Thank you for making it simpler to grasp the reason for request , it just seems a very useful and helpful idea if descriptions always exceed the default width, mostly when cloning invoice is where the need is highlighted to see everything in that field as you can end up with a wrong descripton say December when it is now for January period for example ( see original post ).
I still don’t understand the issue. When you are viewing the invoice (View button), whatever is entered in the field will show in full.
If you are editing the invoice, then yes - the field is fixed size and having too much text in the field won’t show entire text but this is how text fields are implemented across entire program. The size of the field is usually to indicate how much text is recommended to enter. If you generally need to enter a lot more text, then that is an indication that perhaps you should create a custom field.
Why do you enter so much text in Description field on invoice level in the first place? The text on invoice will show in large font and in bold. It’s not a field which should contain a lot of text in the first place. If you need a lot of text, why not create a custom field?
Actually, not, @lubos . The Description field for individual line items will grow and wrap text on the Edit screen if you put in a lot of text. Also, line-item custom fields will do the same thing.
I should have made distinction between multi-line fields and single-line fields. It’s true multi-line fields will expand. But summary-level description field is single-line field and it’s on purpose. The text on invoice from that field is large and bold. It’s not a field where long text should be entered in the first place.
Summary-level description field could be converted to multi-line field but then we would need to de-emphasize the style because current invoice layout assumes it will be short text (that’s why the font is large and bold).
You’re the designer/developer. Your explanation about layout makes sense to me, and I’ve never found this to be a problem. I only put it into Ideas originally because I thought it would be an easy change.