Jump to content

mdavis6537

Members
  • Content count

    56
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mdavis6537

  • Rank
    member

Profile Information

  • Gender
    Not Telling

FileMaker Experience

  • Skill Level
    Intermediate
  • FM Application
    15 Advanced

Platform Environment

  • OS Platform
    Windows
  • OS Version
    10

Recent Profile Visitors

1,577 profile views
  1. Thanks Jesse I will update my script accordingly.
  2. @Jesse Barnum Jesse I know this is an old post, has this changed in MirrorSync 3? I am using this and I seem to get a code 0 whether successful or unsuccessful on the sync. Just wanted to make sure it was still accurate. I am using Get(ScriptResult) Thanks.
  3. I was able to resolve this by checking the mirrorsync table for any records.
  4. Is there a variable I can check against to see if its an initial sync or not? Initial sync meaning the first time the user has done a sync with this file. Reason: MirrorSync is telling me it cant sync (the first time) because there is records in the database. I do have one record which is used in my update process from an old file to a new file. So I just want to delete that record before the first sync to resolve this error. Thanks. Edit - I guess I could just check for any records existing in the mirrorsync table, correct?
  5. Syncing after importing records

    Thanks for the replies. I follow what you are saying but currently I am doing my updates a bit differently using a blank (no records) file distributed to the users instead of having them download the hosted mobile file. We only keep 30 days worth of records on the iPad, so I am not sure its a huge deal if it has to go back and check all the records. Perhaps I need to change my approach but this is how I do updates today. I work on the updates to the new offline file for the iPads on my desktop. When its ready to deploy, I delete all the records in it so its completely blank. I send it out to all the iPads through mobile device management, and once they get it and sync, an script runs that imports all the records from their old current file and puts them in the new file, then deleting the old one. So since users are not starting out by downloading the hosted mobile file, I am not sure that setting the mirrorsync record would help. Whats happening is they do the update and then mirrorsync deletes all their records that were imported and re-downloads them from the server. Perhaps if I copied over their MirrorSync record when doing the update that would prevent that from happening instead of starting with it blank?
  6. Syncing after importing records

    Thanks Tsiry, Its seems this step is the one I am not doing: After the import, create a new record in the MirrorSync table on the hosted database. Set the type to 'Server'. Modify the sync4 field (you'll need to switch to layout mode to see which one that is), and set it to the timestamp when you ran the import, using the format 'YYYY-MM-DD hh:mm:ss' (in 24 hour time). Note: If you are not syncing with FileMaker Server (ex. MySQL<->FileMakerPro/Go) you will make this change in the offline file. However, that is going to prove difficult. The import into the offline file is dependent on when the user downloads the update. I wont have any idea when they did the import, and it will be different for each user. I could run a script on the server to create this new record, but it seems like that might cause problems. I guess I dont know enough about what is happening in this particular process to know what to do - can you shed any more light on it?
  7. Hello, I am using MirrorSync 3 with about 10 iPads. On the iPad solution, I have an update script that installs a new version of the file. As part of that process, all records are exported from the old file, and imported into the new file. What is happening is that after I release an update, MirrorSync on the iPad is deleting all the records and then inserting them all again after this update process is completed. I am assuming that something I am doing during the update process is confusing mirrorsync and it just decides to delete everything and re add it. Here is the process my update script goes through: Old file: Go to every layout and "SHOW ALL RECORDS", then "UNSORT RECORDS" New File: go to every layout and DELETE ALL RECORDS (just in case) Then, go to each layout and IMPORT RECORDS Then I sort the records, go to the last record to get the primary key, and SET NEXT SERIAL VALUE to the next value after this key. (I am currently not unsorting after this, maybe I should be?) Thats pretty much it. From there I delete the old file and start the sync, and everything gets deleted and re-inserted into the new file despite my attempt to prevent that by importing all the data. Is there anything I am doing that MirrorSync might not like and would cause it to completed re-insert all the records in all the tables?
  8. Great, thanks Jesse. I'll do some testing and hopefully it all works seamlessly. Thanks!
  9. Thanks Jesse. I assume the internal IDs are not the same as the Primary Keys in the database, right? (P.S. Is there any documentation that explains how all this process works? Would love to have a better understanding). One thing mentioned in the article is that you have to "show all records" for each table. I am wondering if that is going to screw up the order of the internal record IDs and cause issues. Do you have users using another update process? I am definitely open to suggestions.
  10. Hi All, In the process of rolling out our solution under the Filemaker SDK so it will appear more like a "native" iOS app. One of the things I want to include this time around is a way for our users to update the app. Currently looking at this process which basically adds another filemaker file, exports all the records from the old file to the new one, and then deletes the old file. My question is: If I use this process, what do I need to be aware of with MirrorSync to make sure that I dont run into any sync issues? All the timestamp data would be transferred. But I am not sure about whether the "next primary key to be used" will transfer over, I may have to script that. Is there anything else I need to make sure transfers over, or any other potential issues to be wary of? Thanks.
  11. I see in the patch notes in 2.6 that fixes were put in for duplicates. I am still struggling with issues with this, though i have had issues before this patch as well. I just had a new user get an ipad. Gave him the most recent copy of the file, downloaded using the MirrorSync client. Hit sync, it goes through successfully, and somehow managed to duplicate records for about the last 30 customers entered. I know this sync caused it because it was fine before and I looked immediately after syncing to see this (see picture). Whats worse is it seems somehow some child records are attached to one, some to the other (different tables). This is going to take hours to fix. I cant go to a backup file without losing all data entered today, which is not an option. I just dont understand why this is happening. This was a brand new file, there should have barely been any changes to even sync, and somehow it duplicates all these records. What a mess...
  12. A few mirrorSync 2 questions

    Great thanks- I will see if I can find it!
  13. A few mirrorSync 2 questions

    @Jesse Barnum Thank you very much for the reply Jesse. On #3 - I am wishfully hoping that this apple SDK will pan out and I can put my solution on the app store, with an option to sign up for the syncing with a paid plan. Any recommendations to go that route? How hard would it be to replace the UUID with a field? Is it in multiple places? The database and sync fields would be the same for all clients.
  14. Hi I have a few questions as an existing MirrorSync user: On my mobile file, to keep my size down I would like to get rid of all the layouts that are for the computer. Can I delete all those in my mobile file if I keep the sync layouts? The tables would all be the same, I just want to delete the layouts I am not using for mobile. Is there a way to only keep certain records on the mobile device to reduce the size? For example, I would like to only keep records that are within the last 30 days. Can I add this to my customization script? I dont want to delete them on the server, only the mobile file. Lets say I want to have mutliple clients of mine using mirrorsync. I will have multiple installs of Mirrorsync on the server as I understand it. Is it possible to have the same Sync script steps loaded for the different clients and have a field in the customization script that defines which client they are and which database they should sync with? Like a key that I would provide and have them input it? Thanks very much.
  15. Question about duplicate records

    Ok I may try that. I was also thinking about adding in a quick find check after my import to make sure there are no duplicates and throw and error if there are. Thanks for your help.
×

Important Information

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