Problem with related tables

Has anyone experienced issues with incorrect data when using related tables based on a table relate in mxd (and subsequently added as a relationship in Rest manager)? 

I brought a REST map service into ArcMap and did an identify on a point to get related results (1:m) and found this worked fine.

Upon adding this same map service to a geocortex site and doing an identify on a point  in HTML5 viewer, the results for one feature were mixed with those of another feature. No duplicates in the primary key field.  I do have another table related in the mxd to this point feature, with same primary key and with same problem. I have had features with one relate work fine, but adding 2 relationships seems to have a bug associated.  Maybe when they have the same primary key?

I imagine someone will comment that I should try with a data connection. But, how could the relationship pass the wrong data through the REST service with geocortex and not ArcMap?

Thanks for any insight.

Ben