UNC Paths Coerced to Drive Paths
My team runs a number of automated ETL and publishing workflows using arcpy and ArcGIS Pro. We've noticed a change in behavior as we're upgrading from Pro 3.3.2 to 3.5.6. Specifically, we have configured a number of Pro projects with data sources set to a local UNC path (e.g. \\mapping-machine.domain\D\Data) as opposed to a drive path (e.g. D:\Data). We do this because many of our jobs are triggered from other VMs and maintaining the UNC path avoids those data sources from breaking. The change in behavior that we've noticed is that, if a project is saved from that other VM, those paths are coerced to D:\Data in that project and subsequent jobs will fail because of those broken data sources.
Has anyone either run into this issue or developed a workaround?