Dan - I did work as a Programmer for a short while, and am totally aware that sometimes what seems like it should be an easy fix turns out not to be. However, will try one more time to explain what I was saying, since do not feel it registered. Let me know if you know any reason why Birth Location should be treated differently from Birth Surname, Middle Name, etc.
For many of the Basic Fields - including Middle Name, Display Name, Birth Surname - it works the way I consider "the right way" and for at least one other Field, "Birth Location" it does not.
If ProfileA1 and ProfileA2 are the same except that ProfileA1 has never had any data in the Middle Name, and ProfileA2 has a value in Middle Name, and the two are merged, with A1 being/becoming the Primary Profile. Then:
1) For users who are following ProfileA1 or are in A1's close family, they will normally get a message on their Home Page Activity reporting the merge of ProfileA1 and a message reporting the update of ProfileA1.
2) Under the Revision Tab for ProfileA1 there will be an entry reporting that A1's "profile was updated. middle name." with date and blue link "view" below as part of that entry. Above will be an entry saying XXX was added as Manager of A1's profile if the merge added a new manager, and above that will be an entry saying "A duplicate profile was merged into ProfileA1 by ...". All will have the same date and time.
3) From History on Overview Tab, if one clicks on Facts, there will be a line, same date and time as messages mentioned above under Revisions Tab (except, time in Military format here) with "middle name" under "Summary".
4) The merged profile will show the value in Middle Name that had been in A2 (and no Data Conflict will be generated).
If one substitutes "birth surname" or "display name" for "middle name", everything else above stays the same.
However, if one substitutes "Birth Location" - i.e.
If ProfileA1 and ProfileA2 are the same except that ProfileA1 has never had any data in the Birth Location, and ProfileA2 has a value in Birth Location, and the two are merged, with A1 being/becoming the Primary Profile. Then:
1) For users who are following ProfileA1 or are in A1's close family, they will normally get a message on their Home Page Activity reporting the merge of ProfileA1 BUT - No Message reporting the update of ProfileA1.
2) Under Revisions Tab, there will be the entry reporting the added manager (if that happened), and the entry reporting the merge BUT there will NOT be an entry for that date and time reporting an update.
3) From History on Overview Tab, if one clicks on Facts, there will be no line, with same date and time as messages mentioned above. ie No indication in History/Facts that Birth Location was entered.
4) The merged profile will show the value in Birth Location that had been in A2 (and no Data Conflict will be generated).
Hopefully this illustrates both the connection between History/Facts and the listings under the Revision Tab, as well as why I had not thought this was about "missing functionality", "features to be improved" or any major addition in Functionality of Revisions, etc.