On 8/2/2015 3:01 PM, Michael J. Hannah via wrote: > However, since I still have old versions of TMG installed I tested this > merging today in various earlier versions. The behavior we expected and > described *was* the behavior in Version 7.04 (which is the last version > where I tested this specific issue). Testing now shows that the > behavior is different in Version 8.08, and the final Version 9.05 > retains that different behavior. Thanks, Michael, I no longer have any old versions installed. My article on Merging, which covers this issue, was last updated in Apr 2005, when TMG 6 was new. And I don't know that the part that covers this issue was updated then - it may have been last tested with TMG 5. I know Jim and I spent a large amount of time with the developers trying to get the Merge Data Sets feature to work in a reasonably logical way, and I think that was when multiple Data Sets were first introduced with TMG 5. I believe this article was first written when or soon after TMG 5 was released. I never merge data sets so I'm sure I've not looked at the issue in years. Thanks to your testing we now know we did all correctly understand how it was supposed to work, and that it did change without anyone noticing. > In summary as Terry noted, as of Version 8 the only way to retain the > old values from the sending dataset is to first create a flag of the > same name in the receiving dataset. Actually, I noted that it works correctly if the custom Flag is created and set in the "receiving" data set. It did not occur to me that you can make it work with the flag in the "sending" data set provided you create one of the same name in the other data set too, which I think is what you are saying you found works. If so, that does provide a workable work-around as long as one knows it is required. Terry Reigel