Announcement

**claudiobosticco** · 2 Sep 2024, 23:18

Note that if I use implicitCriteria instead of initialCriteria, then it works (with autoFetchData) :confused:

**claudiobosticco** · 3 Sep 2024, 00:18

But now I also noticed that if I use implicitCriteria, when the value referred by the valuePath changes, it doesn't trigger a fetch.

Test case (modified fetchOperationFS sample):

Code:

isc.DynamicForm.create({
    ID: "testForm",
    fields: [
        {name: "aField", valueMap: {"Roll": "Roll", "Ea": "Ea"}}
    ]
})

isc.ListGrid.create({
    ID: "dsListGrid", top: 50,
    implicitCriteria: {
        fieldName: "units", operator: "equals", valuePath: "testForm.values.aField"
    },
    width: "100%",
    height: "100%",
    autoFetchData: true,
    dataSource: "supplyItem"
});

instead if I use initialCriteria, every change on the form will trigger a fetch on the grid.

**Isomorphic** · 3 Sep 2024, 12:57

Hi Claudio. Thanks for the report. We have committed a fix for the implicitCriteria not picking up the valuePath changes available in builds starting Sep 4. However, you can also use a full AdvancedCriteria (with outer operator and criteria properties) to make it work without a new build.

With this code we did not reproduce the too much recursion issue. Are you still experiencing it? If so, can you make it happen with a modified showcase sample change as well?

**claudiobosticco** · 4 Sep 2024, 23:55

SmartClient Version: SNAPSHOT_v13.1d_2024-09-04/Enterprise Deployment (built 2024-09-04)

Hello, both issues are fixed for me, thank you very much.

Announcement

InternalError: too much recursion

Comment

Comment

Comment

Comment