# Daylight Saving Time Issue Updating Custom Date Field via XML-RPC Using Infusionsoft SDK

**URL:** <https://integration.keap.com/t/daylight-saving-time-issue-updating-custom-date-field-via-xml-rpc-using-infusionsoft-sdk/93635>\
**Category:** API Q&A\
**Tags:** api\
**Created:** [April 11, 2025, 5:54pm UTC](https://integration.keap.com/t/daylight-saving-time-issue-updating-custom-date-field-via-xml-rpc-using-infusionsoft-sdk/93635 "2025-04-11T17:54:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fady\_khateeb](https://avatars.discourse-cdn.com/v4/letter/f/13edae/32.png) [@Fady\_khateeb](https://integration.keap.com/u/Fady_khateeb)\
**Post date:** [April 11, 2025, 5:54pm UTC](https://integration.keap.com/t/daylight-saving-time-issue-updating-custom-date-field-via-xml-rpc-using-infusionsoft-sdk/93635/1 "2025-04-11T17:54:40Z")

</div>

Hello Keap Team,

We are using the Infusionsoft SDK to update a custom date field (\_LMILastLogin) via XML-RPC, but we are encountering the following error:

Error: Failed to invoke method load in class com.infusionsoft.api.xmlrpc.XmlRpcContactService: java.sql.SQLException: HOUR\_OF\_DAY: 2 → 3

The SDK handles the XML formatting, so we have no control over how the date is structured in the payload. If the SDK does not modify the format, how should we proceed?

Is this issue related to time zone handling or daylight saving time (DST) in Keap’s backend? Any insights or solutions would be appreciated.

Thank you!

---

<div class="post-metadata">

**Author:** ![Marion\_Dorsett2](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/marion_dorsett2/32/14894_2.png) [@Marion\_Dorsett2](https://integration.keap.com/u/Marion_Dorsett2)\
**Post date:** [April 12, 2025, 1:07pm UTC](https://integration.keap.com/t/daylight-saving-time-issue-updating-custom-date-field-via-xml-rpc-using-infusionsoft-sdk/93635/2 "2025-04-12T13:07:47Z")

</div>

@Fady_khateeb try passing the date to the API using the following format:

```auto
Ymd\TH:i:s

```

The result should look something like this:  
20250412T09:05:00

It’s possible that the format of the date you’re passing into the API isn’t being parsed correctly, and throwing the error.
