Classic report SQL with BLOB column not refreshing with jQuery Trigger Apexrefresh call

Similar Questions

• Database trigger - PL/SQL: ORA-00984: column not allowed here

  I am trying to create a trigger that will update a table of audit used when a row is changed. Using a sequence number to assign an identifier unique to each line as it is created. Need to capture the user ID, date modified and action (update), the image of the front line.
  

  CREATE SEQUENCE emp_audit_seq START WITH 10;                

  Create table emp (
     empno       NUMBER(4)      Primary Key,
     ename       VARCHAR2(10),
     job            VARCHAR2(9),
     mgr           NUMBER(4),
     hiredate     DATE,
     sal             NUMBER(7,2),
     comm        NUMBER(7,2),
     deptno       NUMBER(2));

  CREATE TABLE emp_audit   (
       audit_uid          NUMBER(15)      Primary Key,
       change_date          DATE,
       change_user          VARCHAR2(30),
       action                  CHAR(1),
       empno                  NUMBER(4),
       ename                  VARCHAR2(10),          
       job               VARCHAR2(9),
       mgr               NUMBER(4),
       hiredate          DATE,
       sal               NUMBER(7,2),
       comm                  NUMBER(7,2),
       deptno                  NUMBER(2));

  CREATE OR REPLACE TRIGGER trig_emp_audit
    BEFORE UPDATE ON emp
    FOR EACH ROW
  BEGIN
    INSERT INTO emp_audit
      VALUES(emp_audit_seq.nextval, change_date, change_user, action, :old.empno, :old.ename, :old.job, :old.mgr, :old.hiredate, :old.sal, :old.comm, deptno);
  END;
  /
  
  Warning: Trigger created with compilation errors.
  
  SQL> show errors
  Errors for TRIGGER TRIG_EMP_AUDIT:
  
  LINE/COL ERROR
  -------- -----------------------------------------------
  2/3      PL/SQL: SQL Statement ignored
  3/149    PL/SQL: ORA-00984: column not allowed here

  Can someone help to help me find what I'm doing wrong with the trigger?
  
  Published by: LostNoob on August 25, 2012 14:24

  First of all, when you write an INSERT statement, it is always good for the columns that you insert in the list. Which makes the code easier to follow - you do not have separately pull toward the top of the table definition to know what order of columns is inserted. And it makes the code easier to manage because the declaration become invalid if you add a new column to the table in the future.

  Second, CHANGE_DATE, CHANGE_USER and ACTION are not (probably) functions and are not local variables so it is not supposed to use them in an INSERT statement. You need to write code or to take advantage of the existing functions to fill in these columns. I suppose, for example, that you want to use SYSDATE to fill the CHANGE_DATE and the USER to fill the column CHANGE_USER. My guess is that ACTION must always be a 'U' for UPDATE.

  Thirdly, it seems that you left the: old man on the DEPTNO column.

  Put them all together, you would have something like

  CREATE OR REPLACE TRIGGER trig_emp_audit
    BEFORE UPDATE ON emp
    FOR EACH ROW
  BEGIN
    INSERT INTO emp_audit(
        audit_uid,
        change_date,
        change_user,
        action,
        enpno,
        ename,
        job,
        mgr,
        hiredate,
        sal,
        comm,
        deptno )
      VALUES(
        emp_audit_seq.nextval,
        sysdate,
        user,
        'U',
       :old.empno,
       :old.ename,
       :old.job,
       :old.mgr,
       :old.hiredate,
       :old.sal,
       :old.comm,
       :old.deptno);
  END;
  / 
  

  Justin

• PL/SQL: ORA-00984: column not allowed here

  Sorry, it's probably easy and I forgot something simple, but it's driving me crazy :-)
  

  VARIABLE g_fk_deduction      VARCHAR2(30)
  VARIABLE g_fk_empno          NUMBER
  VARIABLE g_before_or_after_flag     CHAR(1)
  VARIABLE g_deduction_amount     NUMBER
  
  BEGIN
    :g_fk_deduction           := '401K';
    :g_fk_empno               := 7369;
    :g_before_or_after_flag     := 'B';
    :g_deduction_amount          := 150.00;
  END;
  /
  BEGIN
    INSERT INTO emp_deductions      (fk_deduction, fk_empno, before_or_after_flag, deduction_amount)
     VALUES               (g_fk_deduction, g_fk_empno, g_before_or_after_flag, g_deduction_amount);
    COMMIT;
  END;
  /

  Error: PL/SQL: ORA-00984: column not allowed here on g_deduction_amount
  in the value clause.
  Any help would be appreciated.
  
  Table is below:

  CREATE TABLE emp_deductions     (
        fk_deduction            VARCHAR2(30),
        fk_empno                  NUMBER(4),
        before_or_after_flag         CHAR(1),
        deduction_amount            NUMBER(6,2));

  Published by: LostNoob on August 23, 2012 19:06

  rp0428 wrote:
  >
  : g_fk_deduction: = "401k".
  : g_fk_empno: = 7369;
  : g_before_or_after_flag: = 'B ';.
  : g_deduction_amount: = 150.00;
  >
  Why did you put a colon here? Get rid of them.

  They are necessary, since they are declared SQL * more variable.

  The problem for the OP, is that in the clause values in the insert the colon are missing.

  Published by: Mark Williams on August 23, 2012 22:31

  Here is your example requested:

  SQL> create table test (c number);
  
  Table created.
  
  SQL> variable v_c number
  SQL> begin
    2    :v_c := 46;
    3  end;
    4  /
  
  PL/SQL procedure successfully completed.
  
  SQL> begin
    2    insert into test values (:v_c);
    3  end;
    4  /
  
  PL/SQL procedure successfully completed.
  
  SQL> commit;
  
  Commit complete.
  
  SQL> select * from test;
  
           C
  ----------
          46
  
  1 row selected.
  
  SQL>
  

• Classic report SQL question.

  Hello
  
  Can I use Snap on command in a classic report using SQL? If so, how?
  
  I use APEX 3.2.1 with Oracle database 10g.
  
  Thank you
  Mary
  
  Published by: Gabriel on July 23, 2010 11:20

  Hello Mary,.

  WE BREAK is a SQL * more order thus is not allowed in the SQL of a usual report.

  To do this is to use the Break formatting attributes report section. He limited to the break at first, & second or first, second & third columns rows retrieved, but it may be enough for what you're trying to accomplish.

  Hope this helps,
  John

• Classic report area - hide a column from view but include in export

  Hello

  I have a report classic region in my application and I want to hide a particular column of the on-screen display - however I want to include this column when I include the option to export on this region

  On the right, it seems to export only the columns that are available in the region of the screen

  Any ideas would be great?

  Thank you

  S

  Hello

  Thank you for your reply and unfortunately, it has not produced the desired result

  However google'ing it I found the answer.

  Do the conditional display for the column as,

  Conditional display: PL / SQL function body returning a Boolean

  Expression: BEGIN return apex_application.g_excel_format; END;

  This will evaluate to FALSE in the normal display state - but it might be true if we click on export

  Thank you

  S

• Using trigger ('apexrefresh') on a classic report

  4.2.2.00.11 RAC-11.2.0.3 apex.

  With the help of Jquery UI make a popup HTML region dialog box. 2 hidden elements exist in the area of the dialog box. A classic report is a region of the child in the area of dialogue - and use the 2 items hidden as report/SQL variables.

  JavaScript is used to set the values of the 2 hidden items, display the pop-up dialogue window and trigger an update of the classic report.

  Only the shutter button does not work. Which, from my Google search should work.

  The classic report starts with 2 divs. The 1st div id is generated, Apex e.g. report_ < number > _catch. The 2nd div (class uReportContainer) contains the id that I assigned the classic report, for example < regionID > report_.

  Triggering a refresh on each region fails to refresh the report itself. I.e. after does not result in a discount or other identifiers div:

  $('#<divID>').trigger ('apexrefresh');

  What is the identifier (or JQuery selector) to use for a classic report? Or what I am doing wrong?

  Workaround solution - I use a call to the pagination of the classic report in my Javascript instead of the update. For example

  apex.widget.Report.Paginate ('< identifier >', {min:1, max: 100, read: 100});

  It seems to work very well. But I prefer the refresh method and not a hack. :-)

  Strange sounds. I've been watching the code widget.report.js etc, but really, it's pretty basic. There is nothing wild in there. When he realizes it "report_" + id + "_catch" targets and fires before and after the events of refresh it. You can try to trigger an update on this item and see if it works?

• Bug report - classic report lov definition retained when it is no longer relevant

  Hello
  
  In January, I spotted a case where, the attributes were selected after a selection has been changed, and related fields are hidden in the dev environment.
  http://www.grassroots-Oracle.com/2013/01/dynamic-action-hidden-false-actions.html
  
  Anthony Rayner asked me on twitter for more examples, and I just found a.
  
  Classic report - display of the column as "list of selection (query based lov).
  Add sql LOV.
  Replace 'report type column' or 'display as text... '. ', save.
  Change to 'select list... ". '--> lov definition is displayed again.
  
  I actually founded it after assigning the column standard report column, then copy the page - the LOV was present in the new page!
  
  Scott

  Scott,

  Thank you for following up on that. I submitted the bug #16482841 to do this, which will be reviewed at the next major release.

  Thanks again.

  Kind regards
  Anthony.

• Procedure returns ORA-00984: column not allowed here

  Get an error returned by my procedure and can't understand it. Someone has an idea?
  Thanks in advance,
  Carpet
  
  14/2 PL/SQL: statement ignored
  15/80 PL/SQL: ORA-00984: column not allowed here
  
  
  
  CREATE OR REPLACE PROCEDURE basket_add_sp
  (p_idproduct in NUMBER,
  p_price in NUMBERS
  p_quantity in NUMBERS
  p_idbasket in NUMBERS
  p_option1 in NUMBERS
  p_option in NUMBERS)
  IS
  lv_seq_num bb_basketitem.idbasketitem%TYPE;
  BEGIN
  SELECT bb_idbasketitem_seq. NEXTVAL
  IN lv_seq_num
  FROM DUAL;
  INSERT INTO bb_basketitem (idbasketitem, idproduct, price, quantity, idbasket, option 1, option 2)
  VALUES (lv_seq_num, p_idproduct, p_price, p_quantity, p_idbasket, p_option1, p_option2);
  COMMIT;
  END;
  /

  What is p_option2 in the INSERT statement? In the settings, you have only p_option1 and p_option.

  I agree with Walter, you can save an e/s by losing the select double.

• HELP to ' SQL error: ORA-00937: not a function of simple-group.

  < p >
  Hello world:
  
  I have a forum based on oracle 11g database. There two tables: article of thread and the relationship between the two is "one-to-many.
  
  I want to list the total number of seen of all the discussions in each section, and I write the sql code:
  
  Select s.secname, sum (sum1) of join of s section
  
  (select secid, sum1 sum (thrviewednum) of the Group of threads by secid) tt WE s.secid = tt.secid;
  
  
  
  The 'secid' column is the pharmacokinetics of the section table and FK of the table of thread, the "thrviewednum" the number of views of a thread.
  
  But I get the error:
  
  Error in the command line: 1 column: 7
  
  Error report:
  
  SQL error: ORA-00937: not a function of simple-group
  
  I can't understand the problem, could someone help me? Thank you.
  < /p >

  Hello

  Use this

  Select s.secname, sum (sum1) of join of s section

  (select secid, sum1 sum (thrviewednum) of the thread by secid group) THE group s.secid tt = tt.secid by s.secname;

  This is because the select statement contains a column that is not part of any group function, so this column must be there in the group by clause

  Concerning

• Development of the selection list after refresh using jQuery

  Hi all

  I have an Express Application 4.1.1.00.23 application that runs on a server, Oracle 10 g R2.

  In the application, I have a page (suppose it to be Page 10) that has a drop down (let's call it P10_PARENT). Next to the dropdown menu, I have a button that when clicked opens another window popup with page 11. This 11 page is used to create many of the points listed by the P10_PARENT drop down. When enter us the data P11 and click OK, we have a javascript to call a process application that creates the object in the database. Now select the P10_PARENT list is updated to reflect this new object. So after the application process is running, the JavaScript on the Page 11 calls a function in Page 10, using window.opener.functionName. This Page 10 function performs an apex to help refresh

  $('#P10_PARENT').trigger('apexrefresh');
  

  This function returns the Page 11, the page is closed using the Window.Close ().

  It works fine up until this point. Now, there are also by default the value selected in the select list of the newly created object. We made a function for it. But he calls immediately after the outbreak of the updating of the apex does not work because he probably did not updated the list since the back end still.

  Therefore link us an apexafterrefresh event to this element and making the default here. Like this:

  $('#P10_PARENT').bind('apexafterrefresh',function(){
    setdefault('P10_PARENT',newCreatedObjVal);
    alert('Refresh completed!');
  });
  

  But this event does not seem to be triggered. I've tested in IE and Chrome. In Chrome, it started once, but never after that.

  The relevant code on page 10 looks like this. The refreshBusList function is called Page 11 with the value of the newly created object.

  function refreshBusList(pDefault)
  {
    newCreatedObjVal = pDefault;
     $('#P10_PARENT').trigger('apexrefresh');
  }
  
  $('#P10_PARENT').bind('apexafterrefresh',function(){
    setdefault('P10_PARENT',newCreatedObjVal);
    alert('Refresh completed!');
  });
  

  I would like to know what we're doing wrong. Is it still the right way to do it? I can't use dynamic actions here because the logic of javascript page is too complicated be properly implemented using the declarative logic like DAs (we tried once and had to leave after a week. has become a nightmare to manage).

  Any help would be much appreciated!

  Thank you!!

  Aalami

  What does setDefault? Have you tested this feature by running it from the console? It doesn't have the required behavior?

  Can what newCreatedObjVal value contain? What is an object? A string?

  Are you sure that the selection list is updated?

  I would also like to rewrite your refresh logic. On the one hand, you declare a variable of global scope: horrible! There is no need of it. You can also control refreshing after a little better by simply acting on it once.

  function refreshBusList(pDefault)
  {
    // not really necessary. But use "var" to declare scoped variables!
    var newCreatedObjVal = pDefault;
  
    // bind a one time afterrefresh event handler
    // then, trigger the refresh
    $('#P10_PARENT')
    .one('apexafterrefresh',function(){
      setdefault('P10_PARENT',newCreatedObjVal);
      alert('Refresh completed!');
    })
    .trigger('apexrefresh');
  }
  

• Column classic report - export - not visable (APEX 4.1)

  I have a problem with export to excel classic report file.

  I can't do a single column to export, only that one does not work, all the other columns in the report are exported.

  In the column definition value include in exports is set to Yes.

  SQL query is defined as pl/slq body return the sql query.

  It's report

  http://www.deviantpics.com/images/2013/08/14/report.jpg

  It comes to excell

  http://www.deviantpics.com/images/2013/08/14/Excel.jpg

  No, there is no condition on the column, I have reproduced report on the same page with the same set upward and it works on this report.

  I was not able to understand why it does not work on trees report so I recreated all the columns in this report and now it works.

  In addition, there is problem when I get to this site, I can not export the values. I see values in the report, but when I export them in they are not excel file.

  I solved that with refresing region and submit all items that I use in this query, then all values are excellent file.

• Classic report shows wrong "could not parse the SQL query: ORA-00942" error after migrating app to the new environment

  After migrating my APEX 4.1 application to a new environment, one classic report displays a "cannot parse the SQL query: ORA-00942: table or view does not exist" error when the page is displayed. Change the region to report SQL source to somehow (e.g., remove spaces, changing the order of the variables in the WHERE clause) immediately solves the problem, but by returning to the source of the region causes the report error again (the source region valid code without error, however).

  Throw the error message:

  Select v.id,

  v.Col1

  of view_vw v

  where (: P1_FILTER is null or)

  v.col2 = :P1_FILTER)

  Do not throw error:

  Select v.id,

  v.Col1

  of view_vw v

  where (:P1_FILTER is null or)

  v.col2 = :P1_FILTER)

  Changing the order of column in the report has the same effect; i.e. He arranges, but return back to the original column order causes the error to display.

  It's as if a cached result for the correct select statement used by the report is displayed. However, the application does not use the caching of page/region. Any ideas of what could be the cause?

  He solved. Ultimately, all that was necessary was to clear the DB cache using:

  alter system flush shared_pool;

• Classic report with column LOV

  I have simple classic report (Apex 4.2.4) with two columns. One is to main table and shows the ID; another column is LOV that contains detail table names, which must FK main table.

  Table structure:

  master_table (id NUMBER);

  detail_table (detail_name VARCHAR2 (50), master_id NUMBER);

  Source report looks like:

  Select

  ID,

  lov_column null

  of master_table;

  lov_column is defined as a query in function LOV and query looks like:

  Select detail_name from detail_table

  where master_id = #ID #.

  But the application does not recognize the values #ID #? Can I use it without the WHERE statement, but in this case in LOV, I got all the records, and that I want in a folder have values only for this ID.

  What can I do?

  Thanks in advance.

  Kiran I thank you for your care, I finally found the solution.

  Apex.Oracle.com cloud works with Apex5, it is not possible to obtain a classical column LOV relation, but it is possible to do this by using APEX_ITEM. SELECT_LIST_FROM_QUERY. And so I did in my application.

  in the statement I wrote:

  Select

  Mt.ID,

  apex_item.select_list_from_query (1, null, "select dt.detail_code d, dt.detail_code r detail_table dt where dt.master_id = ' |") Mt.ID) retail

  of master_table TM;

  And it works!

• Classic report region is not refreshing using the DA

  Apex 4.2.2 on Oracle 11.2 use EPG in Linux

  I have a Camembert and I want user to click on a section and refresh a report classic region under the graph on the same page.  I've used various methods to try to get this working, but none succeeded.  Here's what I have right now - when a pie is clicked, a value is returned to a text P19_STATUS field in the region of report using javascript in a DA:

  AnyChart.getChartById ($("#chart2_chart_object").attr ("id"))

  .addEventListener ("pointClick", Function {}

  $s ("P19_STATUS", e.data.Name);

  });

  It works fine as I can see the value that corresponds to the label in the chart.  I created a second DA with an event of amendment to article P19_STATUS. There is a REAL action - Refresh.  Selection type:, Region: classic report (40).  I put also enable partial Page Refresh Yes on the classic report and the elements on the Page to be sent to: P19_STATUS.  When the user clicks on the cake the value is in P19_STATUS, but the report is not updated.  FYI, I also tried $('#report_region_id') .trigger ("apexrefresh");  in the second DA but which doesn't work anymore.  I want only the region refresh, not the page.  Please help - I'm fairly new to Apex, so please be as detailed as possible.  Thank you!

  Nicolette wrote:

  User12037683

  The missing part was that the report is a subregion of the chart area.

  Under regions have their own model of the region. Instead the use of models from the parent area area unit.

  Models of the region can be specified for the sub regions as all other regions. In this case it seems to be a problem with the sub-region model as it appears in the list of model as 48560037058667637086selection.

• First group title below displays under the column headers using the model 23 classic report with the help of repeat titles on break

  Hello

  I am migrating an application from 3 APEX APEX 4.2 on a thing I noticed with the classic reports when I put them in the model 23, it's that the first section break has break notch under the headings of columns for this section of line while the remaining lines properly have it display above the headers on the subsequent sections of group.

  
  When I look at firebug code I saw that all the tables but the first, the break line is included in the last line of the previous table, so I can see how it did not work for the holidays since.

  I have tow questions.

  1. is it really intentional because it seems not terribly elegant and my users to zero immediately above as a perceived bug.

  2. is there a reasonable job around always use headers repeat on break? I have multiple reports on the same page in places so switch to interactive reports is not a quick fix for me in this case.

  Example of a question can be seen at apex.oracle.com at home

  Thank you

  Brad

  Roadling wrote:

  Hello

  I am migrating an application from 3 APEX APEX 4.2 on a thing I noticed with the classic reports when I put them in the model 23, it's that the first section break has break notch under the headings of columns for this section of line while the remaining lines properly have it display above the headers on the subsequent sections of group.

  1. is it really intentional because it seems not terribly elegant and my users to zero immediately above as a perceived bug.

  The Standard report template definition in issue 23 contains thead and tbody elements:

  Before the column header

  Column title template

  #COLUMN_HEADER#
  

  After the title column

  After the lines

  
  
  
  
  
  
  #PAGINATION#
  
  
  #EXTERNAL_LINK##CSV_LINK#
  

  This is intentional, the best practice for marking up HTML tables. What is not expected is the problem that arises when this model is used with the break of repeat titles on break formatting option. The repeated headings result table consisting of soup of tags containing several poorly constructed tbody and thead, which is not valid elements.

  2. is there a reasonable job around always use headers repeat on break? I have multiple reports on the same page in places so switch to interactive reports is not a quick fix for me in this case.

  Create a copy of the report model Standard in Standard (break formatting) for use with reports of the break, remove the thead and tbody definitions of template tags and the breakdown of the reports to use the new model of change. (Or, if you use mainly break reports using the Standard template, keep the tags in the copy and remove them from the original in order to minimize the number of reports, you need to change.)

  Personally, I would create a report model of line custom to break complex reports in order to be able to have complete control over the structure and presentation.