Fact table with multiple datefields, yet no foreign key datekey in it for dim_date table's datekey

[ioannaiogr]

Hi all,

pretty much the subject is the problem. Sorry for the confusing description

I have a fact table with lots of different date fields. But there is no datekey as foreign key to the date dimension table.

In that dim_date dimension table there are fields such as datekey ( 20100101, 20100102 and so on), Date (01/01/2010, 02/01/2010 etc), WholeYear like 2010-2011, 2011-2012 etc.

I want the analysis by wholeYear but my problem is, i don't know to which date in fact table I should connect it. I need a datekey like 20100101, don't I?

Can I create one such? To me it looks like I just have to pick for which of all the dates in the fact table I want to consider a WholeYear field.

I've gotten pretty frustrated with this one; Should I do a date bridge?

⚠️

Please share your wisdom with me 👨‍💻👩‍💻

[rwunderlich]

I recommend a data bridge where you will generate the datekey. See this for an example:

Qlikview Cookbook: Tutorial - Using Common Date Dimensions https://qlikviewcookbook.com/recipes/download-info/tutorial-using-common-date-dimensions/

-Rob
http://www.easyqlik.com
http://masterssummit.com
http://qlikviewcookbook.com