Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About sfpx

  • Rank

Profile Information

  • Gender
    Not Telling

FileMaker Experience

  • Skill Level
  • FM Application
    16 Client

Platform Environment

  • OS Platform
  • OS Version
    10.11 el captain

Recent Profile Visitors

2,576 profile views
  1. I added a script in the "Post-Sync Hub actions" section of the mirrorsync customization script and tried to pass the $$MIRRORSYNC_USERTOKEN variable as the parameter. The script does get executed but with a blank parameter. P.S. I only modified the script on the server and not on the device if that makes a difference...
  2. sfpx


    Great to know Thanks
  3. sfpx


    Forgot about that.. But it will eventually though. Pretty sure I read something about that .
  4. sfpx


    I understand that it would be quite the task to update MirrorSync to use the FM 16 REST API but I'm curious if it could be done and if this would result in a better overall performance.
  5. Got this kind of message twice this week. Not sure what it means and how to fix it. where XXX is an uuid with some user token
  6. sfpx

    Renaming devices ?

    That would be a really nice new feature . Thanks
  7. Is that possible to rename the device (the name that appears in the licenses list) without having to do an initial sync ? If I change the field clientname of the mirrorsync table, will it change the name in the mirrorsync config utility ? I'm asking because I always used the default naming but now I see that some devices end up having the same name and it's quite confusing when I have to delete a particular device. I would like to change it for the account name that is used to connect to the database. Possible or not ?
  8. I actually would remove the fields on the sync layouts only on the device version of the database . Should take 5-10 minutes of additional work each time I prepare a new offline version. I will test some initial syncs it to see if it's worth the hassle.
  9. I noticed that writing data is a bit faster when the layout has nothing on it. No object or field. Can we remove the fields from the sync layout on the device (iphone, ipad)? (I understand that the fields must be on the sync layouts on the server) Just a crazy idea I had this morning
  10. I may be tempted to test the Development license of fms 16. Limitations Does this apply to Mirrorsync ?
  11. I'm curious about this new feature. What I particularly want to know if the process requires an initial sync after the download of the new version .
  12. sfpx

    Sync Check Speed Improvement - Part 2

    How's the speed of EasySync compared to Mirrorsync ? We like Mirrorsync but we had troubles recently and the fact that it's an external app makes it harder to debug . We're looking at other products while we're waiting for a fix.
  13. 2 problems that may be related 1.Starting a few days ago I sometimes get an error message (Unexpected response from Mirrorsync server) . It seems to happen when I haven't synced in a few hours. When I retry 2 seconds after the error message it works just fine....apparently anyway. 2.We got a wrong deletion of a record that was just inserted in the same sync. In the log there was this line WARNING: Deletion scanning mismatch in NodeReference for hub node FileMaker Server ... with associated spoke node Client node .. on iPhone Go ... Deleted record count (1) - extra count (0) does not equal expected missing recount count (0). This will probably lead to false deletion scans on every sync after this. Not sure what that means and what is the cause of this problem but I must say that it's scary. I already sent the log to 360works but I'm trying my luck here as maybe someone already had this problem and knows the fix.
  14. Perfect. Thanks for the detailed answer.
  15. Thanks for the reply Jesse. What about containers ? From the documentation Should I convert my container fields into base64 text fields to avoid that ?

Important Information

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