Hi everyone,
I have a requirement to build 3 cubes for a company which sells bouquets of flowers to different retailers.
Describing the issue
The client would like one of the cubes to be designed in a way so it makes use of multi-calendars. The client has a handful of customers who each have a separate calendar stored in a separate file. The client has asked me to deliver the following:
i. Design the cube so that the time dimension is based on the calendar for the selected customer.
ii. Design the cube so that if multiple customers are laid out side by side in the browser the standard calendar will be used.
I am not sure if this request is realistic. I have been thinking that I will need to create various time hierarchies for each customer and then the user will need to pick which hierarchy to use in the browser.
Where advice is needed
My reason for this post is to try to get other people's opinions on what approach they'd use if they had been given such a request.
Firsty: should I develop a time dimension for every calendar file, create lots of virtual cubes for each customer and link them? (is that possible even?), or just one time dimension table which contains the hierarchy for all the different customer calendars.
Secondly is there a completely different approach to this I haven't thought of.
[/color blue]
cheers.
Nassy
I have a requirement to build 3 cubes for a company which sells bouquets of flowers to different retailers.
Describing the issue
The client would like one of the cubes to be designed in a way so it makes use of multi-calendars. The client has a handful of customers who each have a separate calendar stored in a separate file. The client has asked me to deliver the following:
i. Design the cube so that the time dimension is based on the calendar for the selected customer.
ii. Design the cube so that if multiple customers are laid out side by side in the browser the standard calendar will be used.
I am not sure if this request is realistic. I have been thinking that I will need to create various time hierarchies for each customer and then the user will need to pick which hierarchy to use in the browser.
Where advice is needed
My reason for this post is to try to get other people's opinions on what approach they'd use if they had been given such a request.
Firsty: should I develop a time dimension for every calendar file, create lots of virtual cubes for each customer and link them? (is that possible even?), or just one time dimension table which contains the hierarchy for all the different customer calendars.
Secondly is there a completely different approach to this I haven't thought of.
[/color blue]
cheers.
Nassy