Failed to open attachment

[CarsonG]

I am unable to open attachments in ArcPro for feature classes that have attachments or for hosted feature layers that have attachments.

I can open the map in AGOL or the hosted feature layer in AGOL and see the attachments. No issue opening the same attachments on a different computer.

[RhettZufelt]

Any chance you are clicking on either a feature with more than one attachement, OR, close enough that you are clicking more than one feature with attachments?

Pro 2.9.4 and later have a bug with HFLs where you are not able to do the above.  It will only allow you to click on a single feature with a single attachment, or it throws error.

If you select the feature(s), are you able to see/access the attachments in the attributes pane?

R_

[ShoNuff]

I am experiencing the same behavior with Pro 3.2.1 with feature class in our SQL Server enterprise geodatabase . I hope that this is fixed in the latest version!

[_John_DeLoretta]

We are seeing this same bug on our end with a file GDB on our local network. In Pro 3.2.2 my coworker cannot view the attachments in the 'Attributes' window.  They appear to be there but he gets a "Failed to open attachment" error message when trying to view them. The attachments do show up in the feature popups,though.  for me - the attachments show up fine in pop-ups and through the 'Attributes' window.  I'm using 3.1.0

[ClarkLangridge1]

We ran into this due to the odd way that Survey123 wants to handle multiple pictures on a survey.  For whatever reason, you have your feature class with a relationship class to a table, and then attachments are enabled on the table rather than on the feature class.  We found that in Pro, you have to have that intermediary table included in the map or else when you tried to view the attachments you would get an error message.

The kicker is that ArcMap doesn't require this; you can view the pictures just by having the feature class in your project.  Took us a while to figure out what was going on with that, since we have some users using ArcMap and some using Pro and we couldn't figure out the disparate behaviour.