idea Save Project As, Creating more than just the APRX in ArcGIS Pro Ideas

Save Project As, Creating more than just the APRX

ErikBreedon — Fri, 22 Jul 2022 21:12:44 GMT

There should be a way to save the whole project as a new project, creating more than just the aprx file, but also duplicating all other supplemental files.

Re: Save Project As, Creating more than just the APRX

SimonSchütte_ct — Mon, 25 Jul 2022 12:52:08 GMT

It is possible to save a Project Package (ppkx), but having an option in the "Save Project As" dialog would be nice:
(optional checkbox)

Instead of only saving the .aprx file under a new name, also clone the files from the current home directory to the new directory, where the APRX is saved to.

Why is it useful?: If you have different versions of an APRX file, all referencing the same GDB, accidental changes to the data can happen. If you try out different Project configurations for example.

Re: Save Project As, Creating more than just the APRX

wayfaringrob — Mon, 25 Jul 2022 16:33:06 GMT

@SimonSchütte_ct yes. It also takes AGES for a project to package.

Re: Save Project As, Creating more than just the APRX

DavidWheelock2 — Thu, 28 Jul 2022 14:07:01 GMT

Seems like a no-brainer. I've wanted this, too.

Though, you can just copy the whole ArcGIS Pro project folder using Windows File Explorer and that will do the same thing.

@KoryKramer, has this been suggested before?

Is Windows File Explorer the recommended method for this?

Re: Save Project As, Creating more than just the APRX

ErikBreedon — Tue, 29 Aug 2023 20:01:55 GMT

Looking back months later, I've found this workflow accomplishes what I needed:
1. Save your favorite layout as a layout file.
2. Start a new project.
3. Import the layout file into the new project.
4. Save the new project.

Re: Save Project As, Creating more than just the APRX

HallvardSkrede — Tue, 26 Sep 2023 17:36:18 GMT

@ErikBreedon is that only giving you the layout-file, or the entire project?

I am trying to do this myself:

Create a copied project with no references to previous projects/file paths/databases, and then get all the features layers as unique features layers within the new database, maintaing symbology, queries etc.

Links to WMS etc. should also remain.

Share>project template does this partly, but you get a "lot of databases" within the new database instead of all layers gathered in one database. Moreover, absolutely all layers (that have been added in the map) that stems from a database within the company network is brought over in the new project template. These I would like to rather remain as links, as they are many GBs worth of data...

I.e. I only want the feature classes that are existing in the map database I was originally making the template from over in the new one, not all other "linked" databases too. I think it would be nice if we could differentiate which databases are brought over to the new project template and not, then my problem would be fixed, and for those who want to combine databases, their problem would be fixed too. 🙂

I am a fan of the ArcGIS-program (quite a newbie myself), so these are some features I hope to see in the feature (if they don't already exist). 🙂

Re: Save Project As, Creating more than just the APRX

AlfredBaldenweck — Thu, 28 Sep 2023 13:51:01 GMT

PLEASE add this in.

All my users ask for templates so they don't have to recreate everything for each project.

The PAGX workaround works ok but was a lot harder to explain than just using Save As, which is the default workflow for just about every other program, including ArcMap.

Project Templates (APTX) have a host of problems in their current implementation, and, frankly, a project package doesn't really fill the need of just being able to duplicate a whole project. (For one thing, the whole "unpack to the Packages folder instead of a place that's actually useful" thing is a massive tripping hazard).

Please let us just Save As to duplicate the entire project folder, not just the APRX.

Add in a duplicate Project option

AlfredBaldenweck — Sat, 16 Dec 2023 15:27:21 GMT

This keeps happening to my users. They spend a bunch of time making a Pro project to use as a template for everything else, then, to duplicate it, they use Save As.

This is awful.

All of the default stuff, e.g. the default gdb, belongs to the original project, and then everyone is confused as to why stuff is saving there.

The clear workaround is to use Layout Files (PAGX -- also because Project Templates do not work in a smart way) but also that's something else to explain and quite frankly, I have users who just don't get it no matter how many times I explain. They can understand Save As to save a copy, since that's how it works for every other program. But let's be real, an aprx without its own folder or default gdb is kind of useless (and again, confuses everyone trying to save stuff).

So.

Please add in a Duplicate Project option, where it copies everything in the project-- Maps, Layouts and places it in a new project folder, with a new gdb, wherever the user chooses. This will be a lot easier for people to actually do what they think they're doing.

Re: Add in a duplicate Project option

JohnPlunkett — Thu, 07 Dec 2023 20:35:10 GMT

Would creating a project package solve your issue?

Share a project package—ArcGIS Pro | Documentation

This creates a project package and packages up the local data and makes a copy of it.

C:\Users\<USERNAME>\Documents\ArcGIS\Packages\<PACKAGENAME>

When you extract the package - by default it gets extracted here, but you can move the content to a different location if you desire once its opened for the first time

Re: Add in a duplicate Project option

AlfredBaldenweck — Thu, 07 Dec 2023 20:43:12 GMT

Hi, Project Packages do not solve the issue for the same reason that Project Templates (themselves a type of Project Package) don't, either: I'm not looking to duplicate any data, just the maps and layouts.

For ArcMap users, the workflow for the past 20ish years has been to Save As to duplicate and reuse most of your work on a new map, and it's causing issues as they migrate. With the addition of the new default gdb per project as well as the home folder, this workflow no longer works. I suppose I could tell them to copy the original project's entire folder, but then they have to rename everything and change the default gdb in Options, etc. Having a "Duplicate Project" button makes this a lot simpler.

(As a side note, why on earth can't we choose where packages get extracted to? If I'm opening a Project Package, it's because I plan to use it in Documents\ArcGIS\Projects or another folder somewhere. Why on earth would I look for it in Packages after unpacking it?)

Re: Add in a duplicate Project option

KoryKramer — Sat, 16 Dec 2023 15:29:04 GMT

(As a side note, why on earth can't we choose where packages get extracted to? If I'm opening a Project Package, it's because I plan to use it in Documents\ArcGIS\Projects or another folder somewhere. Why on earth would I look for it in Packages after unpacking it?)

Have you looked at Set unpacking options? https://pro.arcgis.com/en/pro-app/latest/get-started/share-and-download-options.htm#ESRI_SECTION1_D6B5AD4C705B47A29A5A75A4183850CC

Re: Add in a duplicate Project option

AlfredBaldenweck — Mon, 18 Dec 2023 13:58:24 GMT

Have you looked at Set unpacking options?

This is great! Why isn't just choosing the output location just the default?

Re: Add in a duplicate Project option

AlfredBaldenweck — Thu, 25 Jan 2024 21:22:34 GMT

Oops, should have done my homework.

I think this idea is a duplicate (Ha-ha!) of this one. ArcGIS Pro: Save Project Copy - Page 2 - Esri Community

Re: Add in a duplicate Project option

AlfredBaldenweck — Sat, 16 Mar 2024 18:45:30 GMT

So, at the Dev Summit this last week, I asked about this.

The very nice Esri staff I was talking to was like "What are you talking about? Save As works fine"

So I say "No, it only duplicates the APRX but nothing else". So we test.

Turns out, in 3.2, the Save As functionality through the GUI has been changed to duplicate the entire folder. No clue as to whether it also duplicates the contents of your default GDB, but still, good to know.

I just tested it again in 3.1 and Save As only duplicates the APRX in this version.

Anyway, so it looks like there may be a viable solution out there. If someone using 3.2 could test and 1) confirm it actually works as it appeared to, as well as whether or not the contents of the Default GDB get duplicated, I'd appreciate it. (also what are the implications here for aprx.SaveACopy()?)

The other thing is: Why wasn't this change in behavior documented, either in the release notes or on one of the two relevant ideas (this one or this older one?) Very excited to hear there's light at the end of this particular tunnel, but I would never have found out if I hadn't asked directly.

Re: Save Project As, Creating more than just the APRX

brianmoran_usfs — Tue, 20 Aug 2024 21:53:13 GMT

Any update on this simple functionality that seems like a total no-brainer?

Re: Save Project As, Creating more than just the APRX

AlfredBaldenweck — Wed, 21 Aug 2024 12:53:00 GMT

@brianmoran_usfs

So, this is anecdotal since I'm still on 3.1, but in March I asked about this at the Dev Summit and got a "What are you talking about, Save As duplicates everything" and I was like "No it doesn't" and then they demoed it and it seems on 3.2 it works?

Can someone test this and let us know?

Re: Add in a duplicate Project option

AlfredBaldenweck — Fri, 21 Mar 2025 18:16:09 GMT

As it turns out, now that I'm in 3.3, Save As still only duplicates the APRX, so I'm not really sure what happened there.

We're trying to get the users to use PAGX and MAPX files, but it's an uphill battle.

The Save As option should create a local folder and copy the database or at least create a new one.

MDB_GIS — Fri, 19 Dec 2025 19:10:15 GMT

When you use the "Save As" option currently, it creates a new .aprx file in the directory that you chose, but that .aprx file is still connected to everything in the old project. It does not have a folder connection to the new folder, it does not have a new file geodatabase (it is still connected to the previous project), and it does not get a tool box. In my opinion, this defeats the purpose of "Save As". When I use that option, I am looking to use my existing map to branch off into a new version, but retain my layouts, project data, etc..

It would make way more sense to me if "Save As" copied your project geodatabase and toolbox, as well as created a new folder connection to the new location rather than being completely tethered to the old project. Re-configuring all that takes so much time, I might as well have just started a new project from scratch.

Re: Save Project As, Creating more than just the APRX

BrennanSmith1 — Mon, 05 Jan 2026 21:09:44 GMT

Thanks @MDB_GIS for explaining it clearly. I had a similar need, and used this python toolbox as a workaround to make a clone of an ArcGIS Pro Project folder. Assuming that the .aprx, .gdb, and .tbx files all have the same name as the parent directory, you just give it in existing input folder, and the desired output folder. It will copy those 3 items (aprx, gdb, tbx) and update the default paths. It will also update the data sources for any layer that was pointing to the old gdb into the new gdb. It's not the most robust solution, but it worked for me.

I agree that this functionality should be native to ArcGIS Pro. Maybe another option next to "Save Project As" for "Clone Project"?

''' This python toolbox will create a total copy of a Pro project (APRX with maps/layouts), as well as the geodatabase and toolbox associated with it. The new project will reference the new gdb/tbx copies. Data sources outside this gdb will not be updated. This approach assumes that the parent directory, aprx, gdb and tbx files all have the same names (default Pro behavior) It will not work if things have been renamed or moved around. ''' import arcpy import os class Toolbox: def __init__(self): self.label = "Toolbox" self.alias = "toolbox" self.tools = [Tool] class Tool: def __init__(self): self.label = "Save As Project Copy (Clone)" self.description = "" def getParameterInfo(self): input_folder = arcpy.Parameter( displayName="Input Folder", name="input_folder", datatype="DEFolder", parameterType="Required", direction="Input") output_folder = arcpy.Parameter( displayName="Output Folder", name="output_folder", datatype="DEFolder", parameterType="Required", direction="Output") params = [input_folder, output_folder] return params def isLicensed(self): return True def updateParameters(self, parameters): return def updateMessages(self, parameters): return def execute(self, parameters, messages): p = {p.name: p for p in parameters} input_folder = p['input_folder'].valueAsText output_folder = p['output_folder'].valueAsText # define paths / variables for input and output dir/aprx/gdb/tbx input_name = os.path.basename(input_folder) input_project_path = os.path.join(input_folder, input_name+".aprx") input_gdb_path = os.path.join(input_folder, input_name+".gdb") input_tbx_path = os.path.join(input_folder, input_name+".atbx") output_name = os.path.basename(output_folder) output_project_path = os.path.join(output_folder, output_name+".aprx") output_gdb_path = os.path.join(output_folder, output_name+".gdb") output_tbx_path = os.path.join(output_folder, output_name+".atbx") # Create the output folder if necessary if not os.path.exists(output_folder): os.makedirs(output_folder) # Copy gdb and tbx arcpy.management.Copy(input_gdb_path, output_gdb_path) arcpy.management.Copy(input_tbx_path, output_tbx_path) # Open the input project p = arcpy.mp.ArcGISProject(input_project_path) # Update data sources p.updateConnectionProperties(input_gdb_path,output_gdb_path) for map_ in p.listMaps(): for layer in map_.listLayers(): if layer.supports("dataSource"): layer.updateConnectionProperties(input_gdb_path, output_gdb_path) # Update project defaults p.defaultGeodatabase = output_gdb_path p.defaultToolbox = output_tbx_path p.homeFolder = output_folder # Save a copy of the modified input aprx as the output aprx p.saveACopy(output_project_path) return def postExecute(self, parameters): return