Forum Discussion
Advocate IIIDate Dimension Model Relationship Woes
You have to do one of the two:
- Either you link the date to the MktOpportunity instead of linking it to MktCalendar; or- You apply to the relationship between MktOpportunity and MktCalendar the both way relatioship and should work fine.
Hope it fixes it, let me know.
Best Regards,
DR
Are you using the date table field to slice or a date from any of the tables?
BR,
DR
Advocate IIIAnonymous
I've been using a date from any of the tables. That's probably my issue since I have done this successfully before, but the multiple dates available are throwing me off. If I use one from the date dimension table, wouldn't I need to link it to the other date fields?
Assuming you have a date for the MktOportunity (when it was created I assume) and with the bidirectional relationship pointing to the same MktOpportunity but when its released (MktCalendar).
So if you filter by the date field in opportunities it will show the mkt opportunities created in that range not the releases.
If you wanna filter by both dates you should turn that relationship into one-sided and create two date tables, one for the marketing oppportunity date and one for MktCalendar.
Can you explain what's the goal so it can be easier to help you?
BR,
DR
- lbudack
It's starting to make a little more sense now. My goal is to be able to filter both tables together by a common date, such as the CreateDate, to compare the two counts. (Sample visualization attached. Activites come from the MktCalendar table, and the Outcome comes from the MktOpportunity table. The columns change if I pick a create date filter from either table which is why I can tell it's not working quite right.)
In theory what you're filtering are all mkt opportunities created in a certain date and it filters both because of the bi directional relationship, so it doesnt happen you can turn the relationship onesided but then it will only filter (if you use the date table created) by the table you have date table connected to.
I don't think there's anything wrong with you're model, it's a matter to know the context in which you need to see the data.
BR,
DR