Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×
The Claris Museum: The Vault of FileMaker Antiquities at Claris Engage 2025! ×

Recommended Posts

Posted

Hello All,

I am running my solution on FM Cloud 2024 and am using Filemaker Pro 2024 on our local machines. I have created a developer copy of my database to add and test new features. In the past I have made changes, tested them, made notes on exactly what I did then made those changes in the production version. 

This time however I have made a complete overhaul including new themes and layout designs. To recreate all those changes in the production version would be a nightmare. My plan was to create the new version, use the data migration tool to move all the data over and simply replace the old file with a new one. This has proved to be quite challenging. I have added another database, a "dummy" if you will with just a few fields and data to the cloud and tested various ways to replace it. I have renamed the file with "_OLD" and tried to rename a restored backup the same name but it wouldn't let me. I have tried to download a backup, close the hosted one, rename the backup and upload the new version but it tells me that it already exists and gives me no way to overwrite or replace it. 

I must also say that I have a starter file on each of my users computer that simply launches the cloud hosted file. The starter file is in the extension folder for Filemaker on the users machine. I have created a shortcut with our company logo and database name on their desktop so they just have to double click it to launch and don't have to open Filemaker, go to hosts and find the file. This causes another concern . I need to be able to use the same file and shortcut so I don't have to log into every users machine to install the new starter file. 

The only option I have tried that "seems" to work is to download a backup of the developer file, remove the encryption. Create a clone, migrate the data into the clone, rename the clone, download a copy of the production file in case something goes horribly wrong, close the production file, remove it, then upload the new version from my desktop. It appears to work and the shortcut seems to still work but it seems like there should be an easier way.

Can anyone tell me of an easier way or is this it?

Any help would be greatly appreciated, Thanks!

Posted

Well, then, a way forward is to use the api. We’re looking to support that, but don’t yet. 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.