Categories
- All Categories
- Oracle Analytics Learning Hub
- 17 Oracle Analytics Sharing Center
- 17 Oracle Analytics Lounge
- 224 Oracle Analytics News
- 44 Oracle Analytics Videos
- 15.8K Oracle Analytics Forums
- 6.2K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 84 Oracle Analytics Trainings
- 15 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Provision to Increase Data Flow Branching to at least 12
Currently, we have 5 as the maximum limit up to which a datasource can be branched into. We have encountered customer scenarios wherein the financial data needs to be branched to 12 (for each month in a year). The feature limitation is forcing to resort to more complex solutioning, by first branching to 4 quarters and each quarter split again into 4 and eventually use Unions to bring it all together.
This could be much simplified for similar financial data requirements, if we have an option to increase the branching to at least 12.
Comments
-
Hi @Ambili - this use case makes a lot of sense. Can you add a second branch immediately after the first branch to simulate generating 12 outputs?
1 -
Here's an example of what I mean:
1 -
Thanks for the example @GabriellePrichard-Oracle. I was also thinking if Nested Branching can be done.
In the above use-case my thinking was to create a nested Branch to have each quarter of the year included.
Something like this
1 -
Hello, after the branching we are completing a Transform step rather than a Save Data step. Currently under the quarterly concept (limitation of 4 branches), each Fiscal Period and its attributes and measure has to be unioned together. Example June to July, then June/July to August to make Q1. Once this has been completed for all 4 quarters, then you have to complete the same union steps to union together all 4 quarters. Ultimately the dataflow stream becomes so long that even with Show Labels un-checked, it is basically un-editable.
Was there a reason as to why the branching limitation was set to 5?
Thanks-
1 -
Thank you, @Elizabeth Pooler, for sharing more details about the use case.
@GabriellePrichard-Oracle , @Sushant Mishra - This is the exact customer scenario that is causing the complexity, due to the branching limitation.
0 -
Looking at the Scenario, and the details provided I am also wondering if the limit can be increased to 1 5 or 20.
I have upvoted for the idea as I think that we should have option in place to change the scenarios or limitation on such restrictions in OAC.
1 -
Thank you Sushant, Ambili, and Gabrielle!
0
