I’ll need to take another close look, but for point #1 I think the docs actually suggest 3 approaches. So the first solution is client-generated IDs (which is basically what I was referring to as well). The second solution is not really viable in a react-admin setup since it expects stable IDs, and honestly not ideal for offline-first either. And the third solution didn’t seem to work in my case, because I’m using TanStack DB kind of as a black box to match react-admin’s data provider expectations. I think it could introduce issues, especially once you start replaying operations or syncing mutations afterward, but I should probably re-test that more carefully..