nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Pro Network Folder Connection Alias

GraceUziallo

Hi All, we just upgraded to Pro 3.7 but have noticed the ability to create an alias for a Network Folder Location in the catalog is no longer possible, I'm not sure when this change happened, as I have checked a Pro 3.6 install and that is the same. Going further back to Pro 3.3, I can change/set an alias for a network folder. If you are using a local folder, the ability to set an alias is unchanged in all these versions.

Is anyone else noticing this? If so, wonder if it was an intentional change?

Network folder context menulocal folder context menu

Find more posts tagged with

Accepted answers

GraceUziallo

FYI if anyone hits this issue in Pro 3.7 - the issue has been identified as a defect:

BUG-000185245 - Missing “Alias” Option for Folder Connections

Status: In Product Plan

All comments

danielri

I can't speak to ArcGIS Pro 3.7, but the Alias option is working in ArcGIS Pro 3.6 SP 6 and SP 7 (released May3rd). Before you ask, yes this alias was assigned to a UNC path like \\myserver.mydomain.loc\mydata

GraceUziallo

Interesting, I just looked at another VM I have that had Pro 3.4 installed. Confirmed alias worked for a network folder location (\\server\ShareFolder, I then ran the updater in the app to go to 3.7. Once that finished, I opened the same project again and the ability create an alias for the same network folder was gone.

I then discovered if I went one folder deeper \\server\ShareFolder\SubFolder - the sub folder would allow me to change an alias. I wonder if Pro is recognising that folder is the root of a share and so behaves differently -it also has the folder icon with the green bit at the bottom? We also have some DFS shares accessed by \\domain\share$\GISShare which are fine.

danielri

The fact that it started working when you went one folder 'deeper' made me think about the current Microsoft Patch KB5082063 released in April and installed on most computers the first weeks of May that resulted in the failure of fuzzy domain resolution. Instead of \\server\ShareFolder\SubFolder try \\server.myDomain.loc\ShareFolder\SubFolder

GraceUziallo

Thanks Richard, I get the same results if I do \\server.domain.com\ShareFolder (no alias) but if I go to the subfolder, that is fine. Think I will just log a ticket on this and see if it's bug with 3.7 or .NET 10 which was also installed at the same time to enable the upgrade to 3.7 .

GraceUziallo

FYI if anyone hits this issue in Pro 3.7 - the issue has been identified as a defect:

BUG-000185245 - Missing “Alias” Option for Folder Connections

Status: In Product Plan

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.