v0.1.80 — 12 Jun 2026
Bug Fix — Content Detail forms now handle numeric, non-PK M2O, and input-code values correctly
Who is affected: Users editing records in Platform Studio Content Detail
pages where fields include numeric inputs, M2O relations keyed by non-primary
columns (for example resource_uri), or input-code interfaces for JSON/CSV.
What was wrong
- Numeric values could be treated as string-only in parts of the input mapping.
- M2O dropdown resolution assumed primary-key based lookup and could fail for non-PK target columns.
input-codehandling for non-string/structured values was inconsistent, which could produce incorrect payload values.
What changed
- Input mapping now preserves numeric behavior instead of forcing string-only assumptions.
- M2O lookup/selection now supports filter-based resolution for non-PK targets.
input-codenow normalizes non-string input and emits parsed JSON for structured values where applicable.
Before / After
| Scenario | Before this fix | After this fix |
|---|---|---|
| Numeric field editing in Content Detail | ❌ Could be coerced through string-only mapping | ✅ Correct numeric-aware handling |
| M2O keyed by non-PK column | ❌ Selection/lookup could fail | ✅ Filter-based non-PK lookup works |
Structured JSON in input-code | ❌ Inconsistent emitted values | ✅ Normalized + correctly parsed payload |
Last updated on