So update:
We've tested the usage of DELTA ENTITYSET for our requirement and we found it it's not an option given the request that all Client data should be sent as part of the answer is not supported by the DELTA ENTITYSET response.
Once we've fetched the modified registers from the collection and we fill the information for every created or updated register, copy_data_to_ref method fills the er_entityset, the response is only the customer "header" information, and it ignores the tables containing other info, such as Phone Numbers, Addresses and so.
Right now we've emptied all the ideas we had in order to fullfil the requirement. We have this two paths so far.
Using a "Delta" enabled Expanded EntitySet:
Doing this allows us to fetch the changed registers and fetch their info fully. The issue here is that we lack the ER_DELETED_ENTITYSET which could be a problem for Kapsel when it comes to identify which registers it should deleted from the mobile DB. The next problem is that, we can code and implement the logic in order to Kapsel to recognize and use this method for the Delta Query, and then find a way to deal with the problem with the deleted entitysets.
Our other approach. Use the Standar DELTA ENTITYSET.
Standar gives us both ER ENTITYSETS to work with and we assume Kapsel recognizes this method as a standar method to use when performing Delta Operations. The issue here is that we cannot fullfil the requirement of the Data being sent fully, sending a complex bussiness structure using the header and the tables for each changed register.
Perhaps we're not giving this the correct approach or we're missing a simple step that would easily solve our requirement. If anyone has any idea will be highly appreciated.
Thank you all for your time.