Categories
- All Categories
- 75 Oracle Analytics News
- 7 Oracle Analytics Videos
- 14K Oracle Analytics Forums
- 5.2K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 40 Oracle Analytics Trainings
- 59 Oracle Analytics Data Visualizations
- 2 Oracle Analytics Data Visualizations Challenge
- 3 Oracle Analytics Career
- 4 Oracle Analytics Industry
- Find Partners
- For Partners
Update multiple rows at a time for write back column - OBIEE Report
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.
Answers
-
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.
0 -
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.
0 -
+1 - writeback never ever took off for a reason...
0 -
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
0 -
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.
0 -
Hi All,
Thank you for the response. We are planning to implement Oracle apex.
Thank you,
steel.
0