Time Intelligence Guru Needed

---

Chthonian wrote:

• What is the best way to set up my data model? 1 Date Table or 3 Date Tables (Ideally, I want to use just 1 date table to allow for filtering/slicing on a field using a “MMM-YYYY” column)

---

If you just want to use a single date slicer then using a single date table is the best approach. The main time I see multiple date tables used in a data model is in situations where people want to produce matrixes with things like Ordered Date on rows and Completed Date on columns.

---

• Is USERELATIONSHIP possible to use when you need to reference 3 separate date fields in the same measure?

 

---

Yes, you would simply call CALCULATE( ...  USERELATIONSHIP() )  on any of the inactive relationships to evaluate an expression using the other relationships. 

---

• Would table variables for each scenario be a better way forward to create my measures?

---

I'm not entirely sure what you are referring to here, but I suspect the answer is "no" as creating inactive relationships and using the CALCULATE( ... , USERELATIONSHIP(...)) pattern would be the preferred approach.