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

The ultimate Microsoft Fabric, Power BI, Azure AI & SQL learning event! Join us in Las Vegas from March 26-28, 2024. Use code MSCUST for a $100 discount. Register Now

New Member

Dashboard in PBI Service deformats measures related to DAX TODAY() while refreshing in shared area

I have a Dashboard published in the company's Power BI Server Workspace, and whenever I refresh it in Power BI Desktop everything works well. However whenever it is refreshed in Power BI Service, 2 measures that are related to DATE context, get deformated. Also, when I publish in my personal area in PBI Service it refreshes well without no problem, only deformats in company's shared area.


My personal area:


Company shared area with deformatted values (measure UC 2022 and UC 2021, that impact the rest):




From reading in multiple other threads it can be related to date format, date timezone of Power BI Desktop and Power BI Service, however even after trying to fix with the possible solutions it isn't working (still deformats measure).

I'm living in UTC timezone (Working in Lisbon) so when refreshing in Power Service the DAX Measure TODAY() still retrieves the exact same value from the value in Power BI Desktop.


I've also tried grabbing the date from Power query using the DAX DateTime.Now() since supposedly (i think) there's no need to change the TimeZone. However even with that measure, it still deformats.


I have the measure 1.0_Período Corrente which is given by:













1.0_Período Corrente = LOOKUPVALUE( Date_Table[Period], Date_Table[Current_Day], "Current Day" )














where Date_Table has this format:



Current_Day column was created with:













Current_Day = 
    YEAR(Date_Table[Date Day]) = YEAR(TODAY()) && MONTH(Date_Table[Date Day]) = MONTH(TODAY()) && DAY(Date_Table[Date Day]) = DAY(TODAY()),
    "Current Day",
    "Other Day"














This is the measure that deformats:














UC 2022 T = IF(
    SELECTEDVALUE(Calendario[Periodo]) = VALUE([1.0_Período Corrente]),
    CALCULATE(SUM(Vendas[CU]),  FILTER( Dias, Dias[Dias]<= [1.3.1_Último Dia])),














where [1.3.1_Ultimo Dia]  corresponds  to:














1.3.1_Último Dia = 
    LOOKUPVALUE('Date_Table'[Period],Date_Table[Date Day],TODAY()) <=  VALUE('Medidas GJ'[1.0_Período Corrente]),
    LOOKUPVALUE('Date_Table'[Fecha],Date_Table[Date Day],TODAY()),
    CALCULATE(MAX ('Date_Table'[Fecha]),FILTER('Date_Table','Date_Table'[Period]= VALUE('Medidas GJ'[1.0_Período Corrente])))















I'd highly appreciate your help sinceI can't figure out what else to do !  

Community Support
Community Support

Hi @GoncaloJ ,

I suspect that it is caused by the difference in time zones. Power BI service operates in the UTC time zone, and evaluates all locale based time functions in that time zone. Power BI Desktop evaluates them according to the locale of the user.

A workaround is to use a fuction such as NOW()+TIME(8,0,0).

Thanks for your efforts & time in advance.


Best regards,
Community Support Team_Binbin Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Fabric Community Conference

Microsoft Fabric Community Conference

Join us at our first-ever Microsoft Fabric Community Conference, March 26-28, 2024 in Las Vegas with 100+ sessions by community experts and Microsoft engineering.

February 2024 Update Carousel

Power BI Monthly Update - February 2024

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

Fabric Career Hub

Microsoft Fabric Career Hub

Explore career paths and learn resources in Fabric.

Fabric Partner Community

Microsoft Fabric Partner Community

Engage with the Fabric engineering team, hear of product updates, business opportunities, and resources in the Fabric Partner Community.

Top Solution Authors
Top Kudoed Authors