Wrong data binding on dropping card (During Card Rendered event)

[Taras Sokha]

Hi, currently working on my pet project and faced an issue. After i dropping card into another column i have wrong data properties to be set.

Example of my data source:
[{

    "id": 380,

    "createdAt": "2025-11-21T16:26:25.174865Z",

    "createdBy": {

        "id": 1030,

        "uuid": null,

        "mainUserId": null,

        "firstName": "Taisiia",

        "lastName": "Mykolenko",

        "patronymic": "Patronymic"

    },

    "commentsCount": 0,

    "candidateSource": {

        "id": 1180,

        "name": "TALENT_SOURCING",

        "displayName": "Talent Sourcing"

    },

    "activeStage": null,

    "candidateInformation": {

        "fullName": "New 4",

        "email": "[email protected]",

        "phone": null,

        "location": null,

        "linkedIn": null

    },

    "applicationAttachments": {

        "portfolioLink": null,

        "coverLetter": null,

        "cvFile": null

    },

    "employmentDetails": {

        "expectedCompensation": null,

        "expectedStuffingTime": null

    },

    "stageKey": "1766",

    "stage": {

        "id": 1770,

        "displayName": "Applied",

        "displayOrder": 0,

        "isApplicationStage": true,

        "color": {

            "name": "LIGHT_BLUE",

            "textColor": "#6790EF",

            "backgroundColor": "#D9E3F8"

        },

        "stageActions": [],

        "localizations": null

    },

    "expanded": false

}]

Pay attention to 'New 4' card:


After dragging it into next('Interviewing') column it looks next:


This is because(i guess) when data should be updated and our keyField should be updated, we get only new stageKey, not whole object(as it was in example of my data source) with updated stageKey

Attachment: image_4_240684fa.png

[Taras Sokha]

In data source changed event situation is the same

[Vinitha Jeyakumar]

Hi Taras Sokha,

Currently, the Kanban component does not have support for complex data binding. However, we have considered this requirement as a feature request. Now you can track the status of the feature in the below feedback link.

Feedback: https://www.syncfusion.com/feedback/33303/need-to-provide-complex-data-binding-support-on-kanban-board

The above feature will be implemented in any one of the future volume releases. Generally, we will plan the feature implementation based on the customer request count, feature rank, and wishlist plan. You can upvote the feature request feedback so that it gets support and will be ranked higher for implementation.

[Taras Sokha]

Btw my issue was resolved with adding headerField to cardSettins (i've skipped it occasionally).

[Vinitha Jeyakumar]

Hi Taras Sokha,

We are glad that your issue has been resolved, and we would like to inform you that  the headerField property of cardSettings is mandatory to render the cards in the Kanban board. It acts as a unique field that is used to avoid the duplication of card data. You can not change the headerField of the mapped data value using the updateCard public method or server-side update of data.