The OneStream Community is temporarily frozen until June 29th due to the ongoing maintenance. Please read the blog post here to learn more.
Forum Discussion
FrankDK
2 years agoContributor
Extended Analytics export
hi folks!
I'm seeking advice on overcoming the obstacle of exporting data from an Operating System (OS) to make it accessible for a Business Intelligence (BI) solution. Currently, my goal is to ex...
RobbSalzmann
2 years agoValued Contributor II
Hi FrankDK
Here are some ideas in the form of an outline of the steps needed to create an "extended analytics" star schema like HFM has 🙂 :
- Choose the dimensions you wish to use in the star schema
- Create a fact table with columns:
- (1) column for each exported dimension's member IDs
- (12) data columns, one for each period
- Create a dimension table for each exported dimension. The ID column in each dimension table is PK, tied to the dimension column in the fact table. This is the "star", dimensions at the points and facts in the center
- Choose a default member from each dim not exported to use in the member script, I'm thinking export with FDX
- Create a buffer to hold the fact data as a MemberInfo from each dim associated with each data value.
- Export the Dimensions to the dimension tables
- Using the buffer, export the data by member id for each dimension into the fact table.
Viola! you have an extended analytics star schema for BI analysis. I think everything here can be coded in an Extender Rule.
- FrankDK2 years agoContributor
hi Robb, thanks for your input; which aligns pretty much with the way we have planned to build and run the process. But do you have any practical experience with how to manage/control/configure what data should be exported to the fact table? A defined Cubeview you extract from using FDX?
Also, I was on the hunt for other solutions and/or experiences where a PULL mechanisme was used compared to this PUSH process, don't know if you can chip in here?
Cheers Frank
Related Content
- 4 years ago
- 7 months ago
- 4 years ago