Transactional
GoZync4.Transactional History
Hide minor edits - Show changes to markup
Why "import records" doesn't work: transactions and syncing.
Wikipedia definition: http://en.wikipedia.org/wiki/Database_transaction
filemaker-go-and-transactions and inventory-transactions.
filemaker-go-and-transactions and inventory-transactions.
Wikipedia definition: http://en.wikipedia.org/wiki/Database_transaction
The FileMaker Transactions reference page: https://www.geistinteractive.com/filemaker-transactions
The FileMaker Transactions reference page
filemaker-go-and-transactions
inventory-transactions
filemaker-go-and-transactions and inventory-transactions.
\\ http://en.wikipedia.org/wiki/Database_transaction
http://en.wikipedia.org/wiki/Database_transaction
\\ filemaker-go-and-transactions
filemaker-go-and-transactions
Wikipedia definition: http://en.wikipedia.org/wiki/Database_transaction
Wikipedia definition: \\ http://en.wikipedia.org/wiki/Database_transaction
filemaker-go-and-transactions
\\ filemaker-go-and-transactions
Wikipedia definition:
http://en.wikipedia.org/wiki/Database_transaction
Wikipedia definition: http://en.wikipedia.org/wiki/Database_transaction
Wikipedia definition: \\http://en.wikipedia.org/wiki/Database_transaction
Wikipedia definition:
http://en.wikipedia.org/wiki/Database_transaction
Wikipedia definition: http://en.wikipedia.org/wiki/Database_transaction
Wikipedia definition: \\http://en.wikipedia.org/wiki/Database_transaction
filemaker-go-and-transactions/
inventory-transactions/
filemaker-go-and-transactions
inventory-transactions
http://www.geistinteractive.com/2010/07/21/filemaker-go-and-transactions/
http://www.geistinteractive.com/2010/04/21/inventory-transactions/
The FileMaker Transactions reference page: https://www.geistinteractive.com/filemaker-transactions
Older Articles: filemaker-go-and-transactions/
inventory-transactions/
A transaction means that everything associated with a record stays with the record. In a sync context that means the record, and all its related records, are bound together in an indivisible package. You, as the developer, control how far across the graph – how many tables – that package spans. Transactions can also include any scripted edits that have to happen on either the mobile or hosted side – scripts like notifications or logging.
All of that goes with the record, or none of it goes. Outside of a transaction, some or all of that could happen per record, per sync.
When you have a shaky connection, or turn off your device mid-sync, you could sync an invoice, but not its line items. Or sync the invoice and its line items, but not send the notification. Or sync the invoice, fail the line items, and the send the notification.
A transaction means that everything associated with a record stays with the record. In a sync context that means the record, and all its related records, are bound together in an indivisible package. You, as the developer, control how far across the graph – how many tables – that package spans using the "required" column on GoZyncHosted's configuration tab. Transactions can also include any additional set fields that have to happen on either the mobile or hosted side--things like notifications or checkout.
All of that goes with the record, or none of it goes. Without transactions, some or all of that could happen per record, per sync. Fo example, when you have a shaky connection, or turn off your device mid-sync, you could sync an invoice, but not its line items. Or sync the invoice and its line items, but not send the notification. Or sync the invoice, fail the line items, and the send the notification anyway.
A transaction means that everything associated with a record stays with the record. In a sync context that means the record, and all it's related records, are bound together in an indivisible package (you, as the developer, control how far across the graph--how many tables--that package spans) which can also include any scripted edits that have to happen on either the mobile or hosted side: scripted things like notifications or logging.
A transaction means that everything associated with a record stays with the record. In a sync context that means the record, and all its related records, are bound together in an indivisible package. You, as the developer, control how far across the graph – how many tables – that package spans. Transactions can also include any scripted edits that have to happen on either the mobile or hosted side – scripts like notifications or logging.
When you have a shaky connection, or turn off your device mid sync. You could sync an invoice, but not its line items. Or sync the invoice and its line items, but not send the notification. Or sync the invoice, fail the line items, and the send the notification.
When you have a shaky connection, or turn off your device mid-sync, you could sync an invoice, but not its line items. Or sync the invoice and its line items, but not send the notification. Or sync the invoice, fail the line items, and the send the notification.
Transactions are what let us say that when you see "uploaded" on a zynced record in your mobile file, you know that record made it to the host / server.
GoZync eliminates the possibility of incomplete syncs by enclosing all of the data within a transaction envelope. If a transaction completes a Zync, it's complete. If it fails because of connection problems, it leaves the data untouched.
Transactions are what let us say that when you see "uploaded" on a Zynced record in your mobile file, you know that record made it to the host / server.
Todd Geist, co-author of GoZync pioneered the concept of transactions for FileMaker Pro. Read more on this here:
Todd Geist, co-author of GoZync, pioneered the concept of transactions for FileMaker Pro. Read more on this here:
http://www.geistinteractive.com/2010/04/21/inventory-transactions/
http://www.geistinteractive.com/2010/04/21/inventory-transactions/
All of that goes with the record, or none of it goes.
Outside of a transaction, some or all of that could happen per record, per sync.
You could sync an invoice, but not its line items. Or sync the invoice and its line items, but not send the notification. Or sync the invoice, fail the line items, and the send the notification.
All of that goes with the record, or none of it goes. Outside of a transaction, some or all of that could happen per record, per sync.
When you have a shaky connection, or turn off your device mid sync. You could sync an invoice, but not its line items. Or sync the invoice and its line items, but not send the notification. Or sync the invoice, fail the line items, and the send the notification.
A transaction means that everything associated with a record stays with the record. In a sync context that means the record, and all it's related records, are bound together in an indivisible package (devs control how far across the graph--how many tables--that package spans) which can also include any scripted edits that have to happen on either the mobile or hosted side: scripted things like notifications or logging.
A transaction means that everything associated with a record stays with the record. In a sync context that means the record, and all it's related records, are bound together in an indivisible package (you, as the developer, control how far across the graph--how many tables--that package spans) which can also include any scripted edits that have to happen on either the mobile or hosted side: scripted things like notifications or logging.
Transactions are what let us say that when you see "uploaded" on a zynced record in your mobile file, you know that record made it to the host / server.
What does it mean that GoZync is "transactional"?
A transaction means that everything associated with a record stays with the record. In a sync context that means the record, and all it's related records, are bound together in an indivisible package (devs control how far across the graph--how many tables--that package spans) which can also include any scripted edits that have to happen on either the mobile or hosted side: scripted things like notifications or logging.
All of that goes with the record, or none of it goes.
Outside of a transaction, some or all of that could happen per record, per sync.
You could sync an invoice, but not its line items. Or sync the invoice and its line items, but not send the notification. Or sync the invoice, fail the line items, and the send the notification.
While you'll see this on FileMaker networked solutions sometimes (usually as incomplete records, or totals that don't match) you see it much more often in distributed (Go) solutions where disconnect and record lock can be common.
Learn more about transactions.
Todd Geist, co-author of GoZync pioneered the concept of transactions for FileMaker Pro. Read more on this here:
Wikipedia definition: http://en.wikipedia.org/wiki/Database_transaction
http://www.geistinteractive.com/2010/07/21/filemaker-go-and-transactions/
http://www.geistinteractive.com/2010/04/21/inventory-transactions/