https://community.esri.com/t5/developers-questions/replica-is-being-offset-by-3-3-feet-from-child-to/m-p/1631120#M7564 <P><STRONG>Replica is being offset by 3.3 feet from Child to Parent Database when replicating using arcpy.management.SynchronizeChanges (arcpy version 2.3.0) in a standalone python script running version 3.11.8.&nbsp; We do not have an offset when running corresponding built-in geoprocessing tools from within ArcGIS Pro (version 3.3.1).&nbsp; We also see the same results in Notebook, which fails outside of ArcPro.</STRONG></P><P><STRONG>We did not have this issue in ArcMap and Python 2.7</STRONG></P><P><STRONG>Does anyone have anything like this?&nbsp; How do you solve it.</STRONG></P> Tue, 08 Jul 2025 15:04:32 GMT dbKlingdom 2025-07-08T15:04:32Z https://community.esri.com/t5/developers-questions/replica-is-being-offset-by-3-3-feet-from-child-to/m-p/1631120#M7564 <P><STRONG>Replica is being offset by 3.3 feet from Child to Parent Database when replicating using arcpy.management.SynchronizeChanges (arcpy version 2.3.0) in a standalone python script running version 3.11.8.&nbsp; We do not have an offset when running corresponding built-in geoprocessing tools from within ArcGIS Pro (version 3.3.1).&nbsp; We also see the same results in Notebook, which fails outside of ArcPro.</STRONG></P><P><STRONG>We did not have this issue in ArcMap and Python 2.7</STRONG></P><P><STRONG>Does anyone have anything like this?&nbsp; How do you solve it.</STRONG></P> Tue, 08 Jul 2025 15:04:32 GMT https://community.esri.com/t5/developers-questions/replica-is-being-offset-by-3-3-feet-from-child-to/m-p/1631120#M7564 dbKlingdom 2025-07-08T15:04:32Z