Impacted Areas 69.0
Jan 20, 2026 • 3 minutes to readThis article lists product areas and functions that are affected by the Caspio 69.0 release.
Flex Pivot Report DataPart Headers
What changes were made
Caspio 69.0 introduces a DOM structure update in Flex Pivot Report DataParts that may affect applications using custom HTML, CSS, or JavaScript. Specifically, a new <div> element was introduced that wraps the Pivot Report header container (.DataPartHeader). If your applications rely on specific DOM structures or DOM traversal around the DataPart header, review your custom code and make any necessary updates to ensure continued compatibility after your site is updated to Caspio 69.0. This change may affect custom CSS or JavaScript that assumes the header is a direct child of .DataPartPermissionsWrapper or that navigates to the header using DOM traversal (for example, parentElement, children[index], or similar patterns.
What you should do
If your applications include custom code that targets Caspio-generated markup, review and test your customizations after your site is updated to Caspio 69.0.
Markup changes
Before:
<div class="DataPartContent"> <div class=DataPartPermissionsWrapper> <div class=DataPartHeader>/*header content*/</div> <div>/*pivot content*/</div> </div> </div>
After:
<div class="DataPartContent"> <div class=DataPartPermissionsWrapper> <div><div class=DataPartHeader>/*header content*/</div></div> <div>/*pivot content*/</div> </div> </div>
REST API v3 Date/Time Handling
What changes were made
Caspio 69.0 updates the behavior of REST API v3 when storing date/time-formatted values in Text (255) and Text (64000) data type fields. Previously, if a value resembling a date/time (for example, 2026-12-30T10:00:00) was submitted to a text field, the system could interpret it as a date/time value, apply formatting logic, and adjust it based on time zone. As a result, the stored value could differ from the original input (for example, being converted to 12/30/2026 10:00:00).
With this update, REST API v3 now treats Text (255) and Text (64000) fields strictly as text. Date/time-formatted strings submitted to these fields are stored exactly as received, without conversion, formatting, or time zone adjustment. This change corrects unintended behavior where text fields were implicitly processed as date/time fields.
What you should do
If your integrations rely on REST API v3 to store date/time-formatted strings in Text (255) or Text (64000) data type fields, review how your applications process these values after storage.
If you previously depended on Caspio’s automatic date/time interpretation or time zone adjustment when writing to text fields, update your integration logic accordingly. After your site is updated, test any integrations or processes that read or manipulate these text field values to ensure they continue to function as expected.
