【InField】Set Names for Uploaded Photos and Videos

Thanks ​@Shun Takase for sharing. We will get back shortly. I have forwarded the request to Infield team. 

Hi ​@Shun Takase, when and where does this happen? e.g. Is this outside or inside InField UI.

“ In most cases, even when checking the file name later, it is difficult to tell what the file actually contains.”

Marius

Hi , ​@Marius Biermann 
Thank you for your reply.

In this case, the situation is that users want to review the files outside of the InField UI after an inspection has been completed.
By “outside of InField UI,” I mean the main CDF search screen as well as custom applications that are commonly used by customer companies in Japan.

Files uploaded from InField are linked to assets. However, when reviewing those asset-linked files later, if they are all named something like “image.jpg,” it is difficult to understand at a glance what each image represents.
Of course, the description may explain the content, but having to open each file one by one to check the description can be time-consuming.

This is still at the idea stage, but for example, during inspections, users may take photos of equipment to capture its condition, and later use those images for analysis (such as evaluating equipment degradation). In such cases, having meaningful file names would reduce unnecessary preprocessing and make the data much easier to use.

Hi ​@Shun Takase! 

We have previously discussed also bringing in som preset namings (that you could later edit), to generally elevate the readability e.g. task name_date if created from a checklist or observation short description_date if created from an observation. Any thoughts on that?

Marius

Hi ​@Marius Biermann 

Thank you for your reply.
I think having preset candidate names defined in advance is a very good approach.

For items created from checklists, I agree that using “task name_date” makes sense.
If I may add one small request, it would be great if the date format were something easy to understand for us as well, such as 20260501 or 2026-05-01.

Regarding observations, we still have limited use cases within our company, so it is a bit difficult to picture the perfect naming pattern. However, “short description_date” seems generally reasonable to me.

One potential concern is that task names or short descriptions may contain characters that are not suitable for file names (such as dots). It would be helpful if there were some internal mechanism to prevent or sanitize such characters.

Great, thank you, your input is much appreciated!