This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I have a central master database, with several subsets on other terminals. We use a windows service with a timer, to look for changes that have occurred since the last sync. We use the UpdatedOn field to find what changed and when. The problem is when we import a record from a terminal, the UpdatedOn, and CreatedOn, dates are not the same as the original record. For some large change sets, the dates can be very different, and hence we are missing updates. Is it possible for Import to use the original CreatedOn and UpdatedOn? |
|
|
No, the behaviour around CreatedOn and UpdatedOn are covered off when the entity is persisted rather than via being something that can be overridden in Import. You can fudge CreatedOn as long as the entity is not in the New state but UpdatedOn is always going to be bumped when the entity is persisted.
|
|