How does CRM handle a multi-entity structure with various parent-child relationships? In other words, can't there be some timing issue with having separate tokens for each entity? If my process requests all updates to a PARENT entity, and then while I am processing them, someone adds a new PARENT with CHILDREN, and then when the step to get all the CHILDREN starts, it will get the new CHILD records, but it didn't get the PARENT. I think I will still have to do it the old fashioned way and keep my own "token" so I can use the same timestamp across all entities in the structure. Any thoughts?
↧