Potential Breaking Change Notice: View-Based API Field Editing Restrictions
Starting August 26, 2025, we’re implementing a security fix that enforces view-level field editing restrictions at the API level when using view-based APIs in a browser session.
What’s Changing:
Grid/Search Views: Fields disabled for inline editing will ignore API updates
Edit Forms: Fields marked as read-only will ignore API updates
Other View Restrictions: All view-level editing restrictions will be enforced via API
Most Likely Impact Scenario: If you have custom code that intentionally updates read-only form fields (for calculated values or complex logic), those updates will be silently ignored after this fix. Required Action: If you’re using custom code to update fields that are disabled for editing at the view level:
Make the field editable in your view settings
Use CSS or JavaScript to hide or disable the field in the UI
Keep your existing custom logic - it will continue to work
Benefits:
Consistent Behavior: API now matches your configured view permissions
Data Integrity: Ensures editing restrictions are universally enforced
**Note: There is no change for API calls which use an API key, because those API calls are fully privileged. **
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Potential Breaking Change: Week 35 (Aug 26): Important Text Formula Fix
We’re fixing a bug where text formula functions incorrectly process certain special characters. This change may affect existing formulas and could require updates to current workarounds. What’s Changing:
left(), right(), and mid() functions will now correctly extract and display %, (, and ) characters
Records containing these specific special characters will display properly in text formulas
No more HTML code fragments (like &#, &# or empty results) for these characters
Potential Impact:
If you currently have workarounds for this specific issue, you may need to update your formulas after the fix.
Text formulas that previously showed HTML fragments for %, (, ) will now display the actual characters
Empty results from formulas with these special characters will start showing the correct values
Affected Functions:
left({field}, number) - extracts characters from the left
right({field}, number) - extracts characters from the right
mid({field}, start, length) - extracts characters from the middle
Important Note: This fix addresses specific character encoding issues with %, (, and ). Text fields containing HTML tags will continue to work as they currently do (e.g., left(‘abc’, 3) will still return a<b). We’re evaluating additional HTML handling improvements for a future update.
Example:
On a new table, add a text formula with the function left({Name}, 2)
Add 3 new records
% as the value in record 1
( as the value in record 2
) as the value in record 3
Expected: The text formula to show the value of the records.
Actual: The text formula is showing the first 2 of the HTML code for the characters. (&#)