Recent content by Vivarto

Hi, I'm just finishing off the modelling of a classic Sales Orders fact and have pushed all of the header information down to the line level as I believe is best practice. I've also got the Order number as a degenerate dimension but there are attributes that really are attributes of the header...

Ah, Mr Blom, read a lot of your posts. Yes, the composite dimension idea came to me last night but its good to hear it from some one else. What has happened today is that the ProductWarehouse has become a fact as I now have a measure that is at that grain (stock in transit). That being the...

Hi, I have a fact table with 5 dimensions. Two of them are product and warehouse. There are textual attributes of the product / warehouse combination Clearly these can't be held in either of the two dimension tables I have created a ProductWarehouse table to hold the attributes. Not sure what...

Still can't do this but have developed a work-around. Set up an attribute, Leaf Level, in the source dimension. Create data item with filter() and select on the attribute: filter( [Cube].[Dimension].[Hierarchy], [Cube].[Dimension].[Hierarchy].[Leaf Level] = 'Y') Think getting leaf members...

No takers? I've scoured the Cognos user guide and there are warnings about unpredictable ragged hierarchy behaviour but nothing about how to work with them. I get the impression that in the ReportStudio view of the world it would be better if ragged hierarchies didn't exist - but they do and...

Away from ReportStudio for a number of years so a bit rusty. Thought this should be simple but can't see how to do it. Can't see an answer posted. How do I create a set of all the leaf members of a ragged hierarchy? Don't think I can use descendents() as there isn't a named level or a fixed...

Hi John, Thanks for the reply, I've been away for a while so sorry about the delay in getting back to you. You've come up with pretty much with my preferred solution which is to separate the dimensional aspects from the structural. In my mind the dimension table is the bridge table. A...

A bit of a tricky design issue that I hope someone can throw some light on We have dimensions with multiple hierarchies. All hierarchies are set up as level 1 - level 15. In the source data the different hierarchies for a single dimension are held in one table. The hierarchies are...

Just FYI from Transformer 8.4 you can publish a cube as a package in Cognos Connection directly without having to use FM. Just right click on cube and select 'Publish PowerCube as Data Source and Package' - understand that this isn't a lot of help if you're on 8.1 but one for the future eh?

This structure is not going to work in any tool. 1) You've got items being their own parent e.g. orgunitkey 6 has orgunit name of ORG A and a parent of ORG A. 2) Each Org unit has multiple parents and each parent has multiple children i.e. a many-to-many relationship - not a hierarchy...

The other way to do this is to have a table of dates (like a date dimension table) and have a flag column to indicate whether the day is a workday or not, something like: cal_date dow_name is_work_day --------- ------------- ------------ 1/01/2008 Tuesday N 2/01/2008 Wednesday Y 3/01/2008...

Paul, Thanks again for taking the time to respond. I'm still confused (or just a bit slow!) I understand the structure you're suggesting, each product grp has one-and-only-one skey. In your example you used: Product_SK Product_Name ProductGrp_SK ProductGrp_Name ----------...

Firstly, thanks for the responses, very encouraging. I have a problem with MDXer's solution. You say: 'My approach would be to use a group SK that is unique to the group level. In fact this is standard practice for me, ensuring that members at each level are distinct.' I don't see how the...

Hi I'm sure this is something that people have come across before and I would imagine that there must be a range of approaches to dealing with it. I've come up with a potential solution so I'm interested in getting some opinions on the idea. I have facts coming in at different grains, in...

Hi Jean, No need for the SDK, I’ve found that there is an alternative form of burst key that explicitly names the user/user class. For example if the user class in AccessManager is called ‘Project1746’ then the burst key for that user class is given by...