#Bug: PBI Time Intelligence Table is Broken

[QC]

Bug: Time table doesn't filter 

Steps to replicate bug: 

1) I created a simple date table which has date hierarchy

2) Added 1 column "_Year" using Dax function Year(xxx)

3) Added date hierarchy to a simple table visual, "_Year" to a simple filter visual

-->> as you can see, when I select year on the filter, it does NOT filter the date hierarchy table below

Please fix asap

----------------------

[Anonymous]

Hi @QC 

Did you test this feature in a previous version? As far as I know, this issue exists in both the April and May versions. The hierarchy can't be filtered by the added time columns unless you add the columns to the corresponding visual.

Also, I don't really understand why you need to create a separate column for filtering, since the time hierarchy itself has the field year. You can just select the field and put it into slicer to do the filtering. Can you provide me with your business scenario and requirements so that I can better handle your problem.

Best Regards,
Community Support Team _ Ailsa Tao

[QC]

Hi Tao, please see my comment below:

" I don't really understand why you need to create a separate column for filtering, since the time hierarchy itself has the field year."

"year" is just an example, it could easily be something else, in complex business analytics a simple time table is not enough, very often we need to create something else, for example, a filter for project milestones, payroll days, leap year, budget period, financial reporting, birthdays, HR days, etc.,.. real business scenarios

"The hierarchy can't be filtered by the added time columns unless you add the columns to the corresponding visual."

This is exactly the issue, it is a big failure by PBI because time intel table should work generically just like another tables, a data column must be able to filter the table, otherwise entire DAX logic breaks down. The app must follow its own logic. There is no MS document indicating time table work differently than others. Again, this is a major failure that MS needs to correct right away. Please discuss w/ your development team, I think they will agree.

[Anonymous]

Hi @QC 

I have submitted this issue to ICM . I will come back with updates if there is any progress .

Best Regards,
Community Support Team _ Ailsa Tao

[QC]

Thank you!

[SMfuss]

Second this one , however for me I used an Older PBIX file and saved as new and no longer worked

[Anonymous]

Hi @QC 

I got a reply from the PG team:

The Core problem is that the hierarchy internally is a different table that has a one way filter relationship with a date table. So the filter on date table can't filter hierarchy.  This is done because the hierarchy might be reused for different dates within model. So they suggested that you could use the year from the hierarchy or change a table to also use calculated columns instead of hierarchy. 

Best Regards,
Community Support Team _ Ailsa Tao