https://community.esri.com/t5/arcgis-enterprise-questions/tracking-feature-service-synchronization-events/m-p/1550262#M40795 <P>We are deploying an application that is leveraging sync-enabled feature services to update mobile geodatabases on user client machines.&nbsp; We've had to work out some kinks with mobile gdb registration and synchronization, but things seem fairly stable at this point.</P><P>Our current concern is about tracking what user has synchronized when.&nbsp; There will be hundreds of mobile users, each of whom will be synching at different points in time.&nbsp; &nbsp;From an admin standpoint we want to know which users have data that is up-to-date and which users do not -- actually we mostly want to know about those that do not.</P><P>We've considered some, admittedly kludgy, ways to do this -- like by adding a single, special purpose feature to each class or table that has the last sync table for each class.&nbsp; &nbsp;But it seems there should be information available from the parent replica database about which client has synced when.</P><P>Any suggestions on how we might access replica sync history would be much appreciated.</P><P>Thx,</P><P>Ed</P> Sat, 19 Oct 2024 15:34:08 GMT EdwardBlair 2024-10-19T15:34:08Z https://community.esri.com/t5/arcgis-enterprise-questions/tracking-feature-service-synchronization-events/m-p/1550262#M40795 <P>We are deploying an application that is leveraging sync-enabled feature services to update mobile geodatabases on user client machines.&nbsp; We've had to work out some kinks with mobile gdb registration and synchronization, but things seem fairly stable at this point.</P><P>Our current concern is about tracking what user has synchronized when.&nbsp; There will be hundreds of mobile users, each of whom will be synching at different points in time.&nbsp; &nbsp;From an admin standpoint we want to know which users have data that is up-to-date and which users do not -- actually we mostly want to know about those that do not.</P><P>We've considered some, admittedly kludgy, ways to do this -- like by adding a single, special purpose feature to each class or table that has the last sync table for each class.&nbsp; &nbsp;But it seems there should be information available from the parent replica database about which client has synced when.</P><P>Any suggestions on how we might access replica sync history would be much appreciated.</P><P>Thx,</P><P>Ed</P> Sat, 19 Oct 2024 15:34:08 GMT https://community.esri.com/t5/arcgis-enterprise-questions/tracking-feature-service-synchronization-events/m-p/1550262#M40795 EdwardBlair 2024-10-19T15:34:08Z