ArcGIS Pro 3.5: Bugs found

[RTPL_AU]

Here are some bugs that I've found after using Pro 3.5 for a few minutes. 

1. When using Copy > Paster Special to copy a feature class in a FGDB the new FC retains the alias of the old FC.
   
   
2. During an edit session, Pro will stop showing the edited geometry once an edit is completed (press F2, etc) and revert to showing the old geometry on screen until you save and refresh the map.
   You can still interact with the geometry in its new location (edit vertices will show the correct geometry while using the tool but revert to display the last saved version when you finish the tool operation.)
   
   This bug is extremely confidence inspiring to clients when you are sharing a screen during a VC to go over an earthworks design revision.
   
   
3. When copying text or numbers from a popup window you may get a leading space or tab character when you paste the selection into something else e.g. Excel, Notepad, etc.
   
   
4. There are still some PDF issues. When exporting a layout, an aerial image in ECW that is clipped to a boundary only partially displays in the PDF. 

These all occurred in 3.3.5 so nothing new.

[DanPatterson]

Were these reported as bugs previously?

They may not be picked up during Beta testing unless it is part of someone's workflow.

Report these, maybe they can be resolved a near term patch.

[RTPL_AU]

Esri are aware of these bugs as they've been around since 3.3 or earlier.

The leading space issue was lodged for 3.1 (IIRC) and I received a notification last week that it was fixed in 3.2. (LOL?)  It wasn't and was reproduceable by the Esri AU support person while on the phone with me Monday in 3.3.5 as part of their follow up. 

"Workflow' went out the window years ago. Some of the issues with Pro are just bad code or bad leadership.
My gut feel is that they are pushing too hard to launch new versions every few months rather than taking the time to create stable release versions with long term support. 
We've just received 3.5 and there are still orgs on 2.x due to fundamental breakages or issues with new versions. It's truly a case of once you find a version that works stably for your scenario you stick with it because who knows what will break next.

I have an Idea lodged that Esri should pivot to a Long Term Stable + Short Term Feature Growth cadence model so that we (the paying customers that are the reason Esri exists) can pick if we prefer a stable cadence (i.e. non changing + non-crashing)  or need the fancy new beautiful feature but accept that it might blow up something else.

Apologies for the rant - I haven't had red cordial in a while and thus tend to not read marketing brochures with tinted glasses much these days.....

[DanPatterson]

Sorry, I misread and thought that these were new bugs.

It would be nice if there was a BUGS_NOT_FIXED to the 

Release notes for ArcGIS Pro 3.5—ArcGIS Pro | Documentation

under Issues Addressed list

It would be much easier to keep track of bug version versus current release version

[RTPL_AU]

@DanPatterson   Agree - Making it easier to track bugs will make it so much easier to figure out what's going on. 
I guess you can look at the bug knowledge base and chase through what is still open.  Filtering bugs by detailed versions (reported in vs fixed in) isn't possible last time I checked.

As you're sort of retired maybe you can compile a blog post from all their sources?  Maybe they'll give you a discount on your licenses....... 

If they wanted to make their support site AI useful this would be a start... Maybe not. It will probs hallucinate that all's well and the weather's good 🙂

[RTPL_AU]

Anybody else finding that Pro 3.5 will stutter for a few seconds when you try to switch back to it when you've done something in another app?

Also seems that there is a problem with some unresponsiveness when using copy - example is to copy the layer name in the layer properties window so I can paste it somewhere else. 
Select text > right click > Copy > Pro hangs a second or so (verified in Diag Monitor as Unresponsive) > continue to do what you wanted....

I'm on Nvidia Studio Drivers 566.36 which seems to be recommend as having less issues than some of their recent releases.  Will try between DX11 & DX12 to see what rolls best. 

[RTPL_AU]

If Pro 3.5 is partially behind another application window and you click in a blank part of the Ribbon or QAT, Pro will not come to the foreground. You have to click inside another part of the application window.

Clicking in the pink areas does nothing when Pro is behind another app (File Explorer in this case):

[Scott_Harris]

Hi @RTPL_AU 

Regarding item 2,

During an edit session, Pro will stop showing the edited geometry once an edit is completed (press F2, etc) and revert to showing the old geometry on screen until you save and refresh the map.
You can still interact with the geometry in its new location (edit vertices will show the correct geometry while using the tool but revert to display the last saved version when you finish the tool operation.)

The ArcGIS Pro Editing team is not aware of a bug that fits this description.

Do you have a bug number that I can look into?

If not, I have many more questions, but I'll try to keep it to a minimum.

1. Is this with every workspace type (ex. File Geodatabase, shapefiles, feature services, enterprise geodatabases)?
2. In every project?
3. Does clearing the display cache resolve it? This button in Options > Display:

Thanks for any more info!

-Scott

[JoshuaBixby]

When discussing defects, it is helpful to provide the bug number.  Most defects, although not all, are searchable through Esri Support website and can be linked to in forums/communities like this one.

[RTPL_AU]

@Scott_Harris   @JoshuaBixby 

Item1:  Lodged as an idea by others in 2022 (IIRC) and also filed as a bug with local reseller (who thinks it is an enhancement request).  Rename a FC in FGDB and Alias is updated. Paste Special and rename copied FC = Alias not changed? Consistency much?

Item 2: If a bug gets stuck with the local monopoly reseller then no public bug nr will be available. Now you know of it as well.

Item 3: To quote Esri Inc:

BUG-000166795 - Undesired additional space when copying a numeric value of a record from the attribute table field popup in ArcGIS Pro 3.2.
Status: Non-Reproducible (Learn More)
Additional Information:  Issue is not reproducible in versions 3.1 or higher.
Alternate Solution:  Delete the space manually after pasting it anywhere else.

A few things got lost in translation - it occurs for any data type. Local reseller has been able to replicate repeatedly on multiple Pro versions.

4 PDF Issues - nothing lodged yet as it seems some of it overlaps the multitude of 3.4 pdf bugs.

Lagginess in UI - no case lodged yet for this specific behaviour. Only installed it yesterday and will see if there is a pattern I can detect. It's not the hardware spec if anyone is wondering.

Clicking in ribbon or QAT not bringing Pro to the foreground - case lodged with locals.

@Scott_Harris re editing bug.
I use FGDB (95%) & SHP most often. As far as I can tell it is related to having certain types of symbology in a map.  I suspected coordinate systems and transformations but that seems to be coincident but unrelated.

It is intermittent - partial behaviour map would be to open a new project, add FC, start editing, things work, save edits, add more data, save project., close Pro, come back ,open Pro, open project, start editing, things work, save edits, save project, start editing, things don't work and likely won't for that project again. Open new project, add data from catalog, start editing, things work, ..... and so it goes.
We have near decades of ArcMap projects & styles that get carried over as clients come back or projects evolve. Working through all of that to find what triggers Pro to hose itself should not be my job. You guys develop it and should know exactly what could trigger specific behaviour. Forcing us to go through local resellers that gatekeep the info you get, again, is not a problem your clients have caused.

Workarounds such as clearing cache etc becomes unworkable very quickly - do I clear cache before every edit session, during editing, after editing? Who pays for the time wasted doing housekeeping that Pro should be able to do itself?
I have had formal feedback on Pro UI lagginess bugs to "work slower"
Leading space bug advice = "Delete the space manually"

These sorts of things are why people still use ArcMap after Pro has been around for a decade.

Yes, I am frustrated.