idea ArcGIS Pro: Save Project Copy in ArcGIS Pro Ideas

ArcGIS Pro: Save Project Copy

emmornile1 — Fri, 21 Sep 2018 19:42:04 GMT

One of the best enhancements of ArcGIS was the Save A Copy of the map document. This is not the same as "Save As", Save A Copy creates a back up copy with the correct paths pointing to the data. "Save As" creates a copy, but then the copy becomes the working document. Pro does not have this functionality which means making working back up copies of the Pro Projects is difficult. There is no need to make a copy of the Project GDB, just point the paths in the Project copy to that folder.

Screenshot of 10.6 File menu:

Re: ArcGIS Pro: Save Project Copy

KoryKramer — Fri, 21 Sep 2018 23:40:15 GMT

It looks like the basic difference is that ArcMap's Save A Copy saved a copy of the document but didn't switch it to the working copy.

Can you copy the aprx and paste (same folder/different folder)? This can be done while the project is still open.

Re: ArcGIS Pro: Save Project Copy

emmornile1 — Mon, 24 Sep 2018 23:17:44 GMT

Typically the workflow our analysts follow is to make a copy in sub-folder named "backups", with 10.x the paths are saved correctly since we use "save relative paths". Using windows explorer won't do that, saving a copy from the ArcGIS application requires a minimal number of steps.

What is the argument that lead to removing 10.x functionality? Why is it that I have to justify the behavior of Esri software to match existing Esri software?

Re: ArcGIS Pro: Save Project Copy

Anonymous User — Thu, 27 Dec 2018 23:13:16 GMT

Kory Kramer‌ Any comment?

Re: ArcGIS Pro: Save Project Copy

KoryKramer — Thu, 27 Dec 2018 23:58:05 GMT

Hi Emmor,

I tagged this as an ArcMap equivalency issue when you submitted it so is on the list of equivalency issues that I provide to development teams.

Thank you.

Re: ArcGIS Pro: Save Project Copy

Anonymous User — Fri, 28 Dec 2018 00:03:06 GMT

Thanks Kory

Re: ArcGIS Pro: Save Project Copy

BarryFosberg — Tue, 06 Apr 2021 19:37:58 GMT

This reads as a definition of "copy" of which I have never experienced.

A copy is supposed to be a stand alone entity such that if something goes wrong in one or features are lost, they still exist in the original. This reads as if all that has been done is to create a new .mdx that continues to point to the old geodatabase.

Deletions, additions or corruption in the one poisons the other as they are the same.

What is the method to start an entirely new .mdx that begins with the same everything in an existing one,, maps, scenes, fonts layers and etcetera and allows the user to change the new ias necessary with nothing changing in the original?

Re: ArcGIS Pro: Save Project Copy

KoryKramer — Tue, 06 Apr 2021 21:13:05 GMT

It sounds like you're more interested in a package.

In ArcMap you could create a map package: https://desktop.arcgis.com/en/arcmap/latest/map/working-with-arcmap/creating-a-map-package.htm

In Pro, there are options to create a map package or project package depending on what you need:

https://pro.arcgis.com/en/pro-app/latest/help/sharing/overview/map-package.htm

https://pro.arcgis.com/en/pro-app/latest/help/sharing/overview/project-package.htm

Re: ArcGIS Pro: Save Project Copy

AndrewWillingale — Fri, 18 Jun 2021 10:14:20 GMT

Hi @KoryKramer

Following your post of 12-27-2018 please can you advise when we can expect this functionality please? Thanks.

Re: ArcGIS Pro: Save Project Copy - Status changed to: Under Consideration

KoryKramer — Sat, 19 Jun 2021 22:22:11 GMT

I spoke with the development team and we're moving this to Under Consideration. See the for the status definitions.

Thank you!

Re: ArcGIS Pro: Save Project Copy

AndrewWillingale — Mon, 21 Jun 2021 15:12:07 GMT

Excellent, thanks Kory.

Re: ArcGIS Pro: Save Project Copy

BarryFosberg — Wed, 01 Dec 2021 15:17:11 GMT

Follow-up as of 12-1-2021.

Using 2.8.2

Saving a project under a new name is functionally counter-intuitive. The new project still defaults to the old geodatabase, tool box and etc. The new project does not create new project anything. Changes in the "new" project changes both the new and the old project.

Creating a Project Template only works IF the existing project can pass certain requirements. My specific need is to let some one else help with a model that is not working, or more exactly only works when run as a model, and not at all as a tool. These failures deny the choice of making a Project template

I am back to saving the earlier project under a new name, then copy, pasting and renaming the tool box and geodatabase, making these the new items defaults, then deleting the connections to the original project.

There has to be an easier way.

Re: ArcGIS Pro: Save Project Copy

KoryKramer — Thu, 28 Jul 2022 15:50:23 GMT

@BarryFosberg it sounds like you are interested in what is requested here: https://community.esri.com/t5/arcgis-pro-ideas/save-project-as-creating-more-than-just-the-aprx/idi-p/1195131

Give that your kudos if you agree.

Thanks

Re: ArcGIS Pro: Save Project Copy

BarryFosberg — Thu, 28 Jul 2022 16:17:17 GMT

I have not yet tested this:

At UC one of the ESRI ARCPro folks advised me that Project Packabe is little more than a .zip file. It differs from a zip file in that it will locate things like the Geodatabase and the Tool box onto a default location. That default location is going to be on the C: Drive.

It was suggested that by treating it as a zip folder, and using an unzip app, it should be easier to direct the pacakge to loard where the user desires to save the map and its componant folders.

The Project package should be less driven to assume where things should be stored somewhere between the 2.8 , which is what we are now using and 3.0.

Re: ArcGIS Pro: Save Project Copy

StefanieWenker — Fri, 28 Jul 2023 18:57:34 GMT

It would be more useful to be able to "Save as a Copy" and then have the option to either keep referencing the original .gdb and toolbox (what it is now) OR make a copy of the entire project folder at the new location.

Creating a package and then having to extract the package at a new location is cumbersome, and I don't understand all the files that are created in the process. I would prefer to have it be 1 operation.