Jump to content

sfpx

Members
  • Content Count

    139
  • Joined

  • Last visited

Community Reputation

0 Neutral

About sfpx

  • Rank
    member

Profile Information

  • Gender
    Not Telling

FileMaker Experience

  • Skill Level
    Intermediate
  • FM Application
    16 Client

Platform Environment

  • OS Platform
    Mac
  • OS Version
    10.11 el captain

Recent Profile Visitors

2,743 profile views
  1. What would be the impact on existing users if I remove tables from the sync and edit the mirrorsync scripts on the server ? I would not delete the actual layouts or tables. Would that delete records on the device or the tables would just not be synced even if they have not updated the mirrorsync script on their device ?
  2. Not really willing to do that I will eventually test it on a test database if I got some spare time. Now , it's a bit off topic but I found out that a relation sort can greatly impact the filter speed if your filter is looking for a related field even if if it's not the related table that is sorted but the sync table itself. It's really a strange filemaker behavior. Example: TableA-TableB TableB is sorted in the relation You are on the TableB layout and you perform a find on TableA. The sort will slow down the operation even if it's not TableA that is sorted but TableB. Pretty annoying stuff but it's good to know I guess.
  3. I would like to change the table occurrence of a sync layout. 1.The layout would remain the same, same fields (but from a different occurrence). 2.The filter would return the same records just faster and on a different table occurrence. Ex: Sync layout: TestLayout Original table occurrence: Test New table occurrence : SyncTest ( occurrence of test) What would happen to the users who haven't got the new version of the database and sync? Would that cause problems because they are expecting records from test and get records from SyncTest or would that work just fine because they actually get the expected fields ?
  4. Excellent. I discovered 2-3 layouts that were a lot slower than the others. The filters were based on unstored calc fields. I will change that. Thanks for the tip.
  5. I noticed that this step is taking quite a long time. Any way to speed it up ? This is with an ios---fm server (v 16) sync.
  6. sfpx

    Foreign Key Mapping

    Thanks a lot for the detailed answer. I will check my relations instead of removing them then .
  7. If we use UUID's for all our key fields can we remove all the relations from the foreign key mapping section ? If so, would it result in a smaller script and a slightly better performance ?
  8. sfpx

    Filtering on the spoke ?

    That's what I thought. Thanks
  9. Can I filter records without having them deleted on the spoke by the sync ? Let's say I have a table "Things" with a field "User" and I want to sync all the things of a particular user but would also like to keep the records of User 'Default' without having to sync them (there are many , they don't have to be synced and they would be included in the empty database). I know I could set the filter to User=$User or User="Default" but would like to set it to only User=$User If I set the filter in the "FindChanges" section of the mirrorsync customization script, will the filter be applied to device data too or only on the hub and all the default user things will end up being deleted ? Hopefully I explained it clearly enough. Thanks
  10. sfpx

    REST API

    Now that FM17 API supports scripts I was wondering if you looked at the possibility to use it in MS and if you think that it would speed up the syncs ?
  11. sfpx

    Partial sync

    We have some sort of an invoice that the customer needs to sign. It's created on the device and needs a serial number that we get back from the server in the sync customization script. The problem is that a full sync can be quite a long process (customer is waiting for the sync to finish) and it's not needed just to get the serial number. So what I want to do is to sync only the invoice record to get the serial number and sync the related records later at the end of the day. I guess that we may use the filemaker data api to get it but I would rather use mirrorsync.
  12. sfpx

    Partial sync

    Thanks What about device registrations ? Do I need to double the device registrations ? If I sync using config 2 will the records be marked as synced for config no 1 What about device data ? Is it shared among the configs. I'm a bit confused
  13. sfpx

    Partial sync

    From the documentation How does it work exactly ? Should I create a new configuration in mirrorsync without any device registrations on it , copy the scripts and use them to sync instead of the main sync script ?
  14. sfpx

    Migration to a new server

    Thanks for help. The thing is that I would like to avoid having to do initial syncs. We currently have in place an update system that works. It installs an empty version of the database on the device and imports all the data from the previous version (including the mirrorsync table). This way, users still can sync normally after an update. My idea : 1.Change my current mirrorsync config to point to the domain name instead of the ip address 2.Wait until everyone has the new version that syncs to the domain name 3.Stop mirrorsync on the current server 4.Install mirrorsync on the new server 5.Copy everything related to mirrorsync on the new server (device sync data , logs etc) 6.Change the ip associated with the domain name 7. Wait for propagation 8.Users sync to new server Could that work ?
  15. sfpx

    Migration to a new server

    That is correct. The new server is not set up yet. Ideally users would still continue to sync to the old server and gradually , when they update to the newest version would sync to the new server. But I understand that it's probably more complicated because of the licensing issues , would necessitate a server to server sync and would also probably necessitate an initial sync on the new server. I would not mind if I had to hard stop all the syncs for an hour or 2 if it means that I can import de device sync data on the new server and they can continue to sync normally once I started mirrorsync on the new server (after I changed the ip associated with the domain name...not sure how long it takes to propagate). Of course with this 2nd method I would need to make sure all the users have the version that syncs on the domain name before stopping mirrorsync and start the migration. I do not really want to increase the number of users. It's just that I understood that I can not install the same mirrorsync license on 2 servers (at least that's what I read somewhere) so I would actually need to buy a new license with the same amount of users if I want both servers to sync at the same time. Maybe I got that wrong. Thanks for your help.
×

Important Information

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