valuePath not resolved with initialCriteria/implicitCriteria

[claudiobosticco]

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

Hello, I encountered a regression when using valuePath with initialCriteria / implicitCriteria (at least since v13.1p_2026-02-15).

Please try the following test case:

isc.DynamicForm.create({
    ID: "dsForm",
    dataSource: "supplyItem"
})

isc.ListGrid.create({
    ID: "dsListGrid",
    visibility: "hidden",
    autoDraw: false,
    width: 500,
    height: 300,
    autoFetchData: true,
    initialCriteria: {
        fieldName: "itemID", operator: "equals", valuePath: "dsForm.values.itemID"
    },
    dataSource: "supplyItem"
});

isc.HLayout.create({
    members: [dsForm, isc.IButton.create({title:"show grid", click:"dsListGrid.show()"}), dsListGrid]
})

dsForm.fetchData()

After clicking the button, you can see from the RPC tab in the developer console that the valuePath is not being resolved:

{
    dataSource:"supplyItem",
    operationType:"fetch",
    componentId:"dsListGrid",
    data:{
        fieldName:"itemID",
        operator:"equals",
        valuePath:"dsForm.values.itemID"
    },
....

[Isomorphic]

hi Claudio, thanks for the report - this has been fixed for tomorrow's builds, dated February 20 and later.

[claudiobosticco]

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

Hi, I can confirm that it's fixed, thank you very much!

[claudiobosticco]

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

Hello, I found another bug in a similar scenario (initialCriteria + valuePath).
I’m not sure whether it was already present before the fix or not.

It is reproducible in the showcase (FetchOperationFS sample) with the following test case:

isc.DynamicForm.create({
    ID: "dsForm",
    dataSource: "supplyItem"
})

isc.ListGrid.create({
    ID: "dsListGrid",
    autoFetchData: true,
    initialCriteria: {
        fieldName: "itemID", operator: "equals", valuePath: "dsForm.values.itemID"
    },
    dataSource: "supplyItem"
});

isc.TabSet.create({
    width: 800,
    height: 600,
    tabs: [
        {
            ID: "firstTab",
            title: "Form",
            pane: isc.VLayout.create({
                membersMargin: 5,
                members: [
                    isc.HStack.create({
                        height: 50,
                        membersMargin: 5,
                        members: [
                            isc.IButton.create({title: "Fetch Record", click: "dsForm.fetchData({itemID:1})"}),
                            isc.IButton.create({title: "Edit New Record", click: "dsForm.editNewRecord()"})
                        ]
                    }),
                    dsForm
                ]
            })
        },
        {
            ID: "secondTab",
            title: "Grid",
            pane: dsListGrid,
            enableWhen: {fieldName: "dsForm.values.itemID", operator: "notNull"}
        }
    ]
});

- Click on "Fetch Record"
- the "Grid" tab becomes enabled
- Switch to the "Grid" tab, where you can see that the record has been fetched
- Switch to the "Form" tab
- Click on "Edit New Record", the "Grid" tab becomes disabled
- Click on "Fetch Record", the "Grid" tab is enabled again
- Switch to the "Grid" tab, where you can see that a fetch has been performed without criteria

[Isomorphic]

hi Claudio - this wasn't related to the previous fix - in this case, the ruleScope mechanism was updating incorrectly in response to the record being cleared - that process recognized the current valuePath as incomplete, removed it and then fetched with no criteria. There shouldn't have been any fetch at this time.

It's been fixed for today's builds.

[claudiobosticco]

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

I can confirm that it's working, thank you very much!