IdeaBlade / DevForce has always resolved all temp ids when a save begins, even for entities that you are not saving. I wrote extensively on this subject recently because - for reasons mysterious to me - there has been a sudden flurry of questions about this. Apparently, more and more folks are tempted to save some but not all of the entities with pending changes/additions/deletions. We discourage this because there are data integrity risks. Saving some but not all of the entities can result in violations of cross-object business rules and lead to inconsistencies that are hard to detect and repair.
That said, many customers want to do it anyway and are further disturbed that we are resolving all temp ids instead of just those of the new entities being saved. Again, in principle, no one should care about the primary keys. They are supposed to hold arbitrary values with no intrinisic meaning. But, of course, customers sometimes feel differently - they don't want to see gaps in the id sequence for example.
Accordingly, and somewhat at odds with our better judgement, we are going to change our 4 year old practice of resolving all temp ids and allow the fixxing up of only the new entities being saved. This will be done with a FixUpTempIds property in the SaveOptions class. Possible enumerated values are All or InSaveListOnly