Currently ArcGIS Pro default export location is the last place something was exported to globally. This should be set to the last place something was exported to for each project, similar to ArcMap. The default should be the project folder.
While this likely wouldn't address every scenario other users have, it would be helpful if the path could be saved in the .xprt preset file introduced in 3.0.
My specific use case is a MapSeries. I need each exported PDF to follow this naming convention: {ACCOUNTNUMBER}_{CUSTOMERNAME}. To accomplish this I have an attribute field that supplies the file name, which the MapSeries then uses as the page number. When exporting I use the "Multiple PDF Files (Page number as suffix)" setting, and then delete the layout name from the export path ('.../.pdf'). Having to delete the layout name is tedious as the path resets if you navigate away from the export pane.
I appreciate being able to save the MapSeries export settings in a .xprt preset, but excluding the path from the .xprt seems like an oversight. A checkbox to have the path included in the .xprt would preserve the standard functionality. If there was a path parameter that could be manually entered in the .xprt file that could be an interim step while a GUI implementation is developed.
I realize this could likely be accomplished in Python, but the same argument could be made about the parameters currently included in the .xprt file.
OMG....I'm so grateful to the ESRI user community. I was at my wit's end this afternoon, after once again, sending the pdf of my layout to the wrong folder.
I switch projects quite a bit, working on different aprx files every day, and the layout exports need to be saved in different folders
I finally made up my mind to suggest this...I was procrastinating, as it seemed a difficult thing to explain.
To my great pleasure, I realized that this has already been suggested. Thanks, @LeoLadefian3 for taking the time to suggest this and to all who contributed to this idea.
@JeffBarrette and @AubriKinghorn - what's the status of this request? Last discussion on this issue - which has continued to pose operational challenges and cause lost work product, wasted time, and unnecessary stress and confusion for our project teams as described above - was close to a year ago. I strongly urge you to include a fix for this in a patch/version update as soon as possible.
Thanks for all your concern and feedback. I know how frustrating it can be when you export something to the wrong location and can't find it. I don't have an update on if or when this idea will be implemented currently. I'll let you know when I learn more. Thank you for your patience!
As it currently stands, whenever you open the export Layout window, the default location will be wherever the last place you exported that file type to, rather than the project's home folder.
As a result, things get saved in entirely different project folders on accident.
I would like to have the default location location be the home folder when first opening the export pane, and then maintain any folder your change it to for the duration of your session, meaning that it will reset between each project's session.
Please just make ArcPro retain the last export folder path IN THAT SPECIFIC PROJECT. Much of Esri's construct is Microsoft-related so this doesn't seem like it would be a difficult thing to do. Either way, the Global default filepath change occurring upon every export from any project is clearly problematic for many users.
Even if there could be a default export folder the same what they there is a default home folder and default .gdb for each project. Then it would automatically populate in each project when exporting.
Add the ability to add a folder and set as default for all map or layout exports e.g. to pdf or jpg.
Make this a one right click and one left click operation i.e. when you right click on a folder in Catalog have the option to select "Add to Project and Make Default for Map & Layout Exports".
This will be a separate folder to the other Pro Default Folders & things.
Having to reset the export for every project and every file type every time you change a project is not efficient.
