is there a way to get the "AddMonths" expression to recognize what month it is and actually add the correct number of days? trying to get this to fire on last day of month and then update a KW in a Unity form to reflect the next due date (last day of next month) but it just adds 30 days 😞 see image...should be 7/31/22. every month WF will send out a reminder based off date in Unity form and then it needs to update that KW in the form to the next month and wait til timer fires again
1 ACCEPTED ANSWER
I recommend an expression closer to this:
AddDays(AddMonths(AddDays(%VPropDate;1-Day(%VPropDate));2);-1)
You could replace the %VPropDate with Now(), but this expression preserves the time component of the date, so you'll get the last day of next month at the current time (plus or minus an hour if there's a DST transition one direction or another between the current date and the last day of next month). If you don't want that, I recommend keeping %VPropDate and adding a Set Property to Expression that sets %VPropDate to this:
Date(Year(Now());Month(Now());Day(Now()))
And then put that Set Property to Expression right before the Set Property to Expression action that calculates the last day of next month. You could technically put it all into one big expression:
AddDays(AddMonths(AddDays(Date(Year(Now());Month(Now());Day(Now()));1-Day(Date(Year(Now());Month(Now());Day(Now()))));2);-1)
But I consider that near impossible to read. If you split it into two steps, you can name them something clear like "Put current date into %VPropDate" and "Calculate Last day of Month after %VPropDate" which is easier to understand when you look at the workflow later!
Making progress, I must be missing something. I setup both Expressions and they appear to work correctly but the KW isnt updating. any ideas?
this is what I'm doing...can ignore first two Actions :
