Forum Discussion
MONTH() function shows peculiar results
- 9 years ago
Hi MFelix,
Yes, the PBI Regional settings do influence the outcome of dates, but not in this case. I have changed to Regional setting from Dutch to English UK and the outcome of 2a,b,c,d were the same. It seems Month() will take any date, with or without double quotes ("), but it will provide a correct answer when in quotes. However it seems to interpret the Dutch date "8-2-2017" (8th of February) as the 2nd of August, similar to the UK/US format "8/2/2017".
What it calculates in 2a and 2b I don't know.
3 and 4 work if you use the [Actual date] in the example without the [.Month] and use "MMM" and "MM" as format strings.
Lessons learned here (at least for me):
- Be aware when using MONTH() and FORMAT() with dates. They will accept any date format, but the outcome is not always what you expect.
- Check the field calculation settings and make sure it is set to "Don't summarize".
- And last: beware of the Regional settings in PBI Desktop.
Thanks for yor help!
Bye,
Rudi
Hi, my first impression is the table is aggreating the months. Actual date is Unique row or several?
- rudiklein9 years agoAdvocate III
Hi Vvelarde,
You are right. The month numbers that came from the table were summed. The field was set to "SUM". I overlook that.
That partially fixed my example table. Some of the fields were still strange ;looking, but that is explaned in my reply to MFelix.
Thanks for your help.
Rudi