Forum Discussion
Date Column Shows Time in Power BI Report Even After Converting to Date in Dataflow Gen2 (Fabric)
Hi everyone,
I’m working with Microsoft Fabric and using Dataflow Gen2 to transform my data. I have a recorded_date column that originally contains both date and time. In the transformation steps, I’ve explicitly changed the data type from datetime to date using the following step:
In the Dataflow preview, the column correctly shows only the date (e.g., 12/17/2010). However, once the data is loaded into the Power BI report side, the same column displays the time part as well (e.g., 12/17/2010 12:00:00 AM), even though the datatype was set to date.
I’d like to show only the date portion in the report without the time. Has anyone faced a similar issue or knows how to fix this?
Thanks in advance!
Hi Parth_1 ,
Thank you for reaching out to Microsoft Fabric Community.
In Power BI Service, the experience is different from Power BI Desktop. In Power BI Desktop you have full control over editing measures, applying formatting and performing calculations directly within the report or data model. However in Power BI Service (or Fabric), that flexibility is more limited. While you can interact with and view reports in the Service, editing measures, formatting them, or applying specific measure tools (like rounding) is typically only possible in Power BI Desktop. To make any changes to measures or calculations in Power BI Service, you would need to first make those changes in Power BI Desktop and then republish the updated model to the Service.
Regarding the issue of not being able to create a new column in your existing table, this is also linked to the environment settings. In Power BI Desktop you can easily create calculated columns because you are directly working with the data model. But in Power BI Service creating new calculated columns is generally not allowed unless you are working in a Premium capacity workspace or the model has been configured to allow this in the service. To enable this functionality you will need the appropriate permissions and the dataset must be set up to allow changes. Without these creating calculated columns directly in Power BI Service won’t be possible.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thank you!!
5 Replies
There is no "date" data type in Semantic Models. Everything is always datetime. "date" is only a formatting choice.
Hi lbendlin,
Really appreciate your quick turnaround.
I am trying to perform some calculations with same semantic model, In that I am facing some issues.
1.Unable to view measure tools setting
Case : I want to roundup the value of my KPI which highlighted here , In desktop we are having option to edit the measure also some formatting setting in Measure tool , but in fabric I am unable to view that setting.
Whereas In desktop I am able to access the measure tools setting.
2. Can't able to create new column in my existing table
I am trying to create one calculated column in existing table but the option is disabled.
Thank you once again for your swift and kind responseYou mentioned DF Gen2. What exactly are you connecting to here? The Default Semantic model of the data warehouse?
Hi Parth_1 ,
Thank you for reaching out to Microsoft Fabric Community.
In Power BI Service, the experience is different from Power BI Desktop. In Power BI Desktop you have full control over editing measures, applying formatting and performing calculations directly within the report or data model. However in Power BI Service (or Fabric), that flexibility is more limited. While you can interact with and view reports in the Service, editing measures, formatting them, or applying specific measure tools (like rounding) is typically only possible in Power BI Desktop. To make any changes to measures or calculations in Power BI Service, you would need to first make those changes in Power BI Desktop and then republish the updated model to the Service.
Regarding the issue of not being able to create a new column in your existing table, this is also linked to the environment settings. In Power BI Desktop you can easily create calculated columns because you are directly working with the data model. But in Power BI Service creating new calculated columns is generally not allowed unless you are working in a Premium capacity workspace or the model has been configured to allow this in the service. To enable this functionality you will need the appropriate permissions and the dataset must be set up to allow changes. Without these creating calculated columns directly in Power BI Service won’t be possible.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thank you!!
Hi lbendlin,
With reference to my initial message, I have my JSON files stored in the Lakehouse. I performed the data transformation using Dataflow Gen2, and after completing the transformation, I saved the transformed data back to the Lakehouse. This is the process I have followed in my case.
