Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
JamesMidgley
Frequent Visitor

date hierarchy reverted to simply date upon new data upload

I have successfully created a number of reports which use a common Date table.  Until this morning, when I introduced a new data set to my model, all my reports allowed drill down from Year, to Qtr to Month.  I did not create this hierarchy it merely existed in my model. 

 

Now having introduced this new dataset, which I linked with the Date table (which enabled my drill down), I find that my date hierarchy is no more and all the reports that previously had a hierarchical nature now do not support drill down they merely show date.

 

Can someone explain this phenomenon and enlighten me as to what has happened?

1 ACCEPTED SOLUTION

@v-yuezhe-msft Thanks for your message.

 

I have, through some level of head banging, managed to resolve my issue.

 

As best as I can describe it....In introducing my new Change Management table and linking it's Date field with the Date field in my Date table, the relationship that was formed (which I stupidly did not verify) caused the change previously described. 

 

The relationship implemented was Date.Date to Change Mangement.Date (Cardinality: One to One with cross filter direction of Both

The relationship I desired was Change Management. Date  to Date.Date (Cardinality: Many to One) with cross filter direction of Single.

 

Thanks

View solution in original post

2 REPLIES 2
v-yuezhe-msft
Employee
Employee

@JamesMidgley,

Do you use the Date field of Data table to create visuals in Power BI Desktop? Could you please share sample data of existing tables and the new table for us to analyze?

Regards,
Lydia

Community Support Team _ Lydia Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

@v-yuezhe-msft Thanks for your message.

 

I have, through some level of head banging, managed to resolve my issue.

 

As best as I can describe it....In introducing my new Change Management table and linking it's Date field with the Date field in my Date table, the relationship that was formed (which I stupidly did not verify) caused the change previously described. 

 

The relationship implemented was Date.Date to Change Mangement.Date (Cardinality: One to One with cross filter direction of Both

The relationship I desired was Change Management. Date  to Date.Date (Cardinality: Many to One) with cross filter direction of Single.

 

Thanks

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.