Categories
Add Writeback Feature to DV
In classic, the writeback feature is very useful in collecting inputs from users and bridging the gap between bi tools and full blow apex or java apps that require a lot of development.
Would love to see the writeback feature added to DV. it will be especially useful for distributed BI cases like at oracle with SI-DV, where the average dv developer does not have RPD or admin access to build classic views and enable writeback.
Comments
-
This seems like a valuable feature. I am interested in hearing more about the use case here, as we do have a version of database writeback offered in OAC Data Flows.
@Brian Watkins-Oracle Would you mind sharing more details on the use case you outlined above? (For example, if you have a specific scenario in mind it would be helpful to understand what target system you'd want to write back to, how much data would be written to the target, is there a need to execute this writeback on a schedule, etc)
1 -
Hi Gabrielle, thanks for the feedback!
We have two use cases at the moment. The first is related to collecting status updates and notes from the sales teams related to our AR aging top customers. To build the report we join an aging report to the revenue analysis subject area, then cut our top aging accounts by product, sales leader, and sales rep. so it's two fields for about 100 rows of data in that case.
The second case is related to a project tracker that we run for our Deal Desk team. The idea there was to collect inputs for status changes, person assignment, etc directly into DV right next to the dasboarding and reporting itself. This use case might be better covered by an apex app with separate DV reporting though.
1 -
If I could vote more than once, I would cast 100 votes for this one.
2 -
Any update on this one?
Would be highly appreciated to see it planned.0 -
Hi @O_Sanne and welcome to the community. Please refer to the to understand when an idea is being considered. Thank you.
0 -
This is useful feature.
Many times, we need some subjective feedback stored in dataset. Uploading teh spread sheet every time may not feasible.
It is little complex feature to implement but worth to consider.
1 -
We have a use case within our Budget vs Actual dashboard that we’re looking to enhance. Currently, the dashboard includes budget, actuals, and encumbrances. However, business managers have expressed a need for a “what-if” scenario feature that would allow them to account for anticipated expenses and see how those might impact their available budget.
Because these anticipated expenses can change frequently before becoming actual POs in the system, we’re exploring options that would allow users to write back to a table. This functionality would give them a more realistic and dynamic view of their remaining budget, taking into account potential future expenditures.
2
