A few of us at FIS were pondering the very same thing earlier this week.The file datatype while now available for adding to the forms isn't yet available (nor it is unknown if planned) for it to be available for use in a view or advanced find. If you are using tools such as XRMToolbox you can see the filename stored by executing a fetchxml similar to the following:<fetch> <entity name="opportunity" > <attribute name="XXX_dealvaluation_name" /> <attribute name="XXX_profsvcsaudit_name" /> <filter type="and" > <condition attribute="opportunityid" operator="eq" value="00000000-000-e911-a971-000d3ab98e59" /> </filter> </entity></fetch>Where XXX prefix is your org prefix and then the name that follows has the _name added to it by the system. In the above example there are 2 that we have Deal Valuation and Prof SVCS Audit that both have the field type of file.You can use a tool like the View Designer in the XRMToolbox to customize an existing system or user view to add the attributes of the new file type field(s) you have created - it is important to note that the column header in the view will not be presented however after you save and publish it into the system (you can't use the OOB customization tools to add these to a view). While this might be sufficient to add to a view the name of the file, it isn't very friendly for end users should they want to create their own views.
NOT EXACTLY FRIENDLY WITHOUT A COLUMN HEADING IS IT?A more friendly approach can be taken and create an additional text field to hold the filename that has been uploaded, and a datetime field to hold the date when it was uploaded. You populate these new fields using a Power Automate approach that will trigger when the entity you are working on is updated. Here is an example that will update fields on the opportunity record if a file is uploaded - note that the guid of the opportunity is looked up against the _objected_value in the fileattachments entity.
If you've found this thread useful, dive deeper into User Group community content by role