Effective Date on New Address

Business Applications Foundation
1

Observation:

When I added an address in the Customers application, I noticed that sometimes the effective date of the new address would be the next business day. For example, if I added an address around 9 pm on Friday, then I might see the effective date set to Monday of the following week.

Question:

Can the effective date rule be configurable? If yes, how? If no, what is the current set of rules around the effective date?

2
  1. When you say you noticed the effective date is the next business day, do you mean when processing transactions, you are being stopped because the address effective date hasn’t yet passed (is in the future, despite having the current date)? Or are you seeing that it actually change to a future date on the record?
  2. What timezone are you in, and if you know, what timezone/locale is your NW operating in?
3

Step 1. Open the Customers Application and navigate to the Addresses tab.

Add an address and the effective date is showing 5/27/2026 (today at 5:20pm PDT).

Screenshot 2026-05-27 at 5.26.41 PM
Screenshot 2026-05-27 at 5.26.41 PM3042×548 73.5 KB

Step 2. Hit Save and Stay

Now you can see the address’s effective date is bumped to tomorrow: 5/28/2026.

Screenshot 2026-05-27 at 5.27.04 PM
Screenshot 2026-05-27 at 5.27.04 PM3048×592 72.5 KB

4

Here is my locale settings:

Screenshot 2026-05-27 at 5.33.48 PM
Screenshot 2026-05-27 at 5.33.48 PM1166×796 60.9 KB

5

I suspect this may be happening because the AddressEffectiveDate data item defaults to Current Date (Today)

image
image1900×1041 44.7 KB

And per help text for that, tenant time zone is used to define what ‘today’ is:

image
image694×207 7.11 KB

So as a Pacific Time user, if you are in an environment whose tenant time zone is Eastern, it would be expected that after 9pm Pacific time the date defaulted will be the next day.

@tyler.pham it seems however that this field should possibly be defaulted differently per the help text.

7

The system stores all Date fields in UTC, and when displaying them, it converts the date based on the applicable time zone. In your case:

  1. Storage: When you enter a Date of 5/27 around 9 PM PST, the system converts this to UTC for storage. Since PST is UTC-7, the stored value becomes 5/28 4:00 AM UTC.

  2. Display: When the system retrieves and displays the date, it converts the stored UTC value back to the tenant’s time zone, which is MST (UTC-6). In MST, 5/28 4:00 AM UTC is converted to 5/28 10:00 PM MST. Since this falls on 5/28, the system displays the date as 5/28 instead of 5/27.

This behavior occurs because the system uses the tenant’s time zone (MST) for display, which is one hour ahead of your browser’s time zone (PST). If you’d like the date to align with your local PST time zone, you can set the Time Zone in your user profile or discuss tenant time zone configurations with your administrator.

@david.lee since the way the data is stored can’t be changed, try setting a custom time zone in your user settings to match your browser’s so that the initial date selection will match what is re-shown to you in the UI.

8

Hi Tyler,

There is a flaw in your UTC to MT conversion. That is, 5/28 4:00 AM UTC should be converted to 5/27 10:00 PM MST. I will try your setting my user profile to PST this evening to see if it would make a difference; I recalled it didn’t when I played with it last time. Thanks.

Regards,

David

9

@tyler.pham, I forgot to tag you on my reply…