Teppo Kurki

Closing this as implementation was merged in https://github.com/vaadin/flow/pull/19806

Tested using Vaadin 24.4.10 (and 24.5-SNAPSHOT as well) and latest available Chrome browser on macOS. Could not reproduce the issue with either react router or vaadin router. URL is correctly...

I'll close this issue for now since it can't be reproduced with latest Vaadin version. Please open a new issue if the problem still persists in some circumstances.

The issue was assigned to a developer and is currently being investigated

Looks like this call `comboBox.setDataProvider(fb, (SerializableFunction) s -> 3);` causes the ComboBox to eventually call `com.vaadin.flow.data.provider.CallbackDataProvider#CallbackDataProvider(com.vaadin.flow.data.provider.CallbackDataProvider.FetchCallback, com.vaadin.flow.data.provider.CallbackDataProvider.CountCallback)` which uses `t -> t` as the id provider. Then, when the actually...

Well here's the reason: https://github.com/vaadin/flow-components/blob/9d6a5672b70699a34c0f475244019fe831d1d249/vaadin-combo-box-flow-parent/vaadin-combo-box-flow/src/main/java/com/vaadin/flow/component/combobox/MultiSelectComboBox.java#L128-L133 `MultiSelectComboBox` does listen to `IdentifierProviderChangeEvent` but the new provider is only passed to selection model, nothing is done for data provider.

This case seems quite complex to fix properly. In the meantime @enver-haase could you try a workaround by creating your CallBackDataProvider using the constructor that also takes id provider as...

Alright. Just to confirm, is the workaround the one above or something else?

Ok, thanks. Yes, that was/is the original way to do that, the DataView stuff was added much later in 2020 or so.

Your data provider should ensure there are no duplicate items returned (e.g. your database probably does not have multiple rows with the same unique id). In the code example here,...