Thanks for your response. I'm not sure it directly aligns to the issue I initially reported, but it is 100% also an issue for us. We prepare workbooks in test environments prior to putting them into prod. When we move them to prod, the datasets and connections get replicated over and over. It does get very clunky.

Thank you for this very elaborate response. I appreciate it. This is currently how we are addressing the new model. However, your explanation is basically confirming my point that this new approach is much more complex than it was previously. we used to create a data flow, run it, build workbooks off the resulting dataset,…

Sorry, not following all of this. our concern is that in order for end users to be able to consume data in the workbooks on shared folders, both the dataset and dataflow have to be in the same shared folder. We don't really want our end users to be able to see the data flows or datasets in those folders.

Thanks for the response. This doesn't seem like the behavior we are experiencing though. If I create a dataset it resides in My Folders. Then I create a data flow using that dataset and both are initially in My Folders. I create a workbook from the resulting dataset and move it from My Folders to a Shared Folder for end…

Thanks. actually what I have now is an overlay chart with two bars, one for actuals one for forecast, and a line chart with the original plan. it's good as an alternative i was just trying to see if there was any way to do what my client had requested.

Thanks. that is how I am currently showing it but my clients asked for the other view. Yes, the highest value, whether it be actual, original budget, or reforecast would be the highest value of the bar. i am attaching a pic of what they requested.

some additional context: We experienced this issue again. these were the replication steps. We created a data flow and ran it. then, we needed to create a second data flow that was similar to the first, so rather than recreate it from scratch, we did a "Save As" on the original and updated from there. We gave the dataset…

@Gianni Ceresa about 85 columns and close to a million rows, OAC (current version)

@GabriellePrichard-Oracle nulls would be great

@Gabby Rubin-Oracle this is typically updated on the first or second business day of a month (for example, September 3) for the prior month end accounting close. So some of the branches in the flow are for August (Aug-2025 period name) and some of the branches are for the prior month end close (Jul-2025).

Hi @Gabby Rubin-Oracle - you would have to explain that concept to me. I'm not sure how a data flow can reference a parameter table. I'm attaching a screenshot with a snip it of a data flow we update monthly. it would be great to only have to update a parameter for current month and prior month instead of going into each…

Hi! We have data flows that, in some cases, have a dozen branches. each branch is pulling data for either the current or prior month, so we have filter boxes embedded within each branch of the flow that we have to update every month. If we had a parameter for current month and prior month we could just enter those once and…

@GabriellePrichard-Oracle thank you. I did see the videos for the data flow upgrades coming this month. they look great and could solve this issue. (the zoom functionality currently does not work).

This would be an enormous help!