Removing a geodatabase from a project also removes it from my favorites

[BMCGIS]

When I remove a geodatabase connection from my Pro project, it also removes it from my Favorites in Pro 3.2.1. This happens for both file geodatabases and enterprise geodatabases.

This doesn't make sense, the Favorites list should persist in all projects, whether or not I add or delete any of them from the specific project I am working on.

I don't believe it worked this way in previous versions of Pro. Is anyone else having this issue or is there anything I can check in settings or other places to fix this?

[DanPatterson]

Use project favorites—ArcGIS Pro | Documentation

provides some discussion that may be pertinent

[BMCGIS]

@DanPatterson  Thanks for the reference. I read through it, but it doesn't cover the behavior I am describing.

I also read through the documentation on Remove or delete project items, but it doesn't say that removing a project item will also remove it from Favorites.

[BMCGIS]

These are the steps to reproduce the issue:

• In a Pro project, in the Catalog pane, on the Project tab, right-click on the Databases group and select Add Database.
• Navigate to and select any geodatabase (other than this project's home geodatabase).
• This adds the geodatabase connection in the Databases group.
• Right-click the geodatabase connection and select Add to Favorites.
• On the Favorites tab of the Catalog pane, you will now see that the geodatabase connection has been added.
• Save and close the project.
• Reopen the project.
• In the Catalog pane, on the Project tab, right-click on the geodatabase connection and select Remove from Project.
• On the Favorites tab of the Catalog pane, you will see that the geodatabase connection has now been removed from Favorites.

I have tried several different combinations of the steps, creating the initial connection in the project vs. in the favorites, using New Database Connection to connect to an enterprise geodatabase and saving the connection file to my Favorites folder on the C drive. I am using Pro 3.2, but also tested this on Pro 3.3 and on a coworker's computer and got the same result.

No matter how I do it, I find that if I remove a connection from a project, it removes the same connection from the Favorites as well.

Are there any configuration or settings I should check that might be causing this? I can't believe this would be the intended function of the Remove from Project action.

[DanPatterson]

yes, in Pro 3.4, it removes from Favorites.

So... the issue seems to be whether this is the expected behaviour or changed behaviour.

Tech Support would be your best option.  They may suggest a wording addition in the help files if this is expected, or open an issue if it is not.

Good luck

[BMCGIS]

Thanks, Dan! I appreciate the confirmation that it's happening for you in Pro 3.4 as well. I will follow up with Tech Support as soon as I have a chance.

[tvanloan]

I'd be interested to know what you find out. I've been having this problem on multiple computers since at least 3.1.3 but it's not a big enough problem for me to want to open a case. At least one other person in my department hasn't noticed this problem (I haven't asked the others.)

When you right-click an item in the project, the only removal option is "Remove from Project". When you do the same in the favorites, the only option is "Remove from Favorites". It doesn't make sense that removing something from the project also removes it from favorites.json and there are no warnings that it is doing so.

[mthompson]

Also experiencing this. It makes no sense for removing something from the project to remove it from favorites as the favorites are available across all projects. I don't know if it is a bug or is working as designed, but either way it needs to be changed. Our favorites should be a completely separate thing.

[AmyDunn]

I have the same issue where removing a folder connection from the project also removes it from my Favorites. I am using 3.4.2.

[AndrewNichols_]

Finding this a pain since upgrading from 2.9. Is there an official bug report for this, because it cant be expected behaviour?