formatCellValue calls after startEditingNew

[claudiobosticco]

SmartClient Version: v13.1p_2025-03-21/AllModules Development Only (built 2025-03-21)

Hello, I've got a problem in my application which I managed to replicate in the showcase, please try this test case:

isc.ListGrid.create({
    ID: "countryList",
    width: 700, height: 224,
    showFilterEditor: true,
    initialSort: [
        {
            property: "countryName",
            direction: "ascending"
        }
    ],
    dataSource: worldDS,
    fields: [
        {name: "countryName"},
        {name: "continent"},
        {
            name: "government",
            formatCellValue: function (value, record, rowNum, colNum, grid) {
                isc.logEcho(record, "formatCellValue " + rowNum)
            }
        },
        {name: "area"},
        {name: "gdp"},
        {name: "independence", width: 100}
    ]
})

then if you run countryList.startEditingNew() you'll see a WARN:

*15:52:44.505:WARN:gridEdit:countryList:startEditing() passed bad cell coordinates:1000,0, can't edit
    ListGrid.startEditing(_1=>1000, _2=>0, _3=>undef, _4=>undef, _5=>undef) on[ListGrid ID:countryList] @ ISC_Grids.js:2264:97
    ListGrid.startEditingNew(_1=>undef, _2=>undef) on[ListGrid ID:countryList] @ ISC_Grids.js:2456:6
    null.<anonymous>(<no args: exited>) @ [no file]:1:13

and data will be fetched (I wasn't expecting this).

Instead if you run countryList.startEditingNew({continent:"Asia"}) you'll see also many calls to formatCellValue with record === null (for rowNums==0 to 8, and from 992 to 999, for rowNum == 1000, you'll see a record with the continent value).

is this a bug, or has there been some change in behaviour? Currently my code does not expect record to be null, and even the fetch seems unexpected

[claudiobosticco]

also note that in my actual use case I've got autoSaveEdits:false

[claudiobosticco]

Hello, any news about this issue?

Out of curiosity, I've tried the test case in 14.1 and 15.0 also, and I see the same behaviour.

[Isomorphic]

Hi Claudio
It would help us to understand what you're trying to do here. Usually startEditingNew() is used to edit a new record at the end of a grid's data set and it wouldn't be expected to call it on an empty data bound grid.

Are you using "saveLocally" and using the DataSource as just a schema rather than intending to save edits through standard DataSource add/update operations? We can certainly look into what's going on with the default behavior you're describing but what are you actually trying to achieve here?

Thanks

[claudiobosticco]

Hello, in my application, the grid is empty because no records match the criteria. In fact, grid.data is:

ResultSet{autoFetchRowCount: undef,
dbcFields: Array[16],
dbcCacheOrdinal: 3,
fetchDelay: 1,
operation: Obj{ID:fetchEventiSquadraWithTipologia},
filter: Obj,
context: Obj,
componentId: "gestPlanningTeamManagerEventEditPadreSqu..."[48],
ID: "isc_ResultSet_1",
fetchOperation: "fetchEventiSquadraWithTipologia",
fetch_OpConfig: Obj{ID:fetchEventiSquadraWithTipologia},
dataSource: [DataSource ID:JAS_CALENDARIO_EVENTI_SQUADRA],
fetchMode: "paged",
criteria: Obj,
localData: Array[0],
totalRows: 0,
lastRangeStart: 0,
lastRangeEnd: 25}

However, I couldn't replicate this issue in the showcase with an empty ResultSet.

Other than that, the observed behaviour is exactly the same. I've also discovered that the problem occurs only when the grid has an initialSort, both in my application and in the test case.