Hello @jmh.yy ,
Please, see this example: DHTMLX - Kanban. Backend .
I’m afraid we cannot reproduce the issue:
If to add a new card and then click on the undo button, you could see that the request is sent with the right, new ID from the server.
The new created cards are indeed stored under temporary local IDs. But during any server request an ID from the server is used. That is since a RestDataProvider stores an object of type { localId: serverId } until refreshing.
If there is an issue with our RestDataProvider, could you, please, write the steps for us to reproduce it? For example, in the snippet above.
Or, in case, you are using your own provider solution to work with the server, it’s up to you to decide how you would like to implement a way of IDs resolving.