Hello!
Regarding yesterday’s post here:
There were some questions about this, and I am having trouble updating the examples in the changelog post to be more clear so hopefully this post will help:
Potential Breaking Change for Developers & API Consumers (Coming Week 28)
Classic & 
Next-Gen
Connection record values now include additional data attributes in the HTML markup. This affects the format of responses when accessing data via the API or custom scripts that parse the raw HTML.
Current Response:
"field_35": "<span class=\"63d7f6922196c000120686bf\">p2e</span><br /><span class=\"623b8195f1f48f409ad1b6c5\">p1</span>",
"field_35_raw": [
{
"id": "63d7f6922196c000120686bf",
"identifier": "p2e"
},
{
"id": "623b8195f1f48f409ad1b6c5",
"identifier": "p1"
}
]
After the update:
"field_35": "<span class=\"63d7f6922196c000120686bf\" data-kn=\"connection-value\">p2e</span><br /><span class=\"623b8195f1f48f409ad1b6c5\" data-kn=\"connection-value\">p1</span>",
"field_35_raw": [
{
"id": "63d7f6922196c000120686bf",
"identifier": "p2e"
},
{
"id": "623b8195f1f48f409ad1b6c5",
"identifier": "p1"
}
]
Only the field_X field has changed format. The field_X_raw has not changed
If your integration relies on specific HTML structure or length—such as regex parsing, fixed-length string fields in a database, or rendering logic—you may need to update your code to handle the additional data-kn attributes.