I could use another set of eyes on a problem I just discovered.
I have a table, call it "Tenants" to keep it simple. On the HUB (a SQL Server DB) the primary key is pTenantID. On the FileMaker spoke the primary key is pk_TenantID.
I have another table "WorkOrder" on both the hub and spoke which contains as a foreign key field, fk_TenantID to the Tenants table.
When I do a sync to the spoke, all tenant records come over and are assigned PK's on the spoke. If a Work Order exists on the HUB, the corresponding tenant is properly assigned on the spoke, so if I view it on the FM database, the correct tenant is shown.
However, if I create a new work order record on the spoke, select a valid tenant from the tenant's table and then sync, the tenant assigned in the HUB database is the first tenant record chronologically. In other words, it does not match up the selected tenant PK from the spoke/FM databae with the corresponding Hub/SQL table.
At first, I thought it may be a config problem, but I went through the config and the correct relationship is defined and the fields are matched up properly. I can't figure out why MirrorSync would assign the wrong tenant ID when the new work order is synced to the HUB.