In SAS Customer Intelligence Studio, the set time is changed, incorrectly, in a campaign when time values in a user-defined format are used in the campaign. This problem occurs when you perform steps similar to the following:

1. Create a campaign definition with a user-defined datetime range and time-range values in the custom details.
2. Create a new campaign with the campaign definition.
3. Set values for the user-defined datetime and time ranges.
4. Save and close the campaign.
5. Re-open the campaign and verify whether the datetime and time values are the expected values.

After this last step, you can see that the values shift +9 hours for a local Japanese locale, and they shift -4 hours for an Eastern Standard Time (EST) local instance.

Note: A similar problem exists for the SAS^® Customer Intelligence Common Data Model. For details, see SAS Note 61010, "Incorrect values are stored for the common data model when it is used in a SAS Customer Intelligence Studio campaign."

The solution removes the conversion of the user-defined time value to UTC so that the time entered in the interface is the value that is stored only for time fields in custom details. For details, see SAS Note 61150, "Time-range prompts in SAS® Customer Intelligence Studio custom details do not handle validation properly for different time zones."

The workaround for this issue is to use a datetime range instead of a time range.

Click the Hot Fix tab in this note to access the hot fix for the issue.

For existing campaigns, you need to open and manually update any custom details that contain date, datetime, or time values to the correct time. When you open an existing campaign, the time shifts to your local time as a result of a shift away from conversion to UTC. To correct existing campaigns, follow these steps: 

1. Open the existing campaign.
2. Open the custom details that contain date, datetime, or time values.
3. Update the fields to the values that you want.
4. Save the campaign.

Operating System and Release Information

A fix for this issue for SAS Marketing Automation 6.5 is available at:

A fix for this issue for SAS Marketing Automation 6.4 is available at:

A fix for this issue for SAS Marketing Automation 6.3 is available at: