Summary
Replacing File on Server DELETES REMOTE CONTAINER DIRECTORIES
Product
FileMaker Server
Version
13.03
Operating system version
Mac or PC
Description of the issue
If you have a hosted file that uses remotely stored containers do not do this!
To make changes to the file I created a backup of the file in question and then closed that file.
I made changes to the file none of which affected the remote containers or their directories.
I used the console to remove the hosted file and then used Filemaker to upload the file with the changes.
It appears that the act of removing the file from the server deletes the directory and ALL of the container files and the new file will recreate the directories the first time data is added to them.
This would seem to force users to make ALL changes on the hosted file. THIS IS SO DANGEROUS IT IS BEYOND RiDICULOUS
Expected result
Directories remain along with data
Actual result
Directories are deleted
Workaround
Looking for how to do this. This is so dangerous it is probably worth staying with Supercontainer......
dbail:
Thank you for the post.
"You can remove one or more selected databases with Closed status or delete empty subfolders. The selected databases are moved to the folder Removed_by_FMS/Removed. The Removed_by_FMS/Removed folder is created inside either the default Databases folder or the additional database folder depending on which folder the selected databases are in."
The remote container directories were not deleted, but moved to:
Databases\Removed_By_FMS\Removed\RC_Data_FMS\FILENAME
"If you remove a hosted file, upload a file with the same filename, and remove the second file, then FileMaker Server overwrites the first removed file with the second removed file."
For more information, please review page 108 of the FileMaker Server 13 Help Guide.
TSFalcon
FileMaker, Inc.