Subscription Date Calculation Issue
VIDEO TRANSCRIPT | Recorded: 2025-08-07 | Verify against current system state
Abstract¶
Demonstration of a subscription date calculation issue in Salesforce during bulk historical order import. When creating an order with a fulfillment date after a membership gap (e.g., member expired in 2007, rejoins in 2009), the subscription start date incorrectly calculates as the day after the previous subscription end date rather than using the specified fulfillment date. This affects historical data migration where members had gaps in their membership.
Key Procedures¶
- Create test account (Subtest04)
- Create order with historical fulfillment date (8/1/2006)
- Add NP membership, complete with cash payment
- Verify subscription dates: start 8/1, end 7/31, grace 8/31
- Manually update person record: status to expired, member type, initial join date
- Create second order with later fulfillment date (8/1/2009)
- Observe subscription incorrectly starts 8/1/2007 instead of 8/1/2009
Notable Statements¶
- 0:00:11 "I have started a new order. I've set the order to start the fulfillment date of 8.1.2006."
- 0:01:07 "At this point, I still shouldn't be a member, but I should have subscriptions."
- 0:02:01 "I don't know at this point if I should change the member status to expired."
- 0:05:42 "So that's the issue here. It's starting on 2007 and ending 2008, but that's not the fulfillment date."
- 0:05:54 "What's happening is the subscription record is getting created and then bumped up to the last known subscription date."
- 0:06:08 "Even though I put that fulfillment date in of a later date, it just bumped the next start date to the day after."
Systems & Configurations¶
Systems Mentioned¶
- Salesforce (Orders, Subscriptions, Person Accounts)
Specific Configurations¶
| Item | Value/Setting | Timestamp | Notes |
|---|---|---|---|
| Test Account | Subtest04 | 0:00:04 | For reproduction |
| First Order Fulfillment | 8/1/2006 | 0:00:14 | Historical date |
| First Sub Start | 8/1/2006 | 0:01:34 | Correct |
| First Sub End | 7/31/2007 | 0:01:34 | Correct |
| Second Order Fulfillment | 8/1/2009 | 0:04:47 | After gap |
| Second Sub Start (Actual) | 8/1/2007 | 0:05:44 | Incorrect - should be 2009 |
| Second Sub End (Actual) | 7/31/2008 | 0:05:44 | Incorrect |
Credentials/Access Mentioned¶
- Salesforce admin access for manual field updates
Errors & Troubleshooting¶
- Issue: Subscription start date ignores fulfillment date after gap
- Cause: System calculates next subscription from last end date regardless of fulfillment date
- Resolution: Issue identified - needs development partner review
-
Timestamp: 0:05:54
-
Issue: Person record fields not auto-populated from order
- Cause: Bulk import process doesn't trigger all automations
- Resolution: Manual update of membership status, type, dates required
- Timestamp: 0:02:23
Transcript Gaps & Quality Notes¶
- Bug reproduction demonstration for development team
- First attempt in previous session didn't include manual field updates
- Affects historical data migration with membership gaps
- Need to communicate issue to development partner