As I have mentioned before, I'm beginning to use shared facts for the very limited purpose of listing marriages in timeline order in narrative reports. This is accomplished by sharing the marriage fact with each of the spouses with a new role called Spouse. For the purpose of listing marriages in timeline order in narrative reports, the fact that shared facts don't export to third party software is more of an advantage than a disadvantage.
My sentence template for the standard (unshared) marriage fact continues to use the tag [Couple] to refer to the couple who were married. My sentence template for the shared version of the marriage fact uses the tag [Spouse] instead. The idea is that if John Doe marries Jane Smith, the shared version of the marriage fact for John Doe will say that he married Jane Smith and the shared version of the marriage fact for Jane Smith will say that she married John Doe. My shared sentence template for John Doe works perfectly and says that he married Jane Smith. But my shared sentence template for Jane Smith says that she married Jane Smith.
Originally, I created both shared facts while editing the marriage fact from the Edit Person Screen for John Doe. On a lark, I deleted the shared marriage fact for Jane Smith and shared it again from the Edit Person Screen for Jane Smith. This made no difference.
A workaround for the problem is to replace the tag [Spouse] in Jane Smith's shared marriage sentence template with the string "John Doe" without the quotes. It works just fine, but it seems to me that there is a real bug and that the workaround should not be required.
One thing that I was worried about with the workaround is that it does not create an XE entry in the RTF file to assure that the page with the shared marriage fact is indexed when the narrative report is printed with Microsoft Word. It's not likely to be a problem because John Doe is very likely to appear with other XE entries on the same page. But it turns out that even if the [Spouse] tag had worked correctly, there is no XE entry produced anyway. I think not producing the XE entry in this case is a bug, but again it's extremely unlikely to manifest itself because the person is very likely to appear with other XE entries on the same page anyway.