Preserving leading spaces in a report column.

Hi
I have a report region derived from a sql query. One of the columns in the database can contain leading spaces. However, my report column is not displaying the leading spaces.
These are the things I've tried:
On the Column Attributes page, under Column Formatting, I have entered CSS Class = "code".
Also on the Column Attributes page, under Tabular Form Element, I have selected Display As = Text Field and I have entered Element Attributes = class="code" READONLY.
However, the report does not look nice. The column looks too different from the other columns (disabled text field vs standard report columns). Can anyone suggest a better fix for this problem?
Thanks.
Jo

Here's 3 ways to do it:
http://htmldb.oracle.com/pls/otn/f?p=25262:1
CSS WS - using the CSS white-space: pre property (here in the Column Formatting/CSS Style property, or it could be done with a class and an external style sheet); doesn't work in Win IE 6 :-(
HTML Exp - wrapped the column in a <pre> tag in the report SQL [doing this in the Column Formatting/HTML Expression property didn't work - it stripped the spaces. Anyone know if this expected?]. Also had to add a .t4data pre { display: inline; } style rule to the page to remove unwanted default formatting.
&nbsp; - replaced the spaces in the column in the report SQL with HTML non-breaking spaces: replace(..., ' ', '&nbsp;')
Given the Win IE restriction on the CSS approach, the last one looks like the simplest solution.

Similar Messages

Cuts off leading zeros in a report column when "Download to Excel" function

Hello
When a text column contains leading zeros for example "000250" the download to Excel stores the string as "250" in the spreadsheet. I am using a column which is a string.(varchar)
Can somebody suggest me , how to go ahead with it
Thanks
Edited by: user647228 on Sep 11, 2008 1:40 PM
Edited by: user647228 on Sep 11, 2008 1:42 PM

(To Vins) Actually, concatenating a space doesn't do it. When the file is downloaded into Excel, the leading space is ignored and it the leading zeroes are still trimmed.
To user647228: A non-space character needs to be concatenated. Regarding what character to append, I would give the following consideration: If the users are content with seeing an added character to the "number," you can append say an underscore "_" and Excel will download the number properly. It's fairly unobtrusive and can be "visually ignored."
If the end user insists on gettin rid of the extra character once the file is downloaded, I would append a character that is rarely, if not never, used in the report. (This ensures or mitigates replacing other instances of the character.) Then you can do a Replace All in Excel to replace the extra character with a single apostrophe. The single apostrophe will be interpreted by Excel to mean "text" and the appearance will change to exactly what is desired.
Note: Replacing the extraneous character with a space for example, will result in the leading zeroes being again lopped off by Excel...

How to add leading spaces to af:table column

Hi,
I'd like to display leading spaces in af:outputText located in table column. Value property is bound to backing bean property, where I add custom leading text.
However, if I add , the & nbsp; text "& nbsp;" is displayed, not rendered by the browser. Any ideas?
Regards
Jernej
Message was edited by:
Jernej Kase
Message was edited by:
Jernej Kase

Hi,
since you didn't mention how you solved it, here is the approach i would have taken
- use skinning to add padding. This way you don't have to mess with the display data
Frank

Displaying leading spaces in a Standard Report Column

Is there a way to display leading spaces in a standard report column in APEX?
I am using the following hierarchy query to left pad the metric title with spaces to indent subordinate records. The problem is that the APEX report truncates the leading spaces when the data is displayed.
I have replaced the spaces with an underscore, however the end users prefers white spaces for readability.
Any help is greatly appreciated.
SELECT
t.group_id,
t.metric_id,
LPAD(' ',(LEVEL - 2)*5,' ') || d.metric_title metric_title,
d.business_unit,
get_name(d.data_owner) data_owner,
d.metric_status,
t.group_sort
FROM tbl_health_metric_groupings t JOIN tbl_health_metric_definition d ON t.metric_id = d.metric_id
WHERE t.group_id != 0
START WITH t.group_id = 0
CONNECT BY t.parent_group_id = PRIOR t.group_id
ORDER SIBLINGS BY t.group_sort, d.metric_title

Thanks Tony your comment got me pointed in the right direction.
LPAD only pads a single character to the left so doing something like LPAD(' ',(LEVEL -2)*5,' ') does not produce the expected results however placing LPAD inside a replace function does...
The following works as expected and places leading spaces at the begining of the metric title based on the hierarchy:
SELECT
t.group_id,
t.metric_id,
replace(LPAD(' ',(LEVEL - 2)*5,' '),' ',' ') || d.metric_title metric_title,
d.business_unit,
get_name(d.data_owner) data_owner,
d.metric_status,
t.group_sort
FROM tbl_health_metric_groupings t JOIN tbl_health_metric_definition d ON t.metric_id = d.metric_id
WHERE t.group_id != 0
START WITH t.group_id = 0
CONNECT BY t.parent_group_id = PRIOR t.group_id
ORDER SIBLINGS BY t.group_sort, d.metric_title

Requesting for your kind help...(want to preserve Leading & trailing spaces)

Hello Team, Can you please help in the following issue: I am trying to preserve white space(leading and trailing L&T) as is on the User Interface. We have built our UI using Flex 3.0 SDK. From Java side, I am able to carry the value with L&T spaces till the call goes to Flex .mxml and here response object assigning as var metaConfig:XML = event.result as XML; But here L&T spaces are not visible along with value of ID. I used to see it by using Alert.show(event.result.toString()); Flex Output is as: <allScalarMetadataFields> <id>TEST</id> <name>test name</name> . But from java[in Servlet/in service] side I can see the output as: <allScalarMetadataFields> <id> TEST </id> <name> test name </name> . Java(Servlet) code is as follows: OutputStream writer = response.getOutputStream(); OutputStreamWriter outputStreamWriter = new OutputStreamWriter(writer,"UTF-8"); JAXBContext context = JAXBContext.newInstance(object.getClass(), object.getClass()); Marshaller m = context.createMarshaller(); m.marshal(object, writer); .Here marshal follow a standard structure for XML to map it into writer same as what Flex XML follows..... Note, there is no any other issue/fault with Flex and java except this white spaces. Flex .mxml code is as: protected var _fieldXml:XML; public function MetadataFieldWrapper(xml:XML = null) { if (xml == null) { xml = <allScalarMetadataFields xml:space="preserve"> <id /> <name /> ... Servlet is getting called as : _webService = new HTTPService(); _webService.url = serviceUrl; _webService.method = "POST"; _webService.resultFormat = "e4x"; _webService.contentType = "application/xml"; . _webService.headers = { "serviceName":serviceName, "serviceMethod":serviceMethod }; _webService.send(param); I want to preserve the L&T spaces along with ID/name . Please help me how to allow these L& T spaces in Flex XML object? Thanks in Advance. Regards, Venu.

In the future this type of question should be asked on flexcoders as it doesn't relate to the development of the Flex SDK. To preserve whitespace look at the documentation for XML.ignoreWhitespace. -- Daniel R. <[email protected]> [http://danielr.neophi.com/] On Wed, Nov 12, 2008 at 8:19 AM, venubwal <[email protected]> wrote: > A new discussion was started by venubwal in > > Developers -- > Requesting for your kind help...(want to preserve Leading & trailing > spaces) > > Hello Team, > > Can you please help in the following issue: > I am trying to preserve white space(leading and trailing L&T) as is on the > User Interface. We have built our UI using Flex 3.0 SDK. > > From Java side, I am able to carry the value with L&T spaces till the call > goes to Flex .mxml and here response object assigning as

FTP Directories with leading space report as empty

FTP Directories with leading space in the name report "550/No such file/directories" when clicked-on. Works fine in IE and Chrome.
== URL of affected sites ==
ftp://index.storsys.ibm.com/tivoli-storage-management/

See [/forum/1/609513]
That is a problem with some IBM servers.
[https://bugzilla.mozilla.org/show_bug.cgi?id=543805 Bug 543805] – FTP list parse error when list returns twice space between date and file name
A workaround is this bookmarklet:
<code>javascript:(function() } alert(j);})();</code>

Leading spaces in excel file from ALV

Hi Guys,
once I export a record from ALV to excel. Some values I think all values that are TYPE I. How can I remove this leading spaces.
Ex: '                                                      100'
something like that.. so if you dont expand the column with you wont see the value 100. I checked the internal table being passed to ALV. It doesnt have leading spaces also in the ALV display. there is no leading spaces. Is there something to to with column width optimization? I need this to optimize the column headers. Thanks in Advance!
Regards,
Michael Nacionales

There is one table CRVS_B with field SFHNR, while creating PRTS I need this field, so I do like this:
select max( SFHNR ) into l_sfhnr
from CRVS_B.
add var to l_sfhnr.
So for example l_sfhnr is equal to 000000000000000010, then after add, it gives me 11, and surprisingly in database 11 is placing position in such a way that last char is empty so it is not 11 but 00000000000000011 ( 17 chars ) as after 11 one empty space, and when it comes next time:
select max( SFHNR ) into l_sfhnr
from CRVS_B.
add var to l_sfhnr.
the value of l_sfhnr is still 000000000000000010......
else try this
Hi
Field_catalog:
Field catalog with field descriptions
2.7.1. Description
Field catalog containing descriptions of the list output fields (usually a subset of the internal output table fields). A field catalog is required for every ALV list output.
The field catalog for the output table is built-up in the caller's coding. The build-up can be completely or partially automated by calling the REUSE_ALV_FIELDCATALOG_MERGE module
See also the documentation of the function module REUSE_ALV_FIELDCATALOG_MERGE.
The minimal field catalog is documented under 'default'. The caller can use the other optional parameters to assign output attributes to a field which differ from the default.
A field catalog need not be built-up and passed explicitly only under the following conditions:
The internal table to be output has the same structure as a Data Dictionary structure which is referred to in the internal table declaration using LIKE or INCLUDE STRUCTURE.
all fields in this structure are to be output
the structure name is passed to ALV in the parameter I_STRUCTURE_NAME.
See also the documentation of the IMPORTING paramter I_STRUCTURE_NAME.
Positioning
row_pos (row position)
value set: 0, 1 - 3
Only relevant if the list output is to be multi-line (two or three lines) by default.
A multi-line list can also be defined by the user interactively if the default list is one-line.
The parameter specifies the relative output line of the column in a multi-line list.
col_pos (column position)
value set: 0, 1 - 60
only relevant when the default relative column positions differ from the field catalog field sequence. The parameter specifies the relative column position of the field in the list output. The column order can be changed interactively by the user. If this parameter is initial for all field catalog entries, columns appear in the field catalog field sequence.
Identification
fieldname (field name)
value set: internal output table field name (required parameter)
Name of the internal output table field which is described by this field catalog entry
tabname (internal output table)
value set: SPACE, internal output table name
This parameter is used in 'manual' field catalog build-up only for hierarchical-sequential lists.
Name of the internal output table which contains the field FIELDCAT-FIELDNAME.
Data Dictionary reference
ref_fieldname (reference field name)
value set: SPACE, Data Dictionary field name
Name of the Data Dictionary field referred to.
This parameter is only used when the internal output table field described by the current field catalog entry has a reference to the Data Dictionary (not a program field), and the field name in the internal output table is different from the name of the field in the Data Dictionary. If the field names are identical, naming the Data Dictionary structure or table in the FIELDCAT-REF_TABNAME parameter is sufficient.
ref_tabname (reference table/structure field name)
value set: SPACE, name of a Data Dictionary structure or table
Structure or table name of the referred Data Dictionary field.
This parameter is only used when the internal output table field described by the current field catalog entry has a Data Dictionary reference (not a program field).
Reference to fields with currency/measurement unit
Each internal output table sum or quantity field whose decimal places are to be formatted appropriately for the unit in the list must follow the convention:
the field is of data type QUAN or CURR (internal type P) (the field must really have this physical data type. Overwriting the physical data type with the parameter FIELDCAT-DATATYPE has no effect)
There is a field in the internal output table which contains the associated unit.
There is also an entry in the field catalog for the unit field.
(If the unit is not to appear as a column in the list, and cannot be interactively displayed as a column, e.g. because it is always unambiguous and is therefore explicitly output by the caller in the list header, the field catalog units field entry can take the parameter FIELDCAT-TECH = 'X'.
The association of a value field to a unit affects the output as follows:
appropriate decimal places display for the unit
an initialized field with a link to a non-initial unit is output as '0' for the unit (if FIELDCAT-NO_ZERO is initial). When this field is summed, this unit affects whether the units are homogeneous.
an initialized field with a link to an initial unit is output as SPACE. When this field is summed, the unit SPACE does not affect the homogeneity of the units.
When non-initial fields with an initial unit are summed, the unit SPACE is considered to be a unit.
Link to currency unit
cfieldname (currency unit field name)
value set: SPACE, output table field name
Only relevant for amount columns with associated unit.
Name of the internal output table field containing the currency unit associated with the amount field FIELDCAT-FIELDNAME. The field in FIELDCAT-CFIELDNAME must have its own field catalog entry.
ctabname (internal currency unit field output table)
value set: SPACE, output table field name
only relevant for hierarchical-sequential lists
Name of the internal output table containing the FIELDCAT-CFIELDNAME field.
Link to measurement unit
qfieldname (measurement unit field name)
value set: SPACE, output table field name
only relevant for quantity columns with unit link.
Name of the internal output table field containing the measurement unit associated with the quantity field FIELDCAT-FIELDNAME.
The field in FIELDCAT-QFIELDNAME must have its own field catalog entry.
qtabname (internal measurement unit field output table)
value set: SPACE, output table field name
only relevant for hierarchical-sequential lists
Name of the internal output table containing the FIELDCAT-QFIELDNAME field.
Column output options
outputlen (column width)
value set: 0 (initial), n
For fields with a Data Dictionary link this parameter can be left initial.
For fields without a Data Dictionary link (program field) the parameter must be given the value of the desired field list output length (column width).
initial = column width is the output length of the referred Data Dictionary field (domain).
n = column width is n characters
key (key column)
value set: SPACE, 'X' 'X' = kex field (key field output in color)
Key fields can not be interactively hidden. Parameter FIELDCAT-NO_OUT must be left initial.
For exceptions see the documentation of the FIELDCAT-KEY_SEL parameter.
key_sel (hideable key column)
value set: SPACE, 'X'
only relevant when FIELDCAT-KEY = 'X'
Key field which can be hidden interactively.
The key column sequence cannot be changed interactively by the user.
The output is controlled by the FIELDCAT-NO_OUT parameter analogously to non-key fields.
no_out (field in field list)
value set: SPACE, 'X' 'X' = field is not displayed in the current list.
The user can interactively choose the field for output from the field list.
The user can display the contents of these fields at line level using the 'Detail' function.
See also the 'Detail screen' documentation of the parameter IS_LAYOUT.
tech (technical field)
value set: SPACE, 'X' 'X' = technical field
Field cannot be output in the list and cannot be displayed interactively.
Field can only be used in the field catalog (not in IT_SORT, ...).
emphasize (highlight columns in color)
value set: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off '1'=on)
'X' = column is colored with the default column highlight color.
'Cxyz' = column is colored with a coded color:
C: Color (coding must begin with C)
x: color number
y: bold
z: inverse
hotspot (column as hotspot)
value set: SPACE, 'X'
'X' = column cells are output as hotspots
fix_column (fix column)
value set: SPACE, 'X'
Not relevant for block lists (output of several lists consecutively)
'X' = column fixed (does not scroll horizontally)
All columns to be fixed must have this flag, starting from the left. If a column without this flag is output, only the columns to the left of this column are fixed. The user can change the column fixing interactively. See also the documentation of the Layout parameter
IS_LAYOUT-NO_KEYFIX of the IMPORTING paramter IS_LAYOUT.
do_sum (sum over column)
value set: SPACE, 'X' 'X' = a sum is to be calculated over this internal output table field.
This function can also be called by the user interactively.
no_sum (sums forbidden)
value set: SPACE, 'X' 'X' = no sum can be calculated over this field, although the data type of the field would allow summing.
input (column ready for input)
Function not available
Format column contents
icon
value set: SPACE, 'X' 'X' = column contents to be output as an icon.
The caller must consider the printability of icons.
symbol
value set: SPACE, 'X' 'X' = column contents are to be output as a symbol.
The internal output table column must be a valid symbol character.
The caller must consider the printability of symbols.
Symbols can usually be printed, but may not always be output correctly, depending on the printer configuration.
just (justification)
value set: SPACE, 'R', 'L', 'C'
Only relevant for fields of data type CHAR or NUMC
' ' = default justification for this data type
'R' = right-justified output
'L' = left-justified output
'C' = centered output
The justification of the column header always follows the justification of the columns. Independent justification of the column neader is not possible.
lzero (leading zeros)
value set: SPACE, 'X'
Only relevant for fields of data type NUMC
ALV outputs NUMC fields right-justified without leading zeros by default.
'X' = output with leading zeros
Note: If a NUMC field is output left-justified or centered by FIELDCAT-JUST, leading zeros are output. If the output of leading zeros is suppressed by a Data Dictionary reference ALPHA conversion exit, the output is always left-justified.
no_sign (no +/- sign) Only relevant for value fields
value set: SPACE, 'X' 'X' = value output without +/ sign
no_zero (suppress zeros) Only relevant for value fields
value set: SPACE, 'X' 'X' = suppress zeros
edit_mask (field formatting)
value set: SPACE, template
template = see documentation of WRITE formatting option USING EDIT MASK template
The output conversion conv can be made by template = '== conv'.
Texts
The following text parameters should be specified for program fields without a Data Dictionary reference. The texts are taken from the Data Dictionary for fields with a Data Dictionary reference. If this is not desired, the text parameters can also be specified. The Data Dictionary texts are then ignored. If the user changes the column width interactively, the column header text with the appropriate length is always used. The interactive function 'Optimize column width' takes account of both the field contents and the column headers: if all field contents are shorter than the shortest column header, the column width depends on the column header.
The 'long field label' is also used in display variant definition, sort, etc. popups.
seltext_l (long field label)
seltext_m (medium field label)
seltext_s (short field label)
reptext_ddic (header)
analogous to the Data element maintenance 'Header'
The specified text is not necessarily output in the list, an optimum among all texts is sought.
ddictxt (specify text)
value set: SPACE, 'L', 'M', 'S'
You can specify with values 'L', 'M', and 'S', the keyword that should always be used as column header. If the column width changes, no attempt is made in this case to find an appropriate header for the new output width.
Parameters for program fields without Data Dictionary reference
see also 'Text' parameters
datatype (data type)
value set: SPACE, Data Dictionary data type (CHAR, NUMC,...)
Only relevant for fields without Data Dictionary reference
Program field data type
ddic_outputlen (external output length)
value set: 0 (initial), n
Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.
Prerequisites:
FIELDCAT-EDIT_MASK = '==conv'
see also the documentation of the parameter FIELDCAT-EDIT_MASK
FIELDCAT-INTLEN = n
see also the documentation of the parameter FIELDCAT-INTLEN
n = external format field output length
The column width FIELDCAT-OUTPUTLEN need not be the same as the external format output length (FIELDCAT-DDIC_OUTPUTLEN).
intlen (internal output length)
value set: 0 (initial), n
Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.
Prerequisites:
FIELDCAT-EDIT_MASK = '==conv'
see also the documentation of the parameter FIELDCAT-EDIT_MASK
FIELDCAT-DDIC_OUTPUTLEN = n
see also the documentation of the parameter FIELDCAT-DDIC_OUTPUTLEN
n = internal format field output length
rollname (data element)
value set: SPACE, Data Dictionary data element name
F1 help can be provided for a program field without a Data Dictionary reference, or F1 help which differs from the Data Dictionary help can be provided for a field with a Data Dictionary reference, using this parameter.
When F1 help is called for this field, the documentation of the specified data element is displayed.
If the FIELDCAT-ROLLNAME is initial for fields with a Data Dictionary reference, the documentation of the data element of the referred Data Dictionary field is output.
Others
sp_group (field group key)
value set: SPACE, CHAR(1)
Field group key.
Keys are assigned to group names in the IT_SPECIAL_GROUPS parameter (see also the documentation of the parameter IT_SPECIAL_GROUPS).
When such an assignment is made in the field catalog and in IT_SPECIAL_GROUPS, the fields are grouped correspondingly in the display variant popup.
reprep (Report/Report interface selection criterion)
value set: SPACE, 'X'
Prerequisites:
The system contains the Report/Report interface (function group RSTI, table TRSTI)
Parameter LAYOUT-REPREP = 'X'
(see also the documentation of the parameter LAYOUT-REPREP of the IMPORTING parameter IS_LAYOUT )
'X' = When the Report/Report interface is called, the value of this field is passed in the selected interface start record as a selection criterion.
2.7.2. Default
The following entries are usually sufficient for internal table fields with a reference to a field defined in the Data Dictionary :
fieldname
ref_tabname
Notes:
ALV gets the remaining information from the Data Dictionary.
If no relative column position (COL_POS) is specified, the fields are output in the list in the order in which they were added to the field catalog.
REF_FIELDNAME need only be specifid when the name of the internal table field differs from the name of the referred Data Dictionary field.
Information which is explicitly entered in the field catalog is not overwritten by information from the Data Dictionary.
Priority rule:
Entries in the field catalog have priority over differing entries in the Data Dictionary.
The following entries are usually sufficient for internal table fields without a reference to the Data Dictionary (program fields):
fieldname
outputlen
datatype
seltext_s
seltext_m
seltext_l
Notes:
F1 help can be provided for program fields by assigning a data element to the parameter ROLLNAME.
If the parameters SELTEXT_S, SELTEXT_M, SELTEXT_L, and REPTEXT_DDIC contain appropriate field labels, the program field column headers are also adjusted appropriately when the column width changes.
B. REUSE_ALV_FIELDCATALOG_MERGE : This function module is used to populate a fieldcatalog which is essential to display the data in ALV. If the output data is from a single dictionary table and all the columns are selected, then we need not exclusively create the field catalog. Its enough to mention the table name as a parameter(I_structure name) in the REUSE_ALV_LIST_DISPLAY. But in other cases we need to create it.
The Important Parameters are :
I. Export :
i. I_program_name : report id
ii. I_internal_tabname : the internal output table
iii. I_inclname : include or the report name where all the dynamic forms are handled.
II Changing
ct_fieldcat : an internal table with the type SLIS_T_FIELDCAT_ALV which is
declared in the type pool SLIS.
Reward points if useful
Regards
Anji
Vijayendra Rao
Posts: 1,699
Questions: 28
Registered: 9/14/04
Forum points: 3,018
Re: ALV
Posted: May 14, 2007 8:29 PM    in response to: kotireddy       Reply
Hi,
Field catalog defines the attributes and specifies the technical details of the columns displayed in an ALV output.
You can check the following thread to see how to build a field catalog and how to work with ALV.
Message was edited by:
        Karthikeyan Pandurangan

Preserve leading zeroes?

All,
I created an interactive report, where one of the columns (type: string) periodically has data that "looks" numeric. That is, the column will contain six digits, like "123456" or "001233". The column displays fine--until we save the report as a CSV. The CSV file looks like this:
"123456","other columns"...
"001233","more data"...Excel, in its infinite "wisdom", sees the "001233" and decides that it's really a number--1,233. Which is horribly wrong, and rather annoying to me (and my users). If I go through the data import wizard, I can "force" Excel to see the column as text, but asking my users to remember to do that every time is going to be a losing battle. Is there any way around this?
Thanks,
-David

have you looked at this article?
What I would do myself is have it be tab delimited, not use double quotes around fields (or does apex do that?) and
like they suggest, output a space in front of columns with leading zeros. But it all depends on what exactly you have in
those columns e.g. if people managed to get carriage returns in them (boo! :-)
PS I was using excel 2007).
http://support.microsoft.com/kb/214233
Avoiding Automatic Number Formatting
If you want to type a value such as 10e5, 1 p, or 1-2, and you do not want the value to be converted to a built-in number format, type the number as a text value. To type a number as a text value, use any of the appropriate methods below.
Method 1
Place a space at the beginning of the entry.
NOTE: This method does not work if the entry resembles a number formatted in scientific notation. For example, typing 1e9 results in a scientific number.
Method 2
   1. Choose Format Cells
   2. Click the Number tab.
   3. Click Text, and then click OK.
This method allows you to type data in the selected cells as text. You must perform these steps before you type the numbers in the cells.
Method 3
Precede the entry with an apostrophe. For example, type the following:
'1 p

How to display data in interactive report column without colons (:)

Dear Apex gurus,
I'm a newbie and have just created an Apex application from a spreadsheet. I've created a named list of values and used it in a checkbox against a field in the default page 3 Create form.
When I've selected multiple values in my check box in the form, the data in the interactive report appears as one line with colons separating the selected values like this: Dog:Cat:Bird
What I would like is to have the data appear in the interactive report column as a multi-line list like this:
Dog
Cat
Bird
I can work around this by modifying the SQL code in the Region Source of the Region Definition of the report (Default Page 1 interactive report) to replace the colons with 
SELECT replace("PETS_CHOSEN",':',' ') "PETS_CHOSEN", FROM "MYAPP" Note: this doesn't format properly in the posting. I replace the colon with a html br
This works, but seems to be a hack to me. I am guessing that I've missed a simple option setting somewhere, but I can't find it.
The other problem with this solution is that when I export the report to Excel, what is exported is Dog Cat Bird, which is seems worse than colons.
Thanks,
- Morgan
Edited by: mnrussel on 16-Feb-2009 04:13

Hi Morgan,
I think you have at least two choices:
1 - Replace the colons with ', ' (comma and space) - sort of reasonable on screen and in an export
2 - Create a second page that has the same report but uses the "export: csv" template. Create a manual link to this page to replace the standard Export link. When such report pages are requested, they download immediately instead of displaying. You can, therefore, use commas in this one and tags in the on-screen report version
Andy
ps - To display tags in a post, use &lt; for < and &gt; for >

Assigning a literal space to a report cell

Hi
I want a report column cell to be assigned a specific background colour depending on the value of another column. I can get conditional formatting to work fine by conditionally setting background and foreground colour in the SELECT statement, but what I really want is to use a dummy column as a means to conditionally display a 'bar' of colour as a red / amber / green indicator for the row.
I believe that I have to assign a literal space ( ) to the column to do this, but don't know how to do this in SQL via an UPDATE. Any help or ideas appreciated.
Jules

UPDATE your_table
SET your_column = ' ';If your column in your table is a VARCHAR column a value of space will be converted to NULL in an update statement. NULL will be stored in the database. This will not help you.
Could you set your_column in the database table to any value and set the foreground column color to match the background color in the report region? Then you should not see the value on the screen, right?
Mike

APEX CSS - How do I get data in report columns to wrap?

I found information here http://www.orafaq.com/wiki/APEX_FAQ
About How do I get data in report columns to wrap?
This works and another way to do it is by adding the CSS directly into the
Home>Application Builder>Application 137>Page 1>Report Attributes>Column Attributes page
in the Column Formatting area. I added 'white-space:normal' and this works in FF but in
IE it has a different behavior.
In FireFox
testasdgadhad
gadfadgadgadg
adgafhsrgjsgnsfg
nsdfbadfafhafha
dfhadfh
In Internet Explorer
testasdgadhad gadfadgadgadg adgafhsrgjsgnsfg nsdfbadfafhafha dfhadfh
Is there a way to force it so it display in IE the same way that it displays in FF?
The correct display format is FF.
Thanks,
Nestor :)

I have try this because I found it during a search and it makes no difference in IE.
This is what I am using now 'display: block; width: 100px;max-width:100px;white-space:normal'
I also tried 'display:block; width:500px'
If I use the values 'normal' or 'pre' for white-space' it works in FireFox but not in IE, The display block
does not seem to make a difference. It seems that all I need is 'white-space:normal' but again
it does not works on IE.
Thanks,
Nestor :-)

Referencing report columns in the BLOB download link format mask

Hi there,
In a basic report (Apex 4) I have a link to download a BLOB stored in the table. However to save space, instead of using 2 columns, one for the file name and one for the download link, I want to use only one column where the file name is the download link itself.
To do this, I tried using this download link format mask (ATTACH_FILENAME is the report column that contains the file name):
DOWNLOAD:ATTACHMENTS:ATTACH_BLOB:ATTACHMENT_ID::ATTACH_MIME_TYPE:ATTACH_FILENAME:::attachment:#ATTACH_FILENAME#
However it shows #ATTACH_FILENAME# in all rows instead of the actual file name!
I know that using substitution strings (&) works, so is there a way to also reference report columns in this format mask?
Thanks
Luis

Luis, did you finally resolve this? I have the same question.

Blank space in the report detail section

Hi ,
I have data for ten columns and after that i am getting a blank space, so my report is scrolling to right side without any data.How shall i remove the blank space.Any suggestions.For one more i am getting this only at the second page (Detail section)
Regards,
Rajasekar

Thanks James for the reply,but i am not getting it correctly.
I have a year column which is the last column in my detail section.If i don't get any value for that year column then i am not getting these blank space at the right side of my report.If i have value for the year column then i am getting blank space double the times to my report detail section.
Any suggestions
Regards,
Rajasekar

CSS Style (report column attributes) not working

I found the CSS Style settings for a report column only seem to work if using a "Standard Report Column". Since the report is wider than the screen, some columns are wrapping, making the report not-that-nice readable.
Unfortunately I have the need to define some report columns where undesired wrapping occurs as "Display as Text (based on LOV, does not save state)" and tried to avoid wrapping using "white-space:nowrap;" or specifying a fixed width, but it seems I'm out of luck - is there a way around this (other than performing the report query using a huge DECODE clause and setting the column to "Standard Report Column" again, which somewhat renders the LOV useless except for the select list on the data entry form)? This is happening on APEX 3.12.
Furthermore - is this expected behaviour?
Thanks in advance,
Holger

Furthermore - is this expected behaviour?Looks like it, or it is a [long-standing bug|http://forums.oracle.com/forums/thread.jspa?messageID=1126613]. I've tried it (although only have access to APEX 3.0 at present) and none of the CSS class/style/custom attributes from Column Formatting or Tabular Form Element are being applied. If it's not a bug then it should be raised as an enhancement request.
In the meantime you'll need to work round it.
other than performing the report query using a huge DECODE clause Is that necessary due to a static LOV? If it's dynamic based on a table/view then get the look-up value in the query via a join or scalar subquery so you have a Standard Report Column and can use the CSS class/style/custom attributes from Column Formatting.
Alternatively, stick with the Display as Text from LOV and create a custom named column report template using [colgroup/col|http://reference.sitepoint.com/html/colgroup] to specify fixed width columns.

SQL Report columns formatting

Hi Everyone,
I've got a basic report with a column that is a concatenation of other columns (used for break formatting), and I want to give the effect that there are still separate 'columns' in the concatenation. I've tried using CHR(9) and RPAD in the SQL query to add the 'whitespace' but as soon as Apex gets hold of it, the extra spaces are removed and I'm left with only a single space.
It does the same thing when the "Display As" value is changed to either "standard report column", or any of the "Display as text" types.
Any ideas? This is apex 4.0.0
Thanks!

I've got a basic report with a column that is a concatenation of other columns (used for break formatting), and I want to give the effect that there are still separate 'columns' in the concatenation. I've tried using CHR(9) and RPAD in the SQL query to add the 'whitespace' but as soon as Apex gets hold of it, when the browser renders the output in accordance with the HTML spec the extra spaces are removed and I'm left with only a single space.The HTML specification instructs user agents to collapse white space characters, so spaces and ASCII tabs in options will be treated as a single space.
In a standard report use
<li><tt>white-space: pre</tt> in the CSS Style property for a CSS approach
or
<li>The HTML Expression property for a <tt><pre></tt> HTML wrapper (ensuring the Display Text As column attribute is Standard Report Column rather than the default Display as Text (escape special characters) ):
<pre>#COLUMN_NAME#</pre>Better still, create a custom report template using suitable mark-up so that there are "separate columns" in the report.

Preserving leading spaces in a report column.

Similar Messages

Maybe you are looking for