Thank you for your post.
I was able to reproduce this behavior by following these steps:
1. Created test.fmp12
2. Created a Container field "Container" set with open, external storage.
3. Created a Text Calculation Field "FileName" w/ calculation GetContainerAttribute(Container ; "File Name")
4. Created a new record and imported Test.png
5. Created a new record and imported a different image labeled Test.png
Additionally, a report has been sent to Testing and Development for review. When I receive further information, I will post it to this thread.
Thank you for your patience.
It seems this is expected behavior FileMaker Help topic for GetContainerAttribute: "filename : The name of the file inserted into the container field". For the path, you may want to continue pulling the "image" and parsing the filename for the path from that.
Thank you for the response. One additional sentence explaining the difference between file name and original file name would be a good addition to the documentation. Especially since I can rename that internal file name as well as the name of the file itself by using Base64Decode. Base64Encode and it is no longer the original file name of the file inserted.
You can get the filename with
GetContainerAttribute(Container ; "ExternalFiles")
But there is another problem that inserting same file into different record, the function returns empty string on the record.
Tested on FM15 / Windows7.
When there is a conflict of names in a directory the program will name MyFileName.jpg to MyFileName_1.jpg. If this occurs the GetContainer..... command does not report that change. It reports MyFileName.jpg as still the external name.