Question Re: How to separate the string for a query column custom... in Enterprise Resource Planning Q&A

How to separate the string for a query column custom name into two lines?

IDimitrov — Mon, 12 May 2025 09:55:53 GMT

Hello,

I have this working simple example query in SAP Business One, which calls for all entries for a parameter (document number from all Sales Order documents) to be displayed in a column, which is then renamed:

SELECT T0."DocNum" AS "Document Number" FROM ORDR T0

Which displays a standard table with all the document numbers separated in rows for Sales Orders in a single column named "Document Number".

My question is: how do I split the custom header string "Document Number" into two lines, so it reads

"Document

Number"

as the column name in the query result?

Re: How to separate the string for a query column custom name into two lines?

Felipe_Lima — Mon, 12 May 2025 11:56:47 GMT

Hi. Not sure if I got it. Do you want to have "Document" as header and "Number" as the first query result?

Re: How to separate the string for a query column custom name into two lines?

IDimitrov — Mon, 12 May 2025 12:13:17 GMT

@Felipe_Lima

No. I want only the title to be displayed in two lines without that affecting the results. Only the column title which is changed to this string to appear on 2 (or more) lines. So if it's a long name the whole column doesn't auto-format to immediately take up half the screen because of that long name.

to become:

Re: How to separate the string for a query column custom...

Felipe_Lima — Mon, 12 May 2025 13:08:59 GMT

Hi @IDimitrov ,

I'm afraid this is not achievable within SAP, as it seems to be a UI limitation.

If you have the result of a query displayed somewhere else, where HTML is accepted (like Crystal Reports), I think you might be able to use line break tags to achieve that (<br>).

BR,
Felipe

Re: How to separate the string for a query column custom...

IDimitrov — Mon, 12 May 2025 13:49:04 GMT

Thank you. A rather disappointing lack of a very common sought after feature, but at least you're saving me another several hours of searching + trial&error as a novice with SQL.