I suppose this is an old issue since I recall reading of people having problems with photos in container fields.
A client is having all imported photos from an iPhone being treated as landscape which rotates the portrait photos. The problem was shown to me after the iPhone photos were downloaded to the desktop and then imported into a container. The file itself is a marvel of overcomplexity using, rather avoiding using, SuperContainer. The table itself is a marvel of too many calculations and I suppose some of them are triggered during the import or inserting of the photograph. I did try a new table with just the container field and Filemaker Go 13 on their iPhone. Same problem. I bought a Touch and same problem using Go 13. I used an iPad Mini, same problem when taking the photograph inside a container field.
Using a local file on the Touch or iPad, no matter how I hold the device, the photos are shown correctly. I am using a developer version of 13 server and I have no problem when using Go 12 or 13.
So, it seems the problem is Server 12 as being used.
I haven't had access to check server version, etc. But from what I was shown, Filemaker Server 12 is being run on an older windows server which is also serving all of the files and clients, 10 to 20. And so it is, I am sure, not properly set up. Ocassionally during the day Filemaker Pro 12 Advanced seems to act up.
So, is using Go 13 with Server 12 a problem with photographs?
Is there any easy method of righting the wronged photographs in the container? Since it is most likely a wrong flag in the container data, can that be corrected? Maybe Troi can adjust the metadata in a global container?
Has Filemaker, Inc. provided an answer that I haven't found?