Oracle Analytics Cloud and Server

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Write back template error in obiee 12.2.1.0.0

Received Response
131
Views
16
Comments
2»

Answers

  • Robert Angel
    Robert Angel Rank 8 - Analytics Strategist

    And I don't have a crystal ball to see the syntax of what you tried...

  • Sunny86
    Sunny86 Rank 6 - Analytics Lead

    My question is I have two tables of similar structure .

    Table 1 : Deal Table

    Table 2: Deal Corporate Table

    I need to write back to both the tables at the same time. Is it possible? two update statements in one write back template?

  • cesar.advincula.o
    cesar.advincula.o Rank 6 - Analytics Lead

    You have to wonder yourself if you can do that in the UPDATE SQL statement, since I know you cannot do that ..

    "A template can contain SQL statements other than insert and update. The write-back function passes these statements to the database. However, Oracle does not support or recommend the use of any statements other than insert or update."

    https://docs.oracle.com/middleware/12211/biee/BIESG/GUID-6F16F7CA-E525-4569-A5A0-C1C0F851F57E.htm#GUID-82215685-B79C-4DF…

  • cesar.advincula.o
    cesar.advincula.o Rank 6 - Analytics Lead

    Hi I think you should close this thread

  • Robert Angel
    Robert Angel Rank 8 - Analytics Strategist

    You could;

    create a view on the table(s) in the underlying DB - assuming it is Oracle.

    create a trigger to handle inserts on the view, making the trigger take the data and insert it into both tables. (Or whatever more complex logic you desire, as complex as you like!)

    I have done this previously to get around the limitations of write back.

    I know write back is not apex, but you would have thought Oracle would have either provided fully formed form functionality, or not. Write back as it is is poor without out of system workarounds!

  • cesar.advincula.o
    cesar.advincula.o Rank 6 - Analytics Lead

    His Rober a trigger is a good way but don’t know if this is the best solution.. as you mentioned it has a list of constraints that are written in the oracle documentation .. since there is no sql statement to update two tables at the same time is not a standard way.. perpahs the OP should to rethinks the model