Forum Post: RE: ProDataset MERGE-CHANGES copy-all-mode unexpected behaviour?

  • Thread starter Thread starter Peter Judge
  • Start date Start date
Status
Not open for further replies.
P

Peter Judge

Guest
Smells like a bug to me too. If you dump out the changes dataset after GET-CHANGES() and after MERGE-CHANGES(), they are different. I would not expect them to be, since the direction of the merge should be from changes -- dsCustomer. hChanges:write-json('file', session:temp-dir + 'changes-1.json', yes, ?, ?, ?, yes). /* there's a changes-2 version for dumping after merge-changes() */ changes-1.json has a single eCustomer record (plus the before-image tracking). changes-2.json has a single eCustomer record (plus the before-image tracking) AND 2 eSalesrep records. Note that this doesn't seem to be influenced by the copy-all-mode flag -- peter

Continue reading...
 
Status
Not open for further replies.
Back
Top