You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi
This could be a setting I've missed somewhere but the standard Format String selections appear to be at odds with the standard in Power BI Desktop when it comes to dates, certainly the non-US dates at least. In TE3, "dd/mm/yyyy" is only possible as a custom format, but in Desktop, this is a standard selection; choosing the TE3 option of "dd/MM/yyyy" is regarded by PBI Desktop to be a custom format. Both ways appear okay when dragged on to a report page, so this isn't a very severe bug - just an irritation!
The text was updated successfully, but these errors were encountered:
This is due to a difference in the way that DAX and c# format strings work (TE3 is written in c#)
C#
DAX
Description
mm
nn
Minutes
MM
mm / MM
Months
in C# the uppercase M is different to the lowercase m so TE3 probably needs to translate these when generating the examples. I'd stick with "dd/mm/yyyy" and put up with the incorrect example until this gets fixed.
Hi
This could be a setting I've missed somewhere but the standard Format String selections appear to be at odds with the standard in Power BI Desktop when it comes to dates, certainly the non-US dates at least. In TE3, "dd/mm/yyyy" is only possible as a custom format, but in Desktop, this is a standard selection; choosing the TE3 option of "dd/MM/yyyy" is regarded by PBI Desktop to be a custom format. Both ways appear okay when dragged on to a report page, so this isn't a very severe bug - just an irritation!
The text was updated successfully, but these errors were encountered: