My Timestamp not showing as a date hierarchy in PowerBI Desktop for Direct Query report...

[jfieck]

Hello all.  I have what I'm pretty confident is a bug in PowerBI desktop.

I am brining in a single value called "createdon" that is a from a postgresql db and the data type is timestamp.

If you look at Transform Data it looks like this:

Note the little datetime icon which I believe indicates it recognizes this as a timestamp object.

Now if you pull this value into a visual you will see the icon indicating time is gone and there is no option to let you convert the date into a hierarchy.

This seems to only expose itself using Direct Query report.  

If I open an "Import" report report and pull in the exact same column you will see the time icon in Transform Data and when you pull into a visual:

Can someone tell me how to report this a bug to Microsoft.  I have tried to find a matching ticket or another post to community on this but have not.  If one is there in an obvious capacity I certainly appologize.  

[Idrissshatila]

Hello @jfieck ,

you can reach out to microsoft support directly through this link https://support.powerbi.com

[ribisht17]

Hi @jfieck 

This is not a bug but limitation with Power BI and it can be seen in the official documentation of Power BI

You can refer to this post https://community.fabric.microsoft.com/t5/Desktop/Direct-Query-issues-with-Date-Hierarchy/m-p/259552...

>>Using DirectQuery in Power BI - Power BI | Microsoft Docs

You can submit and idea here https://ideas.fabric.microsoft.com/ , this can't be post as a bug

Regards,

Ritesh

Mark my post as a solution if it helped you| Munde and Kudis (Ladies and Gentlemen) I like your Kudos!! !!
My YT Channel Dancing With Data !! Connect on Linkedin !! PL 300 Certification Series

[jfieck]

Thanks all.  I read the Why there is no date hierarchy - Microsoft Power BI Community and couldn't really figure out the one-to-one one-to-many or how to change to do whatever it was the article was suggesting was a workaround for this.  From an end user view, my report should function exactly the same using Direct Query versus Import.  I know there are technical implications here but from an end user perspective this is really very frusterating to have to manage manually just because I want to the report fetch newer data.

I do appreciate the feedback and being pointed to clips that at least show MS knows about this.  Thanks much!

[ribisht17]

Great, help the community back by marking the relevant answer here so that it can help others as well

Regards,

Ritesh

Mark my post as a solution if it helped you| Munde and Kudis (Ladies and Gentlemen) I like your Kudos!! !!
My YT Channel Dancing With Data !! Connect on Linkedin !! PL 300 Certification Series