Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Issue with grouped grids and displayField behavior

    SmartClient Version: v13.1p_2026-02-08/Enterprise Deployment (built 2026-02-08)

    Hi, I’m encountering a regression in the behavior of grouped grids.
    It seems that when a displayField is present on the grouping field, the getGroupTitle method is no longer called.

    Please try the test case in the SQLlargeValueMapSQL example of the showcase and try grouping on the “Item name” column, you’ll see that getGroupTitle is not called:

    Code:
    isc.ListGrid.create({
        ID: "orderItemList",
        width: 700, height: 224,
        dataSource: largeValueMap_orderItem,
        fields: [
            {name: "orderID"},
            {
                name: "itemID", title: "Item Name", align: "left", width: "50%",
                displayField: "itemName", editorType: "SelectItem", filterEditorType: "ComboBoxItem",
                getGroupTitle: function (groupValue, groupNode, field, fieldName, grid) {
                    isc.logEcho("not called")
                    return "not called";
                },
                filterEditorProperties: {optionDataSource: "supplyItem"}
            },
            {name: "quantity"},
            {name: "unitPrice"}
        ],
        autoFetchData: true,
        canEdit: true,
        showFilterEditor: true
    });

    #2
    Thanks for the clear test case! You're right that the displayField setting should not have caused your getGroupTitle() override to be ignored - this is fixed for tomorrow's build.

    Comment


      #3
      SmartClient Version: v13.1p_2026-02-10/AllModules Development Only (built 2026-02-10)

      Hi, thank you very much for the fix. The original test case now works; however, I noticed that if I hide the "Item Name" field, getGroupTitle is once again not called.
      This only happens when a displayField is present.

      Comment


        #4
        It looks like you're right that we missed a case. This is now fixed for tomorrow's builds.

        Comment

        Working...
        X