Weekly updates (July 16, 2026)

D&I Support Team

Last Updated: July 16, 2026 21:06

Platform Enhancements

Made an update to how visualizations are displayed in Stories. Story creators now have the ability to default visualizations to either the summary table or the visualization. Previously the only default display option was visualization. This provides users more flexibility in how they want to present information.

Resolved an issue where pie charts were not respecting “(no value)” configurations. Previously, pie charts with this configuration would display “(no value)”. This has been resolved and pie charts now display “false” as expected.
Resolved an issue related to the Story background color picker. Previously the color picker would not allow users to select a color. This has been resolved.
Resolved an issue related to custom metadata configurations. Previously, custom metadata that contained characters such as “/” would prevent users from being able to filter in the catalog. This has been resolved and filtering works as expected.
Resolved accessibility issues with the “Skip to Main Content” button on the Dataset Overview Page. Issues related to focus and screen readability have been addressed.

Fixed an issue where ArcGIS datasets were not fully ingesting all rows when newer ESRI servers limited the number of object IDs returned in a single response. The service now automatically detects when the exceededTransferLimit property is set and fetches additional pages of object IDs until the complete dataset is retrieved.

The legacy SODA1 API (/views/{4x4}/rows or /api/views/{4x4}/rows) will be deprecated starting October 1, 2026.

SODA3 is the new standard for reads.
- SODA2 remains available as well.
The Dataset Management API (DSMAPI), the Producer API, and more are available for writes.

Once deprecated, the removal timeline is TBD, but will be communicated. For the latest timeline updates, please refer to our Deprecation Roadmap.

What this means:

After October 1, 2026, SODA1 endpoints will no longer receive bug fixes or enhancements.
Upon deprecation, the API response will include details of the deprecation and links to migration support.
Tyler will continue to support existing SODA1 functionality during the deprecation period.
All users of SODA1 endpoints should migrate to SODA3 for reads to ensure continued access to data. This includes public uses of Open Data using these endpoints.
All users publishing data using SODA1 should update to a supported ingress method (e.g., DSMAPI).

Migration resources:

If you have questions or would like to discuss your migration, please contact your Client Success Manager.