GoZync3

Turning Off Deletes

GoZync3.TurningOffDeletes History

Hide minor edits - Show changes to output

August 05, 2013, at 04:28 AM by 50.132.84.245 -
Added lines 1-2:
(:include NewerDocs:)
January 20, 2013, at 03:56 AM by 50.132.84.245 -
Changed lines 41-42 from:
Then add the line shown below, testing for the name of any ''related'' table occurrences you'd like to turn this off for:
to:
Then add the lines shown below, testing for the names of any ''related'' table occurrences for which you'd like to turn off deletes:
Changed line 47 from:
If you don't see a speed increase, double check that you have spelled the TOs name correctly, or take a look at the last zynced package in GoZyncMobile (after a successful sync) to see if any of the IDs from the table you're trying to turn off are in the package between the <ids></ids> tags.
to:
If you don't see a speed increase, double check that you have spelled the TOs name(s) correctly, or take a look at the last zynced package in then Zync Logs tab of GoZyncMobile (after a successful sync) to see if any of the IDs from the table(s) you're trying to turn off are in the package, between the <ids></ids> tags.
January 20, 2013, at 03:53 AM by 50.132.84.245 -
Changed lines 3-12 from:
GoZync will pass deletes down to the local file, deleting records from your iPhone / iPad that are no longer in the hosted file. These records are also deleted when records on the host no longer "belong to you" (i.e. no longer match your found set critter).

For details on this, read up
on [[deletes]].

Normally this is exactly how you want things to work. But, in very large tables the overhead of this can slow things down when you pull records down to your local file. GoZync will build a list of all the IDs that should be on your iPad ''every'' time you pull: whether records we changed or not.

So if your workflow is more static for some tables--you're not always pulling just "today's" orders, etc.--you may want to turn this behavior off and delete records from the iPad on your own.

This article shows you how to do that.
to:
GoZync will pass deletes down to the local file, deleting records from your iPhone / iPad that are no longer in the hosted file. These records are also deleted when records on the host no longer "belong to you" (i.e. no longer match your [[downloadingFoundSets | found set]] criteria).

For more background
on this, read up on [[deletes]].

Normally, this is exactly how you want things to work. But, in very large tables the overhead of managing deletes can slow things when you pull records down to your local file. GoZync will build a list of all the record IDs that should be on your iPad ''every'' time you pull: it does this if records were changed or not.

So, if your workflow is more static for some tables--you're not always pulling just "today's" orders, etc.--you may want to turn this behavior off and delete records from the iPad on your own.

This is an easy mod, and this article shows you how to do it.
Changed lines 19-22 from:
--> You're pulling just the appointments each of your service techs have each morning. GoZync's auto delete feature should be left on, since you want GoZync to delete those appointments no longer assigned to this technician and those that have been rescheduled for another day.

--> But you may want to turn this on for the 10k record price list table you're pulling. Items on the price list aren't deleted that often and you can set a deleted flag instead and then have a script in the iPad app the finds any records flagged for deletion and deletes them.
to:
--> You're pulling just the appointments each of your service techs have each morning. GoZync's auto delete feature should be left on for the appointments table, since you want GoZync to delete those appointments no longer assigned to this technician and those that have been rescheduled for another day.

--> But you may want to turn deletes off for the 10k record price list table you're also pulling. Items on the price list aren't deleted on the server that often, and you can set a deleted flag there instead and then have a script in the iPad app the finds any records flagged for deletion and deletes them. Much faster that doing deletes as part of the sync.
Changed lines 27-34 from:
--> Turning auto-deletes off will really speed up this pull because you can simply have a script on the iPad that finds records older than 3 months and deletes them. Better yet, since there is no penalty for finding zero records when searching on an indexed field, you can run this iPad's delete script every day.

!! Turning this off

All the changes you need to make are in the script "Get IDs for Found
Set..." in GoZyncHosted,

If you want to turn off deletes for the whole solution (every table you're syncing) then simply add an Exit Script () step as shown in the blue line below. (click on an image for a larger screen shot)
to:
--> Turning GoZync's deletes off will really speed up this pull because you can simply have a script on the iPad that finds records older than 3 months and deletes them. Better yet, since there is no penalty for finding no records when searching on an indexed field, you can run this iPad's delete script every day.

!! How to turn GoZync's deletes off

All the changes you need to make are in the script "Get IDs for Found
Set..." in GoZyncHosted.

If you want to turn off deletes for the whole solution (every table you're syncing) then simply add an Exit Script () step as shown in the blue line below and you're done. (click on the image below for a larger screen shot)
Changed lines 37-38 from:
If instead you'd like to turn this off per-table, you need to make two changes. The first involved adding the Exit Loop If () line shown in blue below. Test for the variable $TO equaling the Table Occurrence name you'd like to turn this off for. This is the name of the TO you created in GoZyncHosted to represent the TO in your hosted fie.
to:
If instead you'd like to turn this off per-table, you need to make two changes. The first involves adding the Exit Loop If () line shown in blue below. Test for the variable $TO equaling the Table Occurrence name you'd like to turn this off for. This is the name of the TO you created in GoZyncHosted to represent the TO in your hosted fie.
January 20, 2013, at 03:40 AM by 50.132.84.245 -
Changed lines 39-47 from:
%width=500 newwin% [[http://www.seedcode.com/rootimages/stikipad/gozync/idmod2.png | http://www.seedcode.com/rootimages/stikipad/gozync/idmod2.png]]
to:
%width=500 newwin% [[http://www.seedcode.com/rootimages/stikipad/gozync/idmod2.png | http://www.seedcode.com/rootimages/stikipad/gozync/idmod2.png]]

Then add the line shown below, testing for the name of any ''related'' table occurrences you'd like to turn this off for:

%width=500 newwin% [[http://www.seedcode.com/rootimages/stikipad/gozync/idmod3.png | http://www.seedcode.com/rootimages/stikipad/gozync/idmod3.png]]

That's it.

If you don't see a speed increase, double check that you have spelled the TOs name correctly, or take a look at the last zynced package in GoZyncMobile (after a successful sync) to see if any of the IDs from the table you're trying to turn off are in the package between the <ids></ids> tags.
January 20, 2013, at 03:35 AM by 50.132.84.245 -
Changed lines 33-34 from:
If you want to turn off deletes for the whole solution (every table you're syncing) then simply add an Exit Script () step as shown in the blue line below.
to:
If you want to turn off deletes for the whole solution (every table you're syncing) then simply add an Exit Script () step as shown in the blue line below. (click on an image for a larger screen shot)
Changed lines 37-38 from:
If instead you'd like to turn this off per-table, you need to make two changes. The first
to:
If instead you'd like to turn this off per-table, you need to make two changes. The first involved adding the Exit Loop If () line shown in blue below. Test for the variable $TO equaling the Table Occurrence name you'd like to turn this off for. This is the name of the TO you created in GoZyncHosted to represent the TO in your hosted fie.
January 20, 2013, at 03:34 AM by 50.132.84.245 -
Changed lines 31-32 from:
All the changes you need to make are in the script
to:
All the changes you need to make are in the script "Get IDs for Found Set..." in GoZyncHosted,

If you want to turn off deletes for the whole solution (every table you're syncing) then simply add an Exit Script () step as shown in the blue line below.

Added lines 36-39:

If instead you'd like to turn this off per-table, you need to make two changes. The first

%width=500 newwin% [[http://www.seedcode.com/rootimages/stikipad/gozync/idmod2.png | http://www.seedcode.com/rootimages/stikipad/gozync/idmod2.png]]
January 20, 2013, at 03:32 AM by 50.132.84.245 -
Added line 33:
%width=500 newwin% [[http://www.seedcode.com/rootimages/stikipad/gozync/idmod1.png | http://www.seedcode.com/rootimages/stikipad/gozync/idmod1.png]]
January 20, 2013, at 03:30 AM by 50.132.84.245 -
Added lines 7-28:
Normally this is exactly how you want things to work. But, in very large tables the overhead of this can slow things down when you pull records down to your local file. GoZync will build a list of all the IDs that should be on your iPad ''every'' time you pull: whether records we changed or not.

So if your workflow is more static for some tables--you're not always pulling just "today's" orders, etc.--you may want to turn this behavior off and delete records from the iPad on your own.

This article shows you how to do that.

!! Scenarios

Here are some examples of when you may want to turn this off. And remember, you can turn this off file-wide, or just for individual tables.

-> '''Example: My Appointments for Today'''

--> You're pulling just the appointments each of your service techs have each morning. GoZync's auto delete feature should be left on, since you want GoZync to delete those appointments no longer assigned to this technician and those that have been rescheduled for another day.

--> But you may want to turn this on for the 10k record price list table you're pulling. Items on the price list aren't deleted that often and you can set a deleted flag instead and then have a script in the iPad app the finds any records flagged for deletion and deletes them.

-> '''Example: Pricing History for Customers'''

--> You're pulling the 3 month pricing history for each customer. There are tens of thousands of records and you only want to keep records from the last 3 months on the iPad.

--> Turning auto-deletes off will really speed up this pull because you can simply have a script on the iPad that finds records older than 3 months and deletes them. Better yet, since there is no penalty for finding zero records when searching on an indexed field, you can run this iPad's delete script every day.

Changed lines 31-32 from:
xcvasfva
to:
All the changes you need to make are in the script
January 20, 2013, at 03:18 AM by 50.132.84.245 -
Changed lines 3-4 from:
sdvasd
to:
GoZync will pass deletes down to the local file, deleting records from your iPhone / iPad that are no longer in the hosted file. These records are also deleted when records on the host no longer "belong to you" (i.e. no longer match your found set critter).

For details on this, read up on [[deletes]].

January 20, 2013, at 03:15 AM by 50.132.84.245 -
Added lines 1-7:
!! Overview

sdvasd

!! Turning this off

xcvasfva
(855) SEEDCODE
support@seedcode.com
Follow us: