It would also be good to be able to use Arcade to calculate the intended file name for an attachment. For photos the name might be an asset name/code appended with a date/time or a date and an automatically incremented integer (for the sequence in which the photo was taken during the current data collection session).
An option to date-stamp photos collected in field maps would be very useful, as would the naming convention mentioned above by Mike_K. This ups the value of collecting photos tremendously.
Having this option combined with an expression using the other suggestion of Sequential values for Field Maps - Esri Community would be a great way to keep all your photos uniquely organized when extracting them from the fgdb.
What I would love is that you can setup the Photo to auto name to a field in your point file so it would name ex: BigBearUnit1_Photo1. "BigBearUnit1" is being auto pulled from the point that your adding in collector/field maps.
This is a critical function for us. We have to extract all of the photos from Field Maps in order to use them in our project reports and to archive them. The only way to do that currently is using a script in Pro (that's another issue). But it needs the photos to have a unique name. Otherwise, you get a folder of jpgs and no way of knowing which point feature they correspond to and you have to spend a lot of time opening photos and clicking on points to find matches, then rename the photos.
I would prefer even if you could select a field from the feature class from a drop-down list, where you could select a field such as "Name" or "ObjectID" and it would auto-name the photos with the corresponding field. The result would be similar to featurename_1, featurename_2, so that when photos are exported into file explorer or etc, is it easy to know what feature you are reviewing.
Our team has a project that requires all attachments have a very specific name based on a field in the parent feature. We currently "solve" this using a Python cursor to ensure all attachments are named correctly. Not only does this take several hours to chew through the table but every renamed attachment creates a new record in the archive table, effectively doubling the size of every attachment. Enforcing the proper name via Arcade at the database level would solve all of these issues.
I really like @MapsInRaleigh's suggestion above. We have created a tool that exports and renames attachments in Pro based on a field in the parent attribute table, but it would be better if we could name them appropriately from the start. That way when users save individual photos themselves from a dashboard or Attachment Viewer or whatever, they'd already be named something meaningful and they wouldn't end up with a bunch of copies of photo1.jpg in their downloads folder.
