Good Day!
Asking for help in
Date Difference function.
My concern is
how to get or how to convert Excel formula into PowerApps formula like this
=DATEDIF(StartDate,EndDate+1,"Y")
=DATEDIF(StartDate,EndDate+1,"YM")
=DATEDIF(StartDate,EndDate+1,"MD")
Example (1) :
Start Date: 11/1/2011
End Date: 3/31/2012
and the result should be like this
Year(s) = 0 / Month(s) = 5/ Day(s) = 0
Example (2) :
Start Date: 2/23/2010
End Date: 5/31/2010
and the result should be like this
Year(s) = 0 / Month(s) = 3 / Day(s) = 9
hope you can help me
thanks and advance
Solved! Go to Solution.
Hi @DHAGZ ,
If I'm reading this right, then there's a couple of ways to do it depending on whether you want totals for each unit, or a single duration value. I'll assume you want a single duration value, as totals for each unit is just DateDiff() once for each unit.
DateDiff takes three parameters;
DateDiff(start_date, end_date, UNITS)
where Units can be Years, Quarters, Months, Days, Hours, Minutes, Seconds or Milliseconds. The unit you specify will be the result it returns.
To get a duration, we want to know the difference between two dates, not as a unit, but as a representation of the total Days in Years, Months and Days. To get that, and make sure we're honoring the calendar between the dates, we need to do a couple of steps - working back from years to months and then days, iterating as we go.
First, the logic:
1: Do a straightforward DateDiff for Years
2: Add Years to the start date, so you can then get the remaining months
3: Do a straightforward DateDiff for Months
4: Add Months to the start date so you can get the remaining days
5: Put them all together to get Duration in Years, Months, Days
Then the build:
Put two datepickers on the screen, call the first one start_date and the second one end_date
Then the Expression:
I've spread this out so you can see each step, and I'm using With() to keep all my variables inside the expression, so it looks like a lot and very complicated - but it's actually not. You can probably condense this, and someone cleverer than me can likely show you a shortcut, but here's the formula that worked for me - you can put this into a Text Label Text property:
With({
evarYearsValue: DateDiff(start_date.SelectedDate, end_date.SelectedDate, Years) //get the years between the dates
},
With(
{
evarYearsAddedDate: DateAdd(start_date.SelectedDate, evarYearsValue, Years) //add the years to the start date
},
With(
{
evarMonthsRemainder: DateDiff(evarYearsAddedDate, end_date.SelectedDate, Months) //so you can get the remaining months
},
With(
{
evarMonthsValue: DateDiff(start_date.SelectedDate, end_date.SelectedDate, Months) //Now get the months between the two dates
},
With(
{
evarMonthsAddedDate: DateAdd(start_date.SelectedDate, evarMonthsValue, Months) //add the months to the start date
},
With(
{
evarDaysValue: DateDiff(evarMonthsAddedDate, end_date.SelectedDate, Days) + 1//so you can get the remaining days ---NOTE: +1 if you want to include the final day as a full day
},
"Year(s) =" & evarYearsValue & " / Month(s) = " & evarMonthsValue & " / Day(s) = " & evarDaysValue
))
))
))
Note at the end on the Days - I've added 1 day to the result to include the last day - so if you don't want to include the last day in your calc, then remove the +1.
Hope this helps,
RT
Hi @DHAGZ ,
I spent some time looking at the problem, and there's a catch. Again, I'm really hoping I'm understanding what you're trying to do correctly, but the best way I can explain it is as follows;
Calculating the days between dates is easy - days are a common denominator. Converting a value of days into a duration that reads "n Years, x Months, y Days" that is independent of the calendar is not so easy - here's how I see the problem taking an example of trying to work out the duration between 12th Feb 2020 and the 23rd May 2020;
Hopefully a) this makes sense and b) is not blatantly wrong. This stuff hurts the brain to think on it too long 🙂
So the question is - is this duration what you're trying to achieve?
If so, then the next question is whether the accuracy will be a problem - rounding and dividing by 30 will introduce variance and you'll never be 100% accurate - but that's because you never know what months are involved between two dates - but unless someone has a better idea, it's the best I can come up with.
RT
Hi @DHAGZ ,
Just following up with another stab at a formula that assumes an average of 30 days per month across a year - might be worth a try;
With({totalDays: DateDiff(start_date.SelectedDate, end_date.SelectedDate, Days)+1},
With({totalYears: RoundDown(totalDays/365, 0), remainingDaysFromYearsRollUp: Mod(TotalDays, 365)},
With({MonthsInRemainingDays: RoundDown(remainingDaysFromYearsRollUp/30, 0), remainingDaysFromMonthsRollUp: Mod(remainingDaysFromYearsRollUp, 30)},
totalYears & " years / " & MonthsInRemainingDays & " months / " & remainingDaysFromMonthsRollUp & " days"
)))
Obviously, not all months have 30 days in them, so expect variance depending on your inputs and longer duration between dates.
If you want to try and increase accuracy you can calculate the full calendar months between the two dates by cutting off the start and end date months and just doing a DateDiff on Months in between, factoring in the remaining days afterwards - but this gets quite involved, (you have to figure out if the remaining days on either side also constitute more than a month), so you may want to decide if it's worth the effort before doing it.
At the end of the day, there's no perfect answer that works 100% for all scenarios, so I guess it's about finding something that works for 99% of your scenarios and living with the variance.
Hope this helps,
RT
Hi @DHAGZ ,
If I'm reading this right, then there's a couple of ways to do it depending on whether you want totals for each unit, or a single duration value. I'll assume you want a single duration value, as totals for each unit is just DateDiff() once for each unit.
DateDiff takes three parameters;
DateDiff(start_date, end_date, UNITS)
where Units can be Years, Quarters, Months, Days, Hours, Minutes, Seconds or Milliseconds. The unit you specify will be the result it returns.
To get a duration, we want to know the difference between two dates, not as a unit, but as a representation of the total Days in Years, Months and Days. To get that, and make sure we're honoring the calendar between the dates, we need to do a couple of steps - working back from years to months and then days, iterating as we go.
First, the logic:
1: Do a straightforward DateDiff for Years
2: Add Years to the start date, so you can then get the remaining months
3: Do a straightforward DateDiff for Months
4: Add Months to the start date so you can get the remaining days
5: Put them all together to get Duration in Years, Months, Days
Then the build:
Put two datepickers on the screen, call the first one start_date and the second one end_date
Then the Expression:
I've spread this out so you can see each step, and I'm using With() to keep all my variables inside the expression, so it looks like a lot and very complicated - but it's actually not. You can probably condense this, and someone cleverer than me can likely show you a shortcut, but here's the formula that worked for me - you can put this into a Text Label Text property:
With({
evarYearsValue: DateDiff(start_date.SelectedDate, end_date.SelectedDate, Years) //get the years between the dates
},
With(
{
evarYearsAddedDate: DateAdd(start_date.SelectedDate, evarYearsValue, Years) //add the years to the start date
},
With(
{
evarMonthsRemainder: DateDiff(evarYearsAddedDate, end_date.SelectedDate, Months) //so you can get the remaining months
},
With(
{
evarMonthsValue: DateDiff(start_date.SelectedDate, end_date.SelectedDate, Months) //Now get the months between the two dates
},
With(
{
evarMonthsAddedDate: DateAdd(start_date.SelectedDate, evarMonthsValue, Months) //add the months to the start date
},
With(
{
evarDaysValue: DateDiff(evarMonthsAddedDate, end_date.SelectedDate, Days) + 1//so you can get the remaining days ---NOTE: +1 if you want to include the final day as a full day
},
"Year(s) =" & evarYearsValue & " / Month(s) = " & evarMonthsValue & " / Day(s) = " & evarDaysValue
))
))
))
Note at the end on the Days - I've added 1 day to the result to include the last day - so if you don't want to include the last day in your calc, then remove the +1.
Hope this helps,
RT
Thank you for your Reply @RusselThomas 🙂
Example (2) :
Start Date: 2/23/2010
End Date: 5/31/2010
Year(s) = 0 / Month(s) = 3 / Day(s) = 9
I've got a correct answer
But in
Example (1) :
Start Date: 11/1/2011
End Date: 3/31/2012
Start Date < End Date
and the result should be like this
Year(s) = 0 / Month(s) = 5/ Day(s) = 0
the result is always Year(s) = 1 / Month(s) = 4/ Day(s) = 31
Hi @DHAGZ ,
Too true - I see the problem - rolling over years or months that aren't actually 365 or 30+ days. Instead of coming up with 0 years between 2011 and 2012 when the difference might only be 5 months, it's literally subtracting 2011 from 2012 and coming up with 1 year.
My original approach is flawed, so we might have to take this from the opposite direction - let me think about it and test some outcomes and I'll respond later today 🙂
Kind regards,
RT
🙂 Thankyou Sir @RusselThomas ..
I've try this based on your formula...
and I got the correct Answer
in Y=0 /M=5 /D=0
With({
evarYearsValue: DateDiff(start_date.SelectedDate, end_date.SelectedDate, Years)-1 //get the years between the dates
},
With(
{
evarYearsAddedDate: DateAdd(start_date.SelectedDate, evarYearsValue, Years) //add the years to the start date
},
With(
{
evarMonthsRemainder: DateDiff(evarYearsAddedDate, end_date.SelectedDate, Months)+1 //so you can get the remaining months
},
With(
{
evarMonthsValue: DateDiff(start_date.SelectedDate, end_date.SelectedDate, Months)+1 //Now get the months between the two dates
},
With(
{
evarMonthsAddedDate: DateAdd(start_date.SelectedDate, evarMonthsValue, Months) //add the months to the start date
},
With(
{
evarDaysValue: DateDiff(evarMonthsAddedDate, end_date.SelectedDate, Days)+1//so you can get the remaining days ---NOTE: +1 if you want to include the final day as a full day
},
"Year(s) =" & evarYearsValue & " / Month(s) = " & evarMonthsValue & " / Day(s) = " & evarDaysValue
))
))
))})
But when I try This.
UpdateContext({LSSTHAN:
With({
evarYearsValue1: DateDiff(start_date.SelectedDate, end_date.SelectedDate, Years) //get the years between the dates
},
With(
{
evarYearsAddedDate1: DateAdd(start_date.SelectedDate, evarYearsValue1, Years) //add the years to the start date
},
With(
{
evarMonthsRemainder1: DateDiff(evarYearsAddedDate1, end_date.SelectedDate, Months) //so you can get the remaining months
},
With(
{
evarMonthsValue1: DateDiff(start_date.SelectedDate, end_date.SelectedDate, Months) //Now get the months between the two dates
},
With(
{
evarMonthsAddedDate1: DateAdd(start_date.SelectedDate, evarMonthsValue1, Months) //add the months to the start date
},
With(
{
evarDaysValue1: DateDiff(evarMonthsAddedDate1, end_date.SelectedDate, Days)+1 //so you can get the remaining days ---NOTE: +1 if you want to include the final day as a full day
},
"Year(s) =" & evarYearsValue1 & " / Month(s) = " & evarMonthsValue1 & " / Day(s) = " & evarDaysValue1
))
))
))});
UpdateContext({GRTHAN:
With({
evarYearsValue: DateDiff(start_date.SelectedDate, end_date.SelectedDate, Years)-1 //get the years between the dates
},
With(
{
evarYearsAddedDate: DateAdd(start_date.SelectedDate, evarYearsValue, Years) //add the years to the start date
},
With(
{
evarMonthsRemainder: DateDiff(evarYearsAddedDate, end_date.SelectedDate, Months)+1 //so you can get the remaining months
},
With(
{
evarMonthsValue: DateDiff(start_date.SelectedDate, end_date.SelectedDate, Months)+1 //Now get the months between the two dates
},
With(
{
evarMonthsAddedDate: DateAdd(start_date.SelectedDate, evarMonthsValue, Months) //add the months to the start date
},
With(
{
evarDaysValue: DateDiff(evarMonthsAddedDate, end_date.SelectedDate, Days)+1//so you can get the remaining days ---NOTE: +1 if you want to include the final day as a full day
},
"Year(s) =" & evarYearsValue & " / Month(s) = " & evarMonthsValue & " / Day(s) = " & evarDaysValue
))
))
))});
UpdateContext({Rslt:If(start_date.SelectedDate < end_date.SelectedDate,GRTHAN,
If( start_date.SelectedDate > end_date.SelectedDate ,LSSTHAN
))
})
the Answer is Not Correct.
Hi @DHAGZ ,
I spent some time looking at the problem, and there's a catch. Again, I'm really hoping I'm understanding what you're trying to do correctly, but the best way I can explain it is as follows;
Calculating the days between dates is easy - days are a common denominator. Converting a value of days into a duration that reads "n Years, x Months, y Days" that is independent of the calendar is not so easy - here's how I see the problem taking an example of trying to work out the duration between 12th Feb 2020 and the 23rd May 2020;
Hopefully a) this makes sense and b) is not blatantly wrong. This stuff hurts the brain to think on it too long 🙂
So the question is - is this duration what you're trying to achieve?
If so, then the next question is whether the accuracy will be a problem - rounding and dividing by 30 will introduce variance and you'll never be 100% accurate - but that's because you never know what months are involved between two dates - but unless someone has a better idea, it's the best I can come up with.
RT
Hi @DHAGZ ,
Just following up with another stab at a formula that assumes an average of 30 days per month across a year - might be worth a try;
With({totalDays: DateDiff(start_date.SelectedDate, end_date.SelectedDate, Days)+1},
With({totalYears: RoundDown(totalDays/365, 0), remainingDaysFromYearsRollUp: Mod(TotalDays, 365)},
With({MonthsInRemainingDays: RoundDown(remainingDaysFromYearsRollUp/30, 0), remainingDaysFromMonthsRollUp: Mod(remainingDaysFromYearsRollUp, 30)},
totalYears & " years / " & MonthsInRemainingDays & " months / " & remainingDaysFromMonthsRollUp & " days"
)))
Obviously, not all months have 30 days in them, so expect variance depending on your inputs and longer duration between dates.
If you want to try and increase accuracy you can calculate the full calendar months between the two dates by cutting off the start and end date months and just doing a DateDiff on Months in between, factoring in the remaining days afterwards - but this gets quite involved, (you have to figure out if the remaining days on either side also constitute more than a month), so you may want to decide if it's worth the effort before doing it.
At the end of the day, there's no perfect answer that works 100% for all scenarios, so I guess it's about finding something that works for 99% of your scenarios and living with the variance.
Hope this helps,
RT
I just ran into the same issue.. DATEDIFF() in PowerApps sucks.. plain and simple. It's a flawed function.
You shouldn't have to do work arounds to get the correct results.
This will not work.. as soon as your start comparing days, months, years over a wider span your result will be more and more flawed... especially with leap years and months of 31.
I found expected solution with the below expression:
With({
varYearsValue: DateDiff(startdate.SelectedDate, enddate.SelectedDate,TimeUnit.Years)-1
},
With(
{
varYearsAddedDate: DateAdd(startdate.SelectedDate, varYearsValue,TimeUnit.Years)
},
With(
{
varMonthsRemainder: DateDiff(varYearsAddedDate, enddate.SelectedDate,TimeUnit.Months)
},
With({
varYearsValue:If(varMonthsRemainder>=12,varYearsValue+1,varYearsValue),
varMonthsRemainder:If(varMonthsRemainder>=12,varMonthsRemainder-12,varMonthsRemainder)
},
varYearsValue & "." & varMonthsRemainder
))
)
)
Result :
startdate.SelectedDate =9/30/2020
enddate.SelectedDate=4/1/2023
Ans: 2.7
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
We are excited to announce the Summer of Solutions Challenge! This challenge is kicking off on Monday, June 17th and will run for (4) weeks. The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities. Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”) - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024 Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods. You must enter into each weekly Entry Period separately. How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different. Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers. At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing. Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner. A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random. Individuals will be contacted before the announcement with the opportunity to claim or deny the prize. Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners. Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event. ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE** Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08 23 @WarrenBelz 31 @DBO_DV 10 @Amik 19 AmínAA 6 @mmbr1606 12 @rzuber 4 @happyume 7 @Giraldoj 3@ANB 6 (tie) @SpongYe 6 (tie) Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08 10@WarrenBelz 25 @DBO_DV 6@mmbr1606 14 @AmínAA 4 @Amik 12 @royg 3 @ANB 10 @AllanDeCastro 2 @SunilPashikanti 5 @Michaelfp 2 @FLMike 5 @eduardo_izzo 2 Meekou 2 @rzuber 2 @Velegandla 2 @PowerPlatform-P 2 @Micaiah 2 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8 SunilPashikanti8
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages