That was exactly that. I was using the same instance and was not aware that data management tracked the instance.
Thank you so much Jeff, problem solved. Benjamin. <http://groups.yahoo.com/group/flexcoders/message/91754;_ylc=X3oDMTJzZ3FsMXB pBF9TAzk3MzU5NzE1BGdycElkAzEyMjg2MTY3BGdycHNwSWQDMTcwNTAwNzIwNwRtc2dJZAM5MTc 1NARzZWMDZG1zZwRzbGsDdm1zZwRzdGltZQMxMTkzMzA3OTQ2> Re: (LCDS) Conflict when inserting data with different ids Posted by: "Jeff Vroom" <mailto:[EMAIL PROTECTED] nserting%20data%20with%20different%20ids> [EMAIL PROTECTED] <http://profiles.yahoo.com/jeffjvroom> jeffjvroom Wed Oct 24, 2007 7:00 pm (PST) For some reason, the cause of the conflict is an update - where the client is trying to change the project_name from project1 to project2. It does not appear to be a "create" operation. Since project_name is the identity property (and primary key) you shouldn't be modifying it. Maybe you are passing the same instance twice to createItem? That won't work with data management because we hang onto the original instance and are tracking changes on it after the first createItem call. As soon as you change project_name, we will think that is a change and queue up a message to the server on that. Jeff
