Adding 1 month to some dates seems to work. Often however it doesn't work. this needs to be fixed.
Thanks for your feedback, I have made a test and the issue is confirmed on my side. It seems that adding 1 month to some dates is based on 31 days (1 Month=31 Days), adding multiple months to some dates is based on 30 days (1 Month=30Days).
I would post this issue to my product team, if this issue is solved, I would reply here.
I'd like to echo @Pieter_Veenstra's diagnosis of this problem, I'm experiencing the same issue. I would think adding any number of months to a date would leave the day attribute of the date as-is, but adjust the month and, if necessary, the year.
This has been driving me crazy as well, and I believe it should continue to be a bug as the desired normal functionality is not working as expected.
That being said, I do believe I have found the reason behind the inconsistency and possible methods to fix this. This method is expected to take the input of interval and add that number of months to the current date, however through initial testing, the actual functionality takes the interval input and adds the number of days in the month corresponding to that number and adds it to the date. So if the interval is 1 it adds 31 because 1=January, 2 would be 28 because 2=February, 3 would be 31 because 3=March and so on and so on.
Here is the output data from tests run with the starting date of 05/10/2018:
|Interval||Date Output||Difference in Days|
I've now found a worksround for this month issue:
Just go the same issue to go back one month. A flow runned today and substracted 31 days. Instead of getting February, I got January. Annoying...
Is there something done for that bug?
@v-xida-msft Are there any updates on this bug? We are being encouraged to use Flow to replace Dynamics 365 processes, but this is a critical function for our system. When I add 1 month to September 1, I'm getting October 2.