Deletes
GoZync5.Deletes History
Hide minor edits - Show changes to output
Changed line 41 from:
"TOName=" & $RelatedTOName; \\
to:
"TOName=" & $TOName; \\
Changed lines 31-43 from:
If you want to manage the deletion of mobile records yourself, you can turn off GoZync's management of it. Simply add an "Exit Script" line at the beginning of the script "Delete Records Not In This List ( $IDsToKeep )" in GoZyncMobile.
to:
If you want to manage the deletion of mobile records yourself, you can turn off GoZync's management of it. This can make some syncs faster as GoZync won't be building a list of all the IDs that should be on the mobile device.
1. Add an "Exit Script" line at the beginning of the script "Delete Records Not In This List ( $IDsToKeep )" in GoZyncMobile.
2. Edit the script "Get IDS Needed For Sync PSOS" in your hosted file and disable the block of lines beginning with the first instance of the comment "gather IDS" (about line 48) and ending with "end loop" (about line 91).
3. The right after that end loop you just disabled above, add a line setting the variable $IDsToKeep to this:
--> List( \\
$IDsToKeep ; \\
"TOName=" & $RelatedTOName; \\
"foo" \\
) \\
1. Add an "Exit Script" line at the beginning of the script "Delete Records Not In This List ( $IDsToKeep )" in GoZyncMobile.
2. Edit the script "Get IDS Needed For Sync PSOS" in your hosted file and disable the block of lines beginning with the first instance of the comment "gather IDS" (about line 48) and ending with "end loop" (about line 91).
3. The right after that end loop you just disabled above, add a line setting the variable $IDsToKeep to this:
--> List( \\
$IDsToKeep ; \\
"TOName=" & $RelatedTOName; \\
"foo" \\
) \\
Changed lines 3-7 from:
Records deleted on the hosted side are deleted from the mobile device the next time the mobile device pulls that table or executes a round-trip sync.
Records deletedon the mobile side are '''not''' passed to the host as deletion instructions. If you want to be able to delete records on mobile and have those records deleted from the host, tag the mobile record with a "deleted" flag instead. Then include the field in your zync layout and delete the record on the host using a server-side script.
(Having been deleted on the host / server, the record will then actually be deleted from the mobile device next time it pulls records.)
Records deleted
(Having been deleted on
to:
Records deleted in the hosted file are deleted from the mobile file the next time the mobile device pulls that table or executes a round-trip sync.
Records deleted in the mobile file are '''not''' automatically deleted from the hosted file when synced. If you want them to be, create a new flag field called "deleted" in both the mobile and hosted files. Add that field to your sync layouts in GoZyncMobile so it syncs. Then set up a server-side script that periodically finds and deleted those records marked "deleted" field = "1" in the hosted file. Once deleted in the hosted file, those records will be permanently deleted from the mobile file on the next sync.
Records deleted in the mobile file are '''not''' automatically deleted from the hosted file when synced. If you want them to be, create a new flag field called "deleted" in both the mobile and hosted files. Add that field to your sync layouts in GoZyncMobile so it syncs. Then set up a server-side script that periodically finds and deleted those records marked "deleted" field = "1" in the hosted file. Once deleted in the hosted file, those records will be permanently deleted from the mobile file on the next sync.
Changed line 25 from:
-> So on Tuesday morning I sync again and the [[downloading found sets | filter]] in GoZync pulls down just the people I'm assigned to see on Tuesday. Since Beth is on my list for Tuesday, she stays on my iPad and gets some new notes from the office. The other 5 people I saw on Monday no longer match my filter criteria (folks assigned to me for Monday) so they're deleted from my iPad and replaced with my Tuesday patients.
to:
-> So on Tuesday morning I sync again and the [[downloading found sets | filter]] in GoZync pulls down just the people I'm assigned to see on Tuesday. Since Beth is on my list for Tuesday, she stays on my iPad and gets some new notes from the office. The other 5 people I saw on Monday no longer match my filter criteria ("folks assigned to me for Monday") so they're deleted from my iPad and replaced with my Tuesday patients.
Changed lines 9-10 from:
!! Deleting records that don't (no longer) belong to me
to:
!! Deleting records that don't (no longer) belong to me (this is awesome)
Changed lines 15-19 from:
Well, next time that mobile user pulls down records, they'll also pull a list of all the orders they are supposed to have on the device: any records not on that list (because they were deleted from the host or because they are no longer "ready") will be deleted from the user's device. This makes it very easy to craft workflows where the user only has the records they need: you [[DownloadingFoundSets | build a found set of records]] appropriate for that user, and GoZync does the rest.
Now this means that you may want to prevent users from pulling down new records if they have [[unzynced records]] on their device, but you don't have to In the [[zync it | round trip]] syncs, for example, GoZync pushes changes before pulling them.
Here is an example of how deletes can really help with your workflow
Now this means that you may want to prevent users from pulling down new records if they have [[unzynced records]] on their device, but you don't have to
Here is an example of how deletes can really help with your workflow
to:
Well, next time that mobile user pulls down records, they'll also pull a list of all the orders they are supposed to have on the device: any records not on that list (because they were deleted from the host or because they are no longer "ready") will be deleted from the user's device. This makes it very easy to craft workflows where the user only has the records they need: you [[DownloadingFoundSets | build a found set of records]] appropriate for that user, and GoZync does the rest. (This is awesome.)
Here are some more examples of how deletes can really help with your workflow...
Here are some more examples of how deletes can really help with your workflow...
Changed line 5 from:
Records deleted on the mobile side are '''not''' passed to the host as deletion instructions. If you want to be able to delete records on mobile and have those records deleted from the host, tag the mobile record with a "deleted" flag instead. Then include the field in your Zync layout and delete the record on the host using a server-side script.
to:
Records deleted on the mobile side are '''not''' passed to the host as deletion instructions. If you want to be able to delete records on mobile and have those records deleted from the host, tag the mobile record with a "deleted" flag instead. Then include the field in your zync layout and delete the record on the host using a server-side script.
Changed lines 31-35 from:
-> GoZync handles all of this: deleting any records on your mobile device that no longer match your filter criteria.
to:
-> GoZync handles all of this: deleting any records on your mobile device that no longer match your filter criteria.
!! Turning Off Deletion
If you want to manage the deletion of mobile records yourself, you can turn off GoZync's management of it. Simply add an "Exit Script" line at the beginning of the script "Delete Records Not In This List ( $IDsToKeep )" in GoZyncMobile.
!! Turning Off Deletion
If you want to manage the deletion of mobile records yourself, you can turn off GoZync's management of it. Simply add an "Exit Script" line at the beginning of the script "Delete Records Not In This List ( $IDsToKeep )" in GoZyncMobile.
Changed line 5 from:
Records deleted on the mobile side are '''not''' passed to the host as deletion instructions. If you want to be able to delete records on mobile and have those records deleted from the host, tag the mobile record with a "deleted" flag instead. Then include the field in your Zync layout and delete the record on the host, either using a server side script.
to:
Records deleted on the mobile side are '''not''' passed to the host as deletion instructions. If you want to be able to delete records on mobile and have those records deleted from the host, tag the mobile record with a "deleted" flag instead. Then include the field in your Zync layout and delete the record on the host using a server-side script.
Added lines 18-31:
Here is an example of how deletes can really help with your workflow.
-> Let's say I'm a home health care aide and each morning I sync down to my iPad the half dozen or so patients I need to visit that day. So on Monday I get 6 patient records on my iPad.
-> If I have %newwin% [[http://www.seedcode.com/gomaps | GoMaps]] I know just where they are, but that's another story =)
-> At the end of the day I sync my visit notes back up to the hosted files. Now one of the patients I saw on Monday, Beth, called up to the office an needs something else, so the folks at the office assigned me to visit her again tomorrow.
-> So on Tuesday morning I sync again and the [[downloading found sets | filter]] in GoZync pulls down just the people I'm assigned to see on Tuesday. Since Beth is on my list for Tuesday, she stays on my iPad and gets some new notes from the office. The other 5 people I saw on Monday no longer match my filter criteria (folks assigned to me for Monday) so they're deleted from my iPad and replaced with my Tuesday patients.
-> And if another aide calls in sick and the office has to assign two of their patients to me as well, all I have to do is sync again and I have those two new patients as well. Both of which will be deleted from my iPad when they no longer match my day's assignment.
-> GoZync handles all of this: deleting any records on your mobile device that no longer match your filter criteria.
Changed lines 5-6 from:
Records deleted on the mobile side are not passed to the host as deletion instructions. If you want to be able to delete records on mobile and have those records deleted from the host, tag the mobile record with a "deleted" flag instead. Then include the field in your Zync layout and delete the record on the host, either using a server side script or our "After Committing Entity" script in GoZyncHosted.
to:
Records deleted on the mobile side are '''not''' passed to the host as deletion instructions. If you want to be able to delete records on mobile and have those records deleted from the host, tag the mobile record with a "deleted" flag instead. Then include the field in your Zync layout and delete the record on the host, either using a server side script.
Changed lines 13-14 from:
For example, let's say that you've scripted GoZync to [[DownloadingFoundSets | only pull down your orders]] that are marked "Ready". And that when you push those records back to the server, you're using our [[ Before Editing Entity]] script to mark the record "Completed."
to:
For example, let's say that you've scripted GoZync to [[DownloadingFoundSets | only pull down your orders]] that are marked "Ready". And that when you push those records back to the server, you're using our [[Custom Field Mapping]] script to mark the record "Completed."
Changed lines 17-21 from:
Now this means that you may want to prevent users from pulling down new records if they have [[unzynced records]] on their device, but you don't have to.
!! Turning this off
While this deletion behavior is often just what you want, for very large data sets it may be faster to take over the duties of deleting records yourself instead of having GoZync do it. If you have many thousands of records, this can make things ''much'' faster. Learn how to turn this off [[Turning Off Deletes | here]]
!! Turning this off
While this deletion behavior is often just what you want, for very large data sets it may be faster to take over the duties of deleting records yourself instead of having GoZync do it. If you have many thousands of records, this can make things ''much'' faster. Learn how to turn this off [[Turning Off Deletes | here]]
to:
Now this means that you may want to prevent users from pulling down new records if they have [[unzynced records]] on their device, but you don't have to. In the [[zync it | round trip]] syncs, for example, GoZync pushes changes before pulling them.
Changed lines 17-21 from:
Now this means that you may want to prevent users from pulling down new records if they have [[unzynced records]] on their device, but you don't have to.
to:
Now this means that you may want to prevent users from pulling down new records if they have [[unzynced records]] on their device, but you don't have to.
!! Turning this off
While this deletion behavior is often just what you want, for very large data sets it may be faster to take over the duties of deleting records yourself instead of having GoZync do it. If you have many thousands of records, this can make things ''much'' faster. Learn how to turn this off [[Turning Off Deletes | here]].
!! Turning this off
While this deletion behavior is often just what you want, for very large data sets it may be faster to take over the duties of deleting records yourself instead of having GoZync do it. If you have many thousands of records, this can make things ''much'' faster. Learn how to turn this off [[Turning Off Deletes | here]].
December 18, 2012, at 06:23 AM
by - minor edits and clarifications
Changed lines 3-6 from:
Records deleted on the hosted side are deleted from the mobile device the next time the mobile device pulls that table or executes a round trip sync.
Records deleted on the mobile side are not passed to the host as deletion instructions. If you want to be able to delete records on mobile and have those records deleted from the host, tag the mobile record with a "deleted" flag instead. Then include the field in yourzync layout and delete the record on the host, either using a server side script or our "After Committing Entity" script in GoZyncHosted.
Records deleted on the mobile side are not passed to the host as deletion instructions. If you want to be able to delete records on mobile and have those records deleted from the host, tag the mobile record with a "deleted" flag instead. Then include the field in your
to:
Records deleted on the hosted side are deleted from the mobile device the next time the mobile device pulls that table or executes a round-trip sync.
Records deleted on the mobile side are not passed to the host as deletion instructions. If you want to be able to delete records on mobile and have those records deleted from the host, tag the mobile record with a "deleted" flag instead. Then include the field in your Zync layout and delete the record on the host, either using a server side script or our "After Committing Entity" script in GoZyncHosted.
Records deleted on the mobile side are not passed to the host as deletion instructions. If you want to be able to delete records on mobile and have those records deleted from the host, tag the mobile record with a "deleted" flag instead. Then include the field in your Zync layout and delete the record on the host, either using a server side script or our "After Committing Entity" script in GoZyncHosted.
Changed lines 11-12 from:
A record doesn't actually have to be deleted from the host / server to be deleted from the users mobile device: the record would also be removed from the users device if it no longer "belongs" to that user.
to:
A record doesn't actually have to be deleted from the host / server to be deleted from the user's mobile device: the record would also be removed from the user's device if it no longer "belongs" to that user.
Changed lines 13-14 from:
For example, let's say that you've scripted GoZync to [[DownloadingFoundSets | only pull down your orders]] that are marked "Ready". And that when you push those records back to the server, you're using our [[ Before Committing Entity]] script to mark the record "Completed."
to:
For example, let's say that you've scripted GoZync to [[DownloadingFoundSets | only pull down your orders]] that are marked "Ready". And that when you push those records back to the server, you're using our [[ Before Editing Entity]] script to mark the record "Completed."
Changed lines 13-17 from:
For example, let's say that you've scripted GoZync to only your orders that are marked "Ready"
to:
For example, let's say that you've scripted GoZync to [[DownloadingFoundSets | only pull down your orders]] that are marked "Ready". And that when you push those records back to the server, you're using our [[ Before Committing Entity]] script to mark the record "Completed."
Well, next time that mobile user pulls down records, they'll also pull a list of all the orders they are supposed to have on the device: any records not on that list (because they were deleted from the host or because they are no longer "ready") will be deleted from the user's device. This makes it very easy to craft workflows where the user only has the records they need: you [[DownloadingFoundSets | build a found set of records]] appropriate for that user, and GoZync does the rest.
Now this means that you may want to prevent users from pulling down new records if they have [[unzynced records]] on their device, but you don't have to.
Well, next time that mobile user pulls down records, they'll also pull a list of all the orders they are supposed to have on the device: any records not on that list (because they were deleted from the host or because they are no longer "ready") will be deleted from the user's device. This makes it very easy to craft workflows where the user only has the records they need: you [[DownloadingFoundSets | build a found set of records]] appropriate for that user, and GoZync does the rest.
Now this means that you may want to prevent users from pulling down new records if they have [[unzynced records]] on their device, but you don't have to.
Changed lines 7-13 from:
(Having been deleted on the host / server, the record will then actually be deleted from the mobile device next time it pulls records.)
to:
(Having been deleted on the host / server, the record will then actually be deleted from the mobile device next time it pulls records.)
!! Deleting records that don't (no longer) belong to me
A record doesn't actually have to be deleted from the host / server to be deleted from the users mobile device: the record would also be removed from the users device if it no longer "belongs" to that user.
For example, let's say that you've scripted GoZync to only your orders that are marked "Ready"
!! Deleting records that don't (no longer) belong to me
A record doesn't actually have to be deleted from the host / server to be deleted from the users mobile device: the record would also be removed from the users device if it no longer "belongs" to that user.
For example, let's say that you've scripted GoZync to only your orders that are marked "Ready"
Changed lines 5-7 from:
Records deleted on the mobile side are not passed to the host as deletion instructions. If you want to be able to delete records on mobile and have those records deleted from the host, tag the mobile record with a "deleted" flag instead. Then include the field in your zync layout and delete the record on the host, either using a server side script or our "After Committing Entity" script in GoZyncHosted.
to:
Records deleted on the mobile side are not passed to the host as deletion instructions. If you want to be able to delete records on mobile and have those records deleted from the host, tag the mobile record with a "deleted" flag instead. Then include the field in your zync layout and delete the record on the host, either using a server side script or our "After Committing Entity" script in GoZyncHosted.
(Having been deleted on the host / server, the record will then actually be deleted from the mobile device next time it pulls records.)
(Having been deleted on the host / server, the record will then actually be deleted from the mobile device next time it pulls records.)
Changed line 5 from:
Records deleted on the mobile side are not passed to the host as deletion instructions. If you want to be able to delete records on mobile and have those records deleted from the host, tag the mobile record with a "deleted" flag instead. Then include the field in your zync layout and delete the record on the host, either using a server side script or our
to:
Records deleted on the mobile side are not passed to the host as deletion instructions. If you want to be able to delete records on mobile and have those records deleted from the host, tag the mobile record with a "deleted" flag instead. Then include the field in your zync layout and delete the record on the host, either using a server side script or our "After Committing Entity" script in GoZyncHosted.
Added lines 1-5:
!! How does GoZync handle deleted records?
Records deleted on the hosted side are deleted from the mobile device the next time the mobile device pulls that table or executes a round trip sync.
Records deleted on the mobile side are not passed to the host as deletion instructions. If you want to be able to delete records on mobile and have those records deleted from the host, tag the mobile record with a "deleted" flag instead. Then include the field in your zync layout and delete the record on the host, either using a server side script or our
Records deleted on the hosted side are deleted from the mobile device the next time the mobile device pulls that table or executes a round trip sync.
Records deleted on the mobile side are not passed to the host as deletion instructions. If you want to be able to delete records on mobile and have those records deleted from the host, tag the mobile record with a "deleted" flag instead. Then include the field in your zync layout and delete the record on the host, either using a server side script or our
