Set operationId on listgrid multiple times not working?

[Isomorphic]

Hi Mathias

We see the behavior you are describing

We'll take a look at this case, but for now you can get past this by explicitly clearing out the data object and re-fetching instead of relying on invalidateCache() after setting the operation ID.
This can be achieved with a 'setData(...)' call, passing in an empty list, then calling 'fetchData()' to re-fetch with the new fetchOperation

Regards
Isomorphic Software

[mathias]

Doesn't matter, once you set it, the grid will use that operationId in requests forever, from what I can tell.

private void handleOperationId(boolean setEnabled){
        String newOpId = setEnabled ? operationId : "fetch";
        GWT.log("handleOperationId: " + operationId + ", setEnabled: " + setEnabled +  ", setting operation to: " + newOpId);
        grid.setFetchOperation(newOpId);
    }

If you set it to fetch or anything else first, it will always have that, and the other way around.

[Blama]

Hi mathias,

what happens with

grid.setFetchOperation(setEnabled ? operationId : "fetch")

?

Best regards
Blama

[mathias]

Hello,

just tried this on a list grid:

private void handleOperationId(boolean setEnabled){
        GWT.log("handleOperationId: " + operationId + ", setEnabled: " + setEnabled);
        grid.setFetchOperation(setEnabled ? operationId : null);
    }

But it seems that after you set it once, it doesn't change? After my method above, I do invalidateCache, and it still uses the old operation when fetching.