Adhoc reports based on Multiple fact tables
Answered
- we have multiple fact tables (Claims Fact, Policy Fact etc.) and their dimensions. In Yellowfin we want to be able to compare the data in these fact tables. In order to do that, all the data has to be present in one view. It works with single fact table but if two fact tables both have a common field like Policy Id or a date key then it’s a reference to the Policy & date dimension, a circular join is created, and this is not supported by Yellowfin.
- Based on above scenario, please suggest how users can create adhoc reports on multiple fact tables in YF to enable self-service capabilities?
I think you are looking to replicate the context functionality available in Business Objects Universes....
I think you are looking to replicate the context functionality available in Business Objects Universes....
Hi Dave,
There could be a few different ways to tackle this in YF, it just depends on what would work best for you .
Most people here seem to think the best way to handle this would be to use aliases, you simply drag one table several times and join to fact tables.
Then at the report level, you use sub-queries
OR
Create multiple views, then pull them together at the report level using advanced sub-queries.
Lastly.. we do have a Data Transformation module coming in 7.4, due for release early Nov, which can act as an additional layer which will allow you to pull in multiple views, and aggregate the data, so the report can then report off that layer.
Does the above give you an idea how you would prefer to proceed?
Thanks,
David
Hi Dave,
There could be a few different ways to tackle this in YF, it just depends on what would work best for you .
Most people here seem to think the best way to handle this would be to use aliases, you simply drag one table several times and join to fact tables.
Then at the report level, you use sub-queries
OR
Create multiple views, then pull them together at the report level using advanced sub-queries.
Lastly.. we do have a Data Transformation module coming in 7.4, due for release early Nov, which can act as an additional layer which will allow you to pull in multiple views, and aggregate the data, so the report can then report off that layer.
Does the above give you an idea how you would prefer to proceed?
Thanks,
David
Replies have been locked on this page!