Q: Is match criteria comparison case sensitive? A:  After 14.5.0  Yes There was some logic prior to 14.5.2 to make matching  ignore case, that was removed to allow true matching.

Q: Can you update existing products in the products table? A: Yes, you can match on a field or fields and update it. One method would be to export all the products, update any of the fields (Name, ItemNumber, Cost, Price) the import back in matching on the Record ID (GUID). Note that custom fields in the Product table are NOT yet editable via OAK!Merge Q: Can you update existing products in an Opportunity? A: No, you can only append new products to an Opportunity; one per merge. You cannot upda...

If a MY RECORD for an USER has a blank contact field; then NO updates to any record manager fields will occur.  No error message is returned. This can also be described as ACT users must have Contact names Status: reproduced in 14.1  and 14.4 beta ACT! requires a contact name when you create a new user and does not let you errase it in the detail screen, but apparently there is someway to have a blank one.  See below.   Below has a space to illustrate how it looks.

The results of a merge are normally shown on the Results page.  That page is an HTM page in the logs folder that can be reviews later.  Know Bug:  The HTM file may not be displayed after a large merge.  The XML page is not properly processed to build the HTM results page.  The merge was completed but the results were not displayed.  This was due to a problem with the progress bar being displayed and was fixed in 14.3.   Below is what is NOT displayed on some large imports on fast machines. Stat...