Update multiple rows at a time for write back column - OBIEE Report

Steelbird

Hi All, @Christian Berg, @Jerry Casey, @Joel Acha , @Gianni Ceresa

We have implemented write back option on two columns Notes and Payment Number.

The requirement is like If we want to update only on 1 customer number which it should have to update multiple rows for Notes and payment number column. How can we achieve this ?

Below is the data..with one customer number which I would like to update only once and it should reflect on 3 rows at a time.(Data for Notes and Payment number column is same).

Thank you,

Steel.

[Deleted User]

Steelbird wrote:How can we achieve this ?

By following the documentation:

https://docs.oracle.com/middleware/bi12214/biee/BIESG/GUID-FF6954BA-2DE0-4422-BA58-05F32936F4FF.htm#BIESG1358

And then coming back with a precise description of how you've implemented what and asking a detailed question.

Joel

To add to @Christian Berg insights, I would also consider reviewing the design of your analyses. The screenshot you provided is at a higher level of granularity than your writeback requirement. I would have an analysis aggregated up to your customer number level and place the writeback there and there can be a drill down option to drill down to the level you have in your screenshot.

[Deleted User]

Or let an analytics do what it's supposed to do: analyze.

And use something that's built for and meant for data entry and manipulation: Oracle APEX.

Joel

+1 - writeback never ever took off for a reason...

M De Fanti

Hi Steel,

maybe you could use a specific db instruction in the xml of custom_messages, where you simply update the records using a where condition only on the "original" customer number (filed to add to the table and not to be overwritten)

Something like

update table

set cust_num=@1

where ori_cust_num=@2

Regards

Massimo

Robert Angel

One possible solution for you, if you have access to create DB objects is to create a view and a trigger on the view.

https://www.oracletutorial.com/plsql-tutorial/oracle-instead-of-triggers/

Then use the view / trigger combination as an API to handle your multiple update logic.

If the straight update with a single parameter cannot handle it, and you do not have the appetite for Christian's excellent Apex suggestion.

hope this helps,

Robert.

Steelbird

Hi All,

Thank you for the response. We are planning to implement Oracle apex.

Thank you,

steel.