-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expiration Date Calculations Required for MVP #83
Comments
We have two schemes, one that uses logic from 2, and another that uses logic May 1- April 30 (our fiscal year is April 1 - March 31) Here are my flow calculations if they help understand the logic. Start Date: End Date: |
In one use case I have (and not listed above), the membership is Dec 31 of the current year. However, if they pay after October 1, the expiration date becomes Dec 31 of the following year. |
I have something similar. With annual start date 1st May, paying April to
Feb is this year but March is counted as next year.
…On Wed, 29 Mar 2023, 20:19 Kathy-Waterworth, ***@***.***> wrote:
In one use case I have (and not listed above), the membership is Dec 31 of
the current year. However, if they pay after October 1, the expiration date
becomes Dec 31 of the following year.
This is part of the formula used in a flow for this calculation:
IF(
MONTH ({!$Flow.CurrentDate} ) < 10,
DATE(YEAR({!$Flow.CurrentDate}), 12,31),
DATE((YEAR({!$Flow.CurrentDate})+1),12,31))
—
Reply to this email directly, view it on GitHub
<#83 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUMH7IG574BF74GC5SDJLX3W6SDNBANCNFSM6AAAAAAVSZIC5Y>
.
You are receiving this because you commented.Message ID:
<SFDO-Community-Sprints/MembershipSchemaAndBenefits/issues/83/1489170302@
github.com>
|
I have a client with a similar business rule. This will help.
On Wed, Mar 29, 2023 at 16:24 DebbieN-SF ***@***.***> wrote:
I have something similar. With annual start date 1st May, paying April to
Feb is this year but March is counted as next year.
On Wed, 29 Mar 2023, 20:19 Kathy-Waterworth, ***@***.***>
wrote:
> In one use case I have (and not listed above), the membership is Dec 31
of
> the current year. However, if they pay after October 1, the expiration
date
> becomes Dec 31 of the following year.
> This is part of the formula used in a flow for this calculation:
> IF(
> MONTH ({!$Flow.CurrentDate} ) < 10,
> DATE(YEAR({!$Flow.CurrentDate}), 12,31),
> DATE((YEAR({!$Flow.CurrentDate})+1),12,31))
>
> —
> Reply to this email directly, view it on GitHub
> <
#83 (comment)
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AUMH7IG574BF74GC5SDJLX3W6SDNBANCNFSM6AAAAAAVSZIC5Y
>
> .
> You are receiving this because you commented.Message ID:
> <SFDO-Community-Sprints/MembershipSchemaAndBenefits/issues/83/1489170302@
> github.com>
>
—
Reply to this email directly, view it on GitHub
<#83 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXDC7UD26WAZBS4FBG55MDLW6SR7DANCNFSM6AAAAAAVSZIC5Y>
.
You are receiving this because you authored the thread.Message ID:
<SFDO-Community-Sprints/MembershipSchemaAndBenefits/issues/83/1489346030@
github.com>
--
T. Ward
|
What are the most common scenarios for organizations calculating expiration dates and which of those scenarios should be included in an MVP?
Examples:
*Considerations needed for Feb. 29/leap years
The text was updated successfully, but these errors were encountered: