Hi Kerry, Seth,
Sorry for the delayed response.
The configuration described above seemed to work fine in a connected environment. It was only in a disconnected environment that the GUIDs for the relates were not getting populated properly. I am still working with ESRI tech support on this, and they provided some additional information for me to test, but I've been swamped and haven't been able to get to it yet. I'm heading out of town for next week, so it likely won't be until the following week before I can adjust my test environment with the info provided.
I will report back when I have more info.
Warren
Here is some details I provided to ESRI:
Just reporting back on this with some updated information as I finally had some time to look into this further, and here's is what I have and what I've found.
Feature Class A (GlobalIDs)
Feature Class B (GlobalIDs)
RelatedTable (GUID & GlobalIDs)
- GlobalIDs were required as well on the RelatedTable to be able to publish the service and enable Sync
Relationship Class A = Feature Class A > RelatedTable (FC A GlobalID to GUID)
Relationship Class B = Feature Class B > RelatedTable (FC B GlobalID to GUID)
The relationships work perfectly in ArcMap and in Collector when connected. However, when disconnected the sync process is not generating the GUIDs in the RelatedTable so the records end up being orphaned the RelatedTable.