Why is Pro using relative paths in some cases and then not finding a resource, when nothing has changed other than it is a new day?
Just go back to using full paths everywhere by default.
Yes - this is not the default gdb. No - the default gdb is used for other stuff. No - this data cannot go into the default gdb.
@yugulje Can you elaborate?
All our data is on a mapped network drive.
From what I understand Esri is forcing relative references because it thinks everything should be in a single project folder/gdb near the aprx so that you can move it around and not loose connections.
This seems to break for various reasons and under various circumstances when you have data external to the default project folder/gdb.
In ArcMap you could specify full or relative paths to suit various circumstances. I just want feature parity.
It seems Pro 3.3 has issues navigating relative paths and will time-out or something leading to temporary raster layers failing almost every time a project is opened.
This path has not changed yet I have to edit the function chain every time and then fix the symbology every time.!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.