The short-term solution was to "touch" all Ci on dataset A and B.
On the other hand, the project is now in a stillstand and will be re-ignite early next year. Then the 7.6.3 version will also be aviable. Regards, Jarl 2010/11/10 Sergio Tomillero <stomill...@gmail.com>: > Hi, > > Thank you Jarl, > > So, as you mention, we have the same problem: > - If Dataset B is modified, replaces the record in Dataset C without taking > into account Dataset A weights. > - It does not happen if Dataset A is modified, that takes into account > Dataset B weights. > > You say that you had had this problem, do you have it now? > > I have checked carefully my merge activities and I think they are correct, I > do not see what could be causing this behavior. So, if this is a product > defect, is there any workarround? How do people manage to resolve this > situation? Because I think that changing data from dataset B is something > habitual. > > Thanks & regards, > Sergio Tomillero > -- > View this message in context: > http://ars-action-request-system.1093659.n2.nabble.com/Reconciliation-Engine-Cannot-merge-data-from-two-datasets-to-a-destionation-one-tp5718360p5723774.html > Sent from the ARS (Action Request System) mailing list archive at Nabble.com. > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
