Why you can’t sync with Import Records

Todd Geist has put together a great video showing how imports will let you down when you’re syncing records. Tricky stuff, but the basics are very well explained in this video. (Import failing begins at 11:40)

Todd’s article/video also includes a pretty cool demo file for showing how the sync / import works. It’s not fully fleshed out (i.e. it’s a demo) but it’s unlocked and has got a really nice FM13 interface. (July 2, 2014 – this  file is now the example file for GoZync 5.)

GoZync uses transactions to sync… this is why.

Todd’s series on transactions is also highly recommended.

Featured Posts

Follow Along

Stay up to date with the latest news & examples from SeedCode

Leave a Reply

Your email address will not be published. Required fields are marked *

Check out some of our other posts ...

DayBack for Supabase

FileMaker and Supabase We are very excited to be supporting Supabase as a datasource for DayBack Calendar. You can embed DayBack in your Supabase project, or see Supabase records alongside your FileMaker events in DayBack.

Read More »

Visual Buffers: a More Accurate Calendar

Buffers in DayBack let you define padding before and after your events so you can see the time you need, not just the time you booked. Instead of squeezing appointments into every available minute, your calendar starts to reflect the reality of how your day unfolds. Buffers is ideal for travel time,

Read More »

Add Jobs to a Mapped Route in FileMaker

See When Assets are Passing by Unscheduled Jobs Showing unscheduled items on the map lets you see when a route is passing close to jobs you need to schedule. As you click on each truck, you’ll see it’s route for the day and find unscheduled jobs that would be good

Read More »

Scheduling Teams and Equipment

Seeing Availability at a Glance We recently customized DayBack for a customer who wanted to consolidates all the decisions of team assignments into a single screen. When a dispatcher clicks on a job, they can schedule the entire field team (technicians, lead, vehicle, departure plan, and equipment) without leaving the

Read More »

FOLLOW ALONG

Stay up to date with the latest news & examples from SeedCode

© 2026 SeedCode, Inc.