#COLNUM# #COLUMN_VALUE# in column Template Condition

Hi,
Is it a limitation to use #COLNUM# #COLUMN_VALUE# in column Template Condition?
I specify a column template condition #COLNUM#=3 in the column template condition, but the error
"ERR-1025 Error Processing PLSQL expression #COLNUM#=3" prompt.
Is that a limitation?
Thanks

Hi,
I can use column name in template column condition with no problem, but I want to apply the condition to few fixed columns(more than 10 columns),
I know I can do something in the SQL query of the report, but it will be too tedious.
If only the #COLNUM# etc is usable in template column condition, it will save a lot of job.
Anyone know the reason #COLNUM# not usable in template column condition?
Thanks

Similar Messages

Report template - How to reference COLNUM in the col template condition?

Hi,
I have a query with 4 columns. based on this query I would like to make a report with a row layout that looks something like this:
| column1 value |
| column2 value | column3 value | column4 value |
I created a report template, four column templates: one for column 1, one for the following columns and one for the las column of the report.
My problem is that when I reference *#COLNUM#* like mod(#COLNUM#,4) = 1 in the Column Template condition fields, then I get *'ORA-06550: line 1, column 34: PLS-00103: Encountered the symbol "#" when expecting one of the following: ( ) - +....'*
Is referencing COLNUM not allowed in the Column Template Condition field?
Tamas
Edited by: Tamas Szecsy on Jul 16, 2011 11:33 PM

Tamas Szecsy wrote:
I have a query with 4 columns. based on this query I would like to make a report with a row layout that looks something like this:
{noformat}| column1 value |{noformat}
{noformat}----------------------------------------------------------------{noformat}
{noformat}| column2 value | column3 value | column4 value |{noformat}
I created a report template, four column templates: one for column 1, one for the following columns and one for the las column of the report.For this you need to create a Named Column (row template), not Generic Columns (column template).
Before Rows
<table class="foo">
Row Template 1
<tr>
<td colspan="3">#1#</td>
</tr>
<tr>
<td>#2#</td>
<td>#3#</td>
<td>#4#</td>
</tr>
After Rows
</table>No conditions.
What about table headers?
My problem is that when I reference *#COLNUM#* like mod(#COLNUM#,4) = 1 in the Column Template condition fields, then I get *'ORA-06550: line 1, column 34: PLS-00103: Encountered the symbol "#" when expecting one of the following: ( ) - +....'*
Is referencing COLNUM not allowed in the Column Template Condition field?I suspect not. Only <tt>#ROWNUM#</tt> is mentioned in the online help for Column/Row Template Expressions. <tt>#COLNUM#</tt> is only indicated in the Column/Row Templates themselves.
(Always post sample layouts using \...\ and/or {noformat }...{noformat } tags to preserve formatting/stop Jive from turning it into something else.)

Generic Column Template - Column Template Conditions

Hi,
I have the following sql report snippet (as an example):
select a,b,c,apex_item.checkbox(1,active_flag,DECODE (active_flag, 'Y', 'CHECKED','')) as "Active"
from tableA
Attached to this report, is a report template which I am trying to attach Column Template Conditions as I basically want to display all rows that have an active flag of 'N' as red or leave as default colour but unfortunately I can't seem to get this to work.
I believe my Column Template Expressions are not correct as I have also tried "ACTIVE" = 'N' and still no luck.
I have the following setup within the Generic Column Template, i,e:
Column Template 1 = <td class="t12datavalue"#ALIGNMENT# style="background:red">#COLUMN_VALUE#</td>
Column Template 1 Condition = Use based on PL/SQL Expression
Column Template 1 Expression = '#1' = 'N'
Column Template 1 = <td class="t12datavalue"#ALIGNMENT#>#COLUMN_VALUE#</td>
Column Template 1 Condition = Use based on PL/SQL Expression
Column Template 1 Expression = '#1' <> 'N'
Any ideas what I could be missing?
Thanks,
Tony.

Hi Tony,
I think the issue here might be because the field you are trying to evaluate in the column template is a Check box. I tried this and it worked :-
select a,b,c,apex_item.checkbox(1,active_flag,DECODE (active_flag, 'Y', 'CHECKED','')) as "Active",active_flag
from tableA
In the report attributes set the second active_flag column to not show (i.e. the one that is not the check box).
In the Column Template
Column Template 1 = <td class="t12datavalue"#ALIGNMENT# style="background:red">#COLUMN_VALUE#</td>
Column Template 1 Condition = Use based on PL/SQL Expression
Column Template 1 Expression = '#ACTIVE_FLAG#'='N'
Column Template 1 = <td class="t12datavalue"#ALIGNMENT#>#COLUMN_VALUE#</td>
Column Template 1 Condition = Use based on PL/SQL Expression
Column Template 1 Expression = '#ACTIVE_FLAG#'='Y'
Regards
Paul

Report Template, Column Template, Column Template Condition

I have a template, Standard Revenue from Standard, I have cloned for a Classic report.
Application ###>Shared Componets>Templates>Edit Report Template
Column Template 1 looks like:
<td#ALIGNMENT# headers="#COLUMN_HEADER_NAME#" class="t1data_revenue">#COLUMN_VALUE#</td>
I have set Column Template 1 Condition to:
"Use based on PL/SQL expresiion"
I have tried several expression in "Column Template 1 Expression" - last one is:
case
when #COLNUM# <= 2 then false
when #COLUMN_VALUE# < 0 then true
else false
end case;
I am trying to use the value in "Column Template 2" when to value of the #COLUMN_VALUE# < 0
where "Column Template 2" is :
<td#ALIGNMENT# headers="#COLUMN_HEADER_NAME#" class="t1data_revenue_negative">#COLUMN_VALUE#</td>
I get the following error when I run the page:
ORA-01403: no data found
and
ERR-1025 Error processing PLSQL expression. case when #COLNUM# <= 2 then false when #COLUMN_VALUE# < 0 then true else false end case;
Any help will be appreciated.
thank you,
jwm

Hi,
That's actually easier. See: [http://apex.oracle.com/pls/otn/f?p=267:60]
The SQL for both reports is:
SELECT EMPNO, ENAME, NVL(SAL,0) SAL, NVL(COMM,0) COMM
FROM EMP
ORDER BY EMPNOThe SAL and COMM columns have been formatted using:
999G999G999G999G990D00For the Row Template, the Row Template 1 setting contains an empty space (you have to have something in there otherwise Apex adds back in a default row containing five cells!). The condition for this is:
TO_NUMBER('#COMM#','999G999G999G999G990D00') < 100The template will see the data as a string, so we use the same number format to convert that string back into a number and compare this to 100. If we didn't use formatting on the numbers and we are sure that every row contained a number (hence the use of NVL()), then you could use:
#COMM# < 100Row Template 2 contains the format for the rows that need displaying:
<tr>
<td class="t18Data">#1#</td>
<td class="t18Data">#2#</td>
<td class="t18Data" style="text-align:right">#3#</td>
<td class="t18Data" style="text-align:right">#4#</td>
</tr>and is unconditional.
The only other settings on the Row Template are the Before Rows:
<table class="t18Standard" style="border-collapse:collapse; border:1px solid black;">
<tr>
<th class="t18ReportHeader">Empno</th>
<th class="t18ReportHeader">Ename</th>
<th class="t18ReportHeader" style="text-align:right">Sal</th>
<th class="t18ReportHeader" style="text-align:right">Comm</th>
</tr>and After Rows:
</table>Of course, you will note that the record counters at the bottom still show the number of records in both reports - as the SQL still outputs the same data, this doesn't change.
Andy

Column Template conditions foiled by a single quote

I am using a generic column template and have a few pl/sql conditions to shade different rows like so:
'#1' like '%Total%'This worked fine until an employee's name appeared in the first column with a single quote in his last name (like O'Brien). Well apparently Apex literally takes whatever is in the field and just shoves it in between the single quotes because the single quote is terminating the string as if you were doing this in sql instead of making it a bind variable:
'O'BRIEN' like '%Total%'Which results in this friendly message to the users:
ORA-06550: line 1, column 65: PLS-00103: Encountered the symbol "BRIEN" when expecting one of the following: ) , * & | = - + < / > at in is mod remainder not rem => .. <> or != or ~= >= <= <> and or like LIKE2_ LIKE4_ LIKEC_ as between from using || multiset member SUBMULTISET_
Error ERR-1025 Error processing PLSQL expression. 'O'BRIEN, JOHN P ' like '%Total%' Can someone from the Apex team confirm that this is the issue? I know I could do a replace on the single quote in my sql, but can't figure out how to escape the '#1#' properly so I don't have to do a replace. I also don't really want to use the Carl Backstrom approach of having to code in a class into the sql when these templates work for 99% of what I need to do.
Any ideas?

Dude you rock! I tried about 6 different combos of the q function before I got frustrated and posted. I had too many quotes in mine I guess but that works perfectly.
Thanks again!

Template Condition based on PL/SQL Expression

Hi everybody!
I need some help in conditional formating. Depending on the value of a column I want to display it with a diffrent background-color.
I copied the template Standard, ALternating Rows to a diffrent name, placed
<td class="t5data" headers="#COLUMN_HEADER_NAME#" #ALIGNMENT# style="background-color:#f00;"> #COLUMN_VALUE# </td>
as template 1 , selected Use Based on PL/SQL Expression and as an expression I used for testing
1=1
As expected all rows are displayed in red.
Now I changed the expression to
'#CHARGE#' ='-'
but it the corresponding rows were not displayed with a red background . Changing to
'#CHARGE#' !='-'
made all rows be red ( such -, too).
Where is my fault?
Thanks for helping
regards
Petra
Edited by: pietja on Dec 9, 2009 11:28 AM

Hi Ben!
Is this what you need?
Column Heading Template <th class="t5ReportHeader" id="#COLUMN_HEADER_NAME#" #ALIGNMENT#>#COLUMN_HEADER#</th> Column Template 1 <td class="t5data" headers="#COLUMN_HEADER_NAME#" #ALIGNMENT# style="background-color:#f00;"> #COLUMN_VALUE# </td> Column Template 1 Condition Use Based on PL/SQL ExpressionColumn Template 1 Expression '#CHARGE#'='-'Column Template 2 <td class="t5data" headers="#COLUMN_HEADER_NAME#" #ALIGNMENT#> #COLUMN_VALUE#</td>Column Template 2 Condition Use for Odd Numbered RowsColumn Template 2 Expression
Column Template 3 <td class="t5dataalt headers="#COLUMN_HEADER_NAME#" #ALIGNMENT#> #COLUMN_VALUE# </td>{code}
Column Template 3 Condition{code} -Select Condition-{code}
Column Template 3 Expression {code}{code}
Regards
Petra

Problems with template condition

Hi,
I would like to set a condition for a report template by the column header content.
I have tried the following statement:
instr(#COLUMN_HEADER#, 'TITLE')>0
and I have got the error message:
"ORA-06550: PLS-00103: Encountered the symbol "#" when expecting one of the following: ( ) - + ..."
Do you have any idea why it doesn't work?
Thx!

In plain english :-) :
I want to create a report with news on the start page of a htmldb application. So I have created a table with 3 columns: DATE, HEADLINE, CONTENT. Now I want to create a template for the layout. Every record in the news table should be showed in the following way:
HEADLINE DATE
CONTENT
My idea was to create 3 conditional templates for every column of a record depending on the column's name. For example a new table row (<tr>) for the content column etc.
The column template conditions based on PL/SQL expression (e.g. instr(#COLUMN_HEADER#, 'CONTENT')>0) don't work... :-(

Passing #COLUMN_VALUE# as parameter to pl/sql function in column template

Hi all,
I want to color negative amounts in red in sql report using column template.
I created a pl/sql function"isNegativeNum" which returns 1 or -1.
create or replace function isNegativeNum(p_column_value varchar2) return number
as
l_dummy number;
begin
      l_dummy := to_number(p_column_value,'999G999G990D00PR');
      IF l_dummy < 0
         THEN
            RETURN 1;
      else
            return -1;
      END IF;
exception
when others then
   RETURN -1;
end;Below is column template.
Column Template 1
<td class="t3dataalt" #ALIGNMENT#><p color=red>#COLUMN_VALUE#</p></td>Column Template 1 Condition
isNegativeNum('#COLUMN_VALUE#') = -1The issue is #COLUMN_VALUE# value is not being passed to the function, Insert statement in function reveals p_column_value as a string "#COLUMN_VALUE#". When I try without quotes like isNegativeNum(#COLUMN_VALUE#) = -1, I get below error.
ORA-06550: line 1, column 48: PLS-00103: Encountered the symbol "#" when expecting one of the following: ( ) - + case mod new not null others select table avg count current exists max min prior sql stddev sum variance execute multiset the both leading trailing forall merge year month DAY_ hour minute second timezone_hour timezone_minute timezone_region timezone_abbr time timestamp interval date
     Error      ERR-1025 Error processing PLSQL expression. isNegativeNum(#COLUMN_VALUE#) = 1
Any help is appreciated.
Kishore

Hi Kishore,
using #COLUMN_VALUE# would probably not make much sense, because normally a report has multiple columns and not just the numeric column which you want to verify if it's negative. But APEX will fire the template condition for each column, because the report template is a column cell template.
What you can do to make it more generic is to use for example
#CHECK_AMOUNT#
in the template and provide a not displayed column in your SQL statement which contains your value which is named CHECK_AMOUNT. For example:
SELECT NAME
     , BALANCE
     , BALANCE AS CHECK_AMOUNT
FROM XXX;Because this CHECK_AMOUNT column would be a generic name, you can use this template in all your reports as long as you provide this column.
Thope that helps
Patrick

Report Template - NULL in Row Template Condition

I just found a workaround, but,
in a report template, in a Row Template # Condition, based on a PL/SQL expression, the condition always fails if/when #COLUMN_VALUE# was NULL.
I worked around this with a NVL in the query - but, is there a better way?
I want the column highlighted when the value is null - to point out where values need to be entered - i.e. when the record needs to be updated.
THanks - Karen

Ok, I have since found out that the setting to make a report template
available in the Based on > Visualization templates is in the
'package.xml' file for each report. The value that needs to be changed
is <IsQueryParameterized>0</IsQueryParameterized> and change the 0 to 1.
kmcooke1
kmcooke1's Profile: https://forums.netiq.com/member.php?userid=5806
View this thread: https://forums.netiq.com/showthread.php?t=49091

How to prevent duplication on a column with condition

Hello everyone,
I need some advice here. At work, we have an Oracle APEX app that allow user to add new records with the automatic increment decision number based on year and group name.
Says if they add the first record , group name AA, for year 2012, they get decision number AA 1 2013 as their displayed record casein the report page.
The second record of AA in 2013 will be AA 2 2013.
If they add about 20 records , it will be AA 20 2013.
The first record for 2014 will be AA 1 2014.
However, recently , we get a user complaint about two records from the same group name have the same decision number.
When I looked into the history table, and find that the time gap between 2 record is just about 0.1 seconds.
Besides, we have lookup table that allows admin user to update the Start Sequence number with the restraint that it has to be larger than the max number of the current group name of the current year.
This Start sequence number and group name is stored together in a table.
And in some other special case,user can add a duplicate decision number for related record. (this is a new function)
The current procedure logic to add new record on the application are
_Get max(decision_number) from record table with chosen Group Name and current year.
_insert into the record table the new entered record with decision number + 1
_ update sequence number to the just added decision number.
So rather than utitlising APEX built-in automatic table modification process, I write a procedure that combine all the three process.
I run some for loop to continuously execute this procedure, and it seems it can autotically generate new unique decision number with time gap about 0.1 second.
However, when I increase the number of entry to 200, and let two users run 100 each.
If the time gap is about 0.01 second, Duplicate decision numbers appear.
What can I do to prevent the duplication ?
I cannot just apply a unique constraint here even for all three columns with condition, as it can have duplicate value in some special condition. I don't know much about using lock and its impact.
This is the content of my procedure
create or replace
PROCEDURE        add_new_case(
--ID just use the trigger
p_case_title IN varchar2,
p_year IN varchar2,
p_group_name IN VARCHAR2,
--decisionnumber here
p_case_file_number IN VARCHAR2,
--active
p_user IN VARCHAR2
AS
default_value NUMBER;
    caseCount NUMBER;
seqNumber NUMBER;
previousDecisionNumber NUMBER;
BEGIN
--execute immediate q'[alter session set nls_date_format='dd/mm/yyyy']';
SELECT count(*)
        INTO caseCount
        FROM CASE_RECORD
        WHERE GROUP_ABBR = p_group_name
        AND to_number(to_char(create_date, 'yyyy')) = to_number(to_char(date_utils.get_current_date, 'yyyy'));
        SELECT max(decision_number)
        INTO previousDecisionNumber
        FROM CASE_RECORD
        WHERE GROUP_ABBR = p_group_name
        AND to_number(to_char(create_date, 'yyyy')) = to_number(to_char(date_utils.get_current_date, 'yyyy'));
        IF p_group_name IS NULL
        THEN seqNumber := 0;
        ELSE
        SELECT seq_number INTO seqNumber FROM GROUP_LOOKUP WHERE ABBREVATION = p_group_name;
        END IF;
    IF caseCount > 0 THEN
           default_value := greatest(seqNumber, previousdecisionnumber)+1;
    ELSE
           default_value := 1;
    END IF;
INSERT INTO CASE_RECORD(case_title, decision_year, GROUP_ABBR, decision_number, case_file_number, active_yn, created_by, create_date)
VALUES(p_case_title, p_year, p_group_name, default_value, p_case_file_number, 'Y', p_user, sysdate );
--Need to update sequence here also
UPDATE GROUP_LOOKUP
SET SEQ_NUMBER = default_value
WHERE ABBREVATION = p_group_name;
COMMIT;
EXCEPTION
WHEN OTHERS THEN
    logger.error(p_message_text => SQLERRM
                ,p_message_code => SQLCODE
                ,p_stack_trace => dbms_utility.format_error_backtrace
    RAISE;
END;
Many thanks in advance,
Ann

Why not using a sequence for populating the decision_number column ?
Sequence values are guaranteed to be unique so there's no need to lock anything.
You'll inevitably have gaps and no different groups will have the same decision_number in common.
Having to deal with consecutive numbers fixations you can proceed as
with
case_record as
(select 2012 decision_year,'AA' group_abbr,1 decision_number from dual union all
select 2012,'BB',2 from dual union all
select 2012,'AA',21 from dual union all
select 2012,'AA',22 from dual union all
select 2012,'BB',25 from dual union all
select 2013,'CC',33 from dual union all
select 2013,'CC',34 from dual union all
select 2013,'CC',36 from dual union all
select 2013,'BB',37 from dual union all
select 2013,'AA',38 from dual union all
select 2013,'AA',39 from dual union all
select 2013,'BB',41 from dual union all
select 2013,'AA',42 from dual union all
select 2013,'AA',43 from dual union all
select 2013,'BB',45 from dual
select decision_year,
       group_abbr,
       row_number() over (partition by decision_year,group_abbr order by decision_number) decision_number,
       decision_number sequence_number -- not shown (noone needs to know you're using a sequence)
from case_record
order by decision_year,group_abbr,decision_number
DECISION_YEAR
GROUP_ABBR
DECISION_NUMBER
SEQUENCE_NUMBER
2012
AA
1
1
2012
AA
2
21
2012
AA
3
22
2012
BB
1
2
2012
BB
2
25
2013
AA
1
38
2013
AA
2
39
2013
AA
3
42
2013
AA
4
43
2013
BB
1
37
2013
BB
2
41
2013
BB
3
45
2013
CC
1
33
2013
CC
2
34
2013
CC
3
36
for retrieval (assuming decision_year,group_abbr,decision_number as being the key):
select decision_year,group_abbr,decision_number -- the rest of columns
from (select decision_year,
               group_abbr,
-- the rest of columns
               row_number() over (partition by decision_year,group_abbr order by decision_number) decision_number
          from case_record
         where decision_year = :decision_year
           and group_abbr = :group_abbr
where decision_number = :decision_number
DECISION_YEAR
GROUP_ABBR
DECISION_NUMBER
2013
AA
4
if that's acceptable
Regards
Etbin

Is it possible to create a Column with Conditional Mandatory with another Column?

Is it possible to create a Column with Conditional Mandatory with another Column?
For example
In a Table we have column A, B, C.
A is Primary Column.
B is Optional
C is Conditional Mandatory.
A B
C
12345 ABC
OK
12346 NULL
NULL
12347 ABC
OK
Only if the B Column has the value then only C column should be mandatory

I guess you can't create a condtional mandatory column directly. However, you can use check constraint to on the column
create table YourTable
A int primary key,
B char(3),
C int,
constraint ch_con check(
B
is not null
or C is null

Html tags removed when #COLUMN_HEADER# is used in column template

Hi all,
I'm using APEX 4.0.2, theme 2 Builder Blue.
I am trying to add html tags to dynamically generated column headings of a dynamic SQL Report.
When using a standard report template, the headings contain the html tags. However when I want to use one of the vertical lay-outs all html tags are removed. After some research I found out that when the substitution string #COLUMN_HEADER# is used within the column headings part of the template, the html tags are being preserved. They are removed however when the #COLUMN_HEADER# substitution string is used in the column templates part of the template.
This is easily testable by using for instance "return htf.bold ('COL01')" as dynamic column header.
Is this a bug or am I overlooking something? Is there another solution maybe to preserve html tags in the column heading?
Cheers, Erik

webdynpro appears to use XHTML instead of HTML so the syntax is a bit more limitted and more picky.
this link explains the difference between the two syntaxes:
http://reference.sitepoint.com/html/html-xhtml-syntax
you can test your tags in this validator tool
http://validator.w3.org
solved? have a good week, and holidays.

Row and Column Template ?

Trying to create this thing but no matter what I do I keep getting this ridiculous error:
Cannot create a linked row and column template based on
the selected rows. The grid needs to have at least one data row that is
not part of a row and column template.
What does this mean?

You can get your requirement done using the Row and Column Template
You can not save a row and column template with all rows in a report. You have to exclude at least one data row, otherwise you
will get the error that you mentioned.
If you want to save all the rows as a template and re-use it in other report, you can insert a data row at the end of all rows and hide that.
Now you can select the complete row set as a template by excluding the extra data row that you will insert & hide.
If you want to link the template in other reports with same row set you must be very careful with the formatting as you need to apply
inherit formatting before saving the template. I suggest to spend some time with the FR online documentation.
Regards
Ram

Row and Column Template in Hyperion Reporting

Hi
Whenver I am trying to save a column of a report as a template , it is giving an error :
"The selected columns contain one or more of the items below that cannot be included in templates:
Invalid Input "
I am not sure what does this mean. Though I have already deselected the "Link to Source Object". Can anyone suggest ?

it may also worth cross checking below form doc:
a.If your row and column template contains formulas with external references (for
example, to cells outside of the selected row and column template), you are prompted
to modify those formulas before saving the row or column template.
Note: You can save a row and column template that contains cell formulas, as these can
be discarded. For more information, see step 9.c on page 115.
b. If a secondary database connection was specified within the row and column template,
a dialog box displays prompting you to continue saving the template. If you save the
template, the secondary database connection you specified in the row and column
template is discarded. The primary database connection is then used for the row and
column template.
c. If unsupported properties are found, an Information dialog box presents a list of
properties to discard before saving the template. For example, if the row and column
template contains a cell formula, you can choose to save the template without the
formula or not save the template.

Hyperion Reports - Row and Column templates

<p>Sorry if this may be a bit basic but we are new to Hyperionreports. Currently we are going through a redesign process and washoping to get some viewpoints on the benefits of using row andcolumn templates within reports. I am looking at this option butgetting frustrated by the limitations around formatting, etc</p><p> </p><p>Are there any views out there on the preferred options. We havea particular style in design we need to include which is becomingdifficult when we use row and column templates</p>

it may also worth cross checking below form doc:
a.If your row and column template contains formulas with external references (for
example, to cells outside of the selected row and column template), you are prompted
to modify those formulas before saving the row or column template.
Note: You can save a row and column template that contains cell formulas, as these can
be discarded. For more information, see step 9.c on page 115.
b. If a secondary database connection was specified within the row and column template,
a dialog box displays prompting you to continue saving the template. If you save the
template, the secondary database connection you specified in the row and column
template is discarded. The primary database connection is then used for the row and
column template.
c. If unsupported properties are found, an Information dialog box presents a list of
properties to discard before saving the template. For example, if the row and column
template contains a cell formula, you can choose to save the template without the
formula or not save the template.

#COLNUM# #COLUMN_VALUE# in column Template Condition

Similar Messages

Maybe you are looking for