If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

[Solved] Building a FM Modell based on 1 relational Table

Started by charon, 27 Nov 2012 03:58:56 PM

Previous topic - Next topic

charon

Hi Guys...another question concerning Cognos 8)
I have one Table (import from csv file), with several informations like name (of customuer), adress, contact, region post zip and more...
what i wanne do is build a package, so i can report against all attributes.

The problem i face is: i have NO facts...what i did is creating a "count (1)" fact, so the number of entries is my fact.
I created dimensions for attributes and a fact table with the count as fact and keys for the dimensions, then i modeled a star schema in FM and puplished it.

And now the issue...my fact in a list or a chart is always the same, like filtering (with a prompt)for the zip code gives me the whole number of entries for that zip code (all customer e.g.), but combining with different dimensions like "It skills" shows me
zip code 4 => 423 Microsoft
zip code 4 => 423 Oracle
Zip Code 4 => 423 IBm
and so on..instead of filtering with a second "´where clausel" it shows me the whole number for the chosen zip code.

I think the problem might be found in my fm model or the tables ive created, but i have no idea...ive TRIED things like set the fact the aggregation mode "calculated" or "sum" and several oither options, but it still does not work.

Anybody an idea what im doin wrong?
Thx guys and...have a nice evening
cheerz :P

MFGF

Hi,

Because all the data is in one table, you don't need to model star schema relationships to get accurate, predictable results. You can still have query subjects that represent star tables, but no relationships or keys are required.

I just tried a similar scenario using some data from a single Excel worksheet. I didn't bring in any measures - just descriptive columns.

I had a Data Source layer containing a single data source query subject based on the spreadsheet. I added nothing to it.
I had a Star layer with model query subjects separating out the different "dimensions" from the columns in the data source query subject
In the Star layer I also created a "Fact" query subject containing a single derived query item with a value of 1. I set the usage of this to Fact and the RegularAggregate property to "Sum". I didn't add any keys or relationships to the Fact query subject.

This seemed to give me the desired results when published into a package.

Cheers!

MF.
Meep!

charon

 ::) Wonderfull, simple and yet so the solution to my problem. Thx a lot sir :)