Custom Field Mapping
GoZync3.FieldMapping History
Hide minor edits - Show changes to output
December 18, 2012, at 10:13 AM
by - minor edits and clarifications
Changed lines 7-8 from:
If the field and table names in your mobile and hosted files match, GoZync will move the data between them automatically. And if the field names are the same, but your table occurrence names are different, you identify that during the integration when you select your table occurrence names in GoZyncHosted. So the only time you need to get into custom mappings is when the field names in your mobile file and those in your hosted file differ.
to:
If the field and table names in your mobile and hosted files match, GoZync will move the data between them automatically. If the field names are the same, but your table occurrence names are different, you identify that during the integration when you select your table occurrence names in GoZyncHosted. So the only time you need to get into custom mappings is when the field names in your mobile file and those in your hosted file differ.
December 10, 2012, at 10:24 PM
by - minor edits
Changed lines 7-8 from:
If the field and table names in your mobile and hosted files match, GoZync will move the data between them automatically. And if the field names are the same, but your table occurrence names are different, you identify that during the integration when you select your table occurrence names in GoZyncHosted. So the only time you need to get into custom mappings is when the field names in your mobile file and those in your hosted file differ.
to:
If the field and table names in your mobile and hosted files match, GoZync will move the data between them automatically. And if the field names are the same, but your table occurrence names are different, you identify that during the integration when you select your table occurrence names in GoZyncHosted. So the only time you need to get into custom mappings is when the field names in your mobile file and those in your hosted file differ.
Changed lines 11-12 from:
From the dashboard, select the layout you're interested in and click "Integration & Options", then proceed to the integration. You'll need all your files open: GoZyncHosted, GoZyncMobile, your mobile file and your hosted solution.
to:
From the dashboard, select the layout you're interested in and click "Integration & Options", then proceed to integration. You'll need all your files open: GoZyncHosted, GoZyncMobile, your mobile file and your hosted solution.
Changed lines 19-20 from:
GoZync syncs repeating fields without issue, but if your names differ, you'll need to create a custom field mapping for each repetition of the field. As shown here for "date" and "orderdate"
to:
GoZync syncs repeating fields without issue, but if your names differ, you'll need to create a custom field mapping for each repetition of the field. As shown here for "date" and "orderdate":
Changed lines 23-24 from:
You'll also want to make sure that all the repetitions you wish to sync are on the layout used for zyncing. For example, if you show repetitions 1 and 3, those are the only ones that will be zynced.
to:
You'll also want to make sure that all the repetitions you wish to sync are on the layout used for Zyncing. For example, if you show repetitions 1 and 3, those are the only ones that will be Zynced.
Changed line 28 from:
Learn more here: [[Processing Errors]]
to:
Learn more: [[Processing Errors]]
Changed lines 26-85 from:
!! The most common errors
Here is what the Inbox tab of GoZyncHosted might look like if you have processing errors. That is, errors pushing changes you've received from your mobile file into the hosted tables:
%center% http://www.seedcode.com/rootimages/stikipad/gozync/processingerrors.png
On the mobile side we don't have an inbox (since there is just one user per device) so errors show up in the Zync Log tab of GoZyncMobile (note the 102 error in the third line from the bottom):
%center% http://www.seedcode.com/rootimages/stikipad/gozync/perrorsmobile.png
The following notes should help you resolve any of these set field errors.
If you have records in your inbox that aren't processing, export the raw error log to see what the issue is (I like to check "Automatically open file" when exporting). Many of the errors will be self explanatory, but the guide below may help.
-> '''101 Record is missing.''' This is about the table occurrence, not the field.
--> Most likely reason for this is that you don't have "Allow creation of records..." set to "on" for this table in its relationship with GoZync in the graph of either GoZyncHosted or GoZyncMobile (whichever file you're seeing the error it).
--> Turn "Allow creation..." on for the table occurrence mentioned in the error and then try again.
-> '''102 Field Missing.''' There are only a few reasons why you'd see a 102 error.
--> You've sent a field that doesn't exist in the destination. Remove the field from the sync layout on the source side (the sending side) or add it to the receiving side.
--> The field exists but has a different name in the destination. See "Custom Field Mapping" above to transform the field name.
--> You've create a transformation (a custom field mapping) but your field is repeating and you haven't created a field mapping for each repetition.
-> '''106 Table is Missing'''
--> There is a mismatch between the table occurrence names found in the package being processed and the TO names connected to GoZync in your destination file (in GoZyncHosted or GoZyncMobile).
--> You may have related fields in your package but don't have their TO connected to GoZync in your destination file.
--> Or you simply don't have the right name either for the TO on the graph itself, OR in the integration setup in GoZyncHosted: you may have selected the wrong table occurrence or changed the TO name since the integration was done.
-> '''301 Record is in use by another user.''' Commonly called "record lock".
--> This is exactly what it sound like.
--> FileMaker couldn't edit the record (or one of the related records for that inbox entry) because another user was editing it. Feel free to reprocess the record later when the original user has left it.
-> '''500-511 Validation Errors.'''
--> These will occur when the data coming in fails to meet the validation criteria set up one one of your fields.
--> Hover over the error and our tool tip will tell you the field which created the error and what kind of validation was offended.
--> You can turn off the validation or change it from "always" to "only during data entry" which will stop it from firing during scripted set fields like those used in GoZync.
!! Re-Processing
In GoZyncHosted, simply select any inbox items you'd like to reprocess and the hold down the shift key while clicking "Process Selected Items". You can even do this with inbox items that haven't had errors. Re-processing is a great way to test your custom field mapping without having to be constantly zyncing.
On the mobile side you can't re-process so you'll need to zync again. If your sync is only bringing down changed records, you may need to [[clear the last zync time]] for that device to ensure you get your records again.
Note that since you can't get 301 errors on mobile, the only errors you should ever have on the mobile side should be during testing, unless you change field names in the hosted side would doing custom field mappings.
to:
!! Seeing Errors?
Learn more here: [[Processing Errors]]
Learn more here: [[Processing Errors]]
Changed lines 9-10 from:
to:
!! Creating a field mapping.
From the dashboard, select the layout you're interested in and click "Integration & Options", then proceed to the integration. You'll need all your files open: GoZyncHosted, GoZyncMobile, your mobile file and your hosted solution.
(Visit the downloads tab of GoZyncHosted to [[Distributing Mobile Files | pull down copies]] of the mobile files, providing they are up to date.)
Now click the "Field Mapping (optional)" tab and you'll see the table occurrences represented on your layout to the left. Select each one and create field mapping for any fields whose names don't match.
From the dashboard, select the layout you're interested in and click "Integration & Options", then proceed to the integration. You'll need all your files open: GoZyncHosted, GoZyncMobile, your mobile file and your hosted solution.
(Visit the downloads tab of GoZyncHosted to [[Distributing Mobile Files | pull down copies]] of the mobile files, providing they are up to date.)
Now click the "Field Mapping (optional)" tab and you'll see the table occurrences represented on your layout to the left. Select each one and create field mapping for any fields whose names don't match.
Deleted lines 39-40:
Added lines 50-57:
-> '''106 Table is Missing'''
--> There is a mismatch between the table occurrence names found in the package being processed and the TO names connected to GoZync in your destination file (in GoZyncHosted or GoZyncMobile).
--> You may have related fields in your package but don't have their TO connected to GoZync in your destination file.
--> Or you simply don't have the right name either for the TO on the graph itself, OR in the integration setup in GoZyncHosted: you may have selected the wrong table occurrence or changed the TO name since the integration was done.
--> There is a mismatch between the table occurrence names found in the package being processed and the TO names connected to GoZync in your destination file (in GoZyncHosted or GoZyncMobile).
--> You may have related fields in your package but don't have their TO connected to GoZync in your destination file.
--> Or you simply don't have the right name either for the TO on the graph itself, OR in the integration setup in GoZyncHosted: you may have selected the wrong table occurrence or changed the TO name since the integration was done.
Added lines 40-41:
--> Another possibility is that you have related fields in your package but don't have their TO connected to GoZync in your destination file (in GoZyncHosted or GoZyncMobile).
Changed lines 22-23 from:
!! Common problems
to:
!! The most common errors
Added lines 36-41:
-> '''101 Record is missing.''' This is about the table occurrence, not the field.
--> Most likely reason for this is that you don't have "Allow creation of records..." set to "on" for this table in its relationship with GoZync in the graph of either GoZyncHosted or GoZyncMobile (whichever file you're seeing the error it).
--> Turn "Allow creation..." on for the table occurrence mentioned in the error and then try again.
--> Most likely reason for this is that you don't have "Allow creation of records..." set to "on" for this table in its relationship with GoZync in the graph of either GoZyncHosted or GoZyncMobile (whichever file you're seeing the error it).
--> Turn "Allow creation..." on for the table occurrence mentioned in the error and then try again.
Changed lines 50-51 from:
-> '''301 Record is in use by another user.''' Commonly called "record lock", this is exactly what it sound like.
to:
-> '''301 Record is in use by another user.''' Commonly called "record lock".
--> This is exactly what it sound like.
--> This is exactly what it sound like.
Changed lines 56-57 from:
-> '''500-511 Validation Errors.''' These will occur when the data coming in fails to meet the validation criteria set up one one of your fields.
to:
-> '''500-511 Validation Errors.'''
--> These will occur when the data coming in fails to meet the validation criteria set up one one of your fields.
--> These will occur when the data coming in fails to meet the validation criteria set up one one of your fields.
Added line 64:
Changed lines 44-47 from:
> > record lock
> > validation
> >
to:
-> '''301 Record is in use by another user.''' Commonly called "record lock", this is exactly what it sound like.
--> FileMaker couldn't edit the record (or one of the related records for that inbox entry) because another user was editing it. Feel free to reprocess the record later when the original user has left it.
-> '''500-511 Validation Errors.''' These will occur when the data coming in fails to meet the validation criteria set up one one of your fields.
--> Hover over the error and our tool tip will tell you the field which created the error and what kind of validation was offended.
--> You can turn off the validation or change it from "always" to "only during data entry" which will stop it from firing during scripted set fields like those used in GoZync.
--> FileMaker couldn't edit the record (or one of the related records for that inbox entry) because another user was editing it. Feel free to reprocess the record later when the original user has left it.
-> '''500-511 Validation Errors.''' These will occur when the data coming in fails to meet the validation criteria set up one one of your fields.
--> Hover over the error and our tool tip will tell you the field which created the error and what kind of validation was offended.
--> You can turn off the validation or change it from "always" to "only during data entry" which will stop it from firing during scripted set fields like those used in GoZync.
Changed lines 46-54 from:
> > validation
to:
> > validation
!! Re-Processing
In GoZyncHosted, simply select any inbox items you'd like to reprocess and the hold down the shift key while clicking "Process Selected Items". You can even do this with inbox items that haven't had errors. Re-processing is a great way to test your custom field mapping without having to be constantly zyncing.
On the mobile side you can't re-process so you'll need to zync again. If your sync is only bringing down changed records, you may need to [[clear the last zync time]] for that device to ensure you get your records again.
Note that since you can't get 301 errors on mobile, the only errors you should ever have on the mobile side should be during testing, unless you change field names in the hosted side would doing custom field mappings.
!! Re-Processing
In GoZyncHosted, simply select any inbox items you'd like to reprocess and the hold down the shift key while clicking "Process Selected Items". You can even do this with inbox items that haven't had errors. Re-processing is a great way to test your custom field mapping without having to be constantly zyncing.
On the mobile side you can't re-process so you'll need to zync again. If your sync is only bringing down changed records, you may need to [[clear the last zync time]] for that device to ensure you get your records again.
Note that since you can't get 301 errors on mobile, the only errors you should ever have on the mobile side should be during testing, unless you change field names in the hosted side would doing custom field mappings.
Changed lines 24-25 from:
Here is what the Inbox tab of GoZyncHosted might look like if you have processing errors:
to:
Here is what the Inbox tab of GoZyncHosted might look like if you have processing errors. That is, errors pushing changes you've received from your mobile file into the hosted tables:
Changed lines 28-33 from:
to:
On the mobile side we don't have an inbox (since there is just one user per device) so errors show up in the Zync Log tab of GoZyncMobile (note the 102 error in the third line from the bottom):
%center% http://www.seedcode.com/rootimages/stikipad/gozync/perrorsmobile.png
The following notes should help you resolve any of these set field errors.
%center% http://www.seedcode.com/rootimages/stikipad/gozync/perrorsmobile.png
The following notes should help you resolve any of these set field errors.
Changed lines 5-6 from:
''Note. Custom field mapping is not available in LowZync, the free version of GoZync.
to:
''Note. Custom field mapping is not available in LowZync, the free version of GoZync.''
Added lines 5-6:
''Note. Custom field mapping is not available in LowZync, the free version of GoZync.
''
''
Changed lines 18-19 from:
! Troubleshooting Your Mapping
to:
! Processing Errors
Added lines 15-16:
You'll also want to make sure that all the repetitions you wish to sync are on the layout used for zyncing. For example, if you show repetitions 1 and 3, those are the only ones that will be zynced.
Added lines 20-24:
Here is what the Inbox tab of GoZyncHosted might look like if you have processing errors:
%center% http://www.seedcode.com/rootimages/stikipad/gozync/processingerrors.png
%center% http://www.seedcode.com/rootimages/stikipad/gozync/processingerrors.png
Changed lines 22-24 from:
-> '''102 Field Missing.''' This is most likely because one or more of your table occurrences in the Packing and UnPacking section of the relationship graph in Connector do not have "Allow creation of records in this table..." checked. This needs to be "on" for each tale on your file's side of the relationship.
-> You may have situations where an inbox record is posted to your file correctly, but you see an error anyway. Thislikely because one of the fields you've mapped to in one of your "Set XXXX Fields" is a calc. Our script only traps the first set field statement to make sure the record is editable, subsequent set field statements aren't error trapped so they aren't invisible, Failing loudly should help you debug them.
-> You may have situations where an inbox record is posted to your file correctly, but you see an error anyway. This
to:
-> '''102 Field Missing.''' There are only a few reasons why you'd see a 102 error.
--> You've sent a field that doesn't exist in the destination. Remove the field from the sync layout on the source side (the sending side) or add it to the receiving side.
--> The field exists but has a different name in the destination. See "Custom Field Mapping" above to transform the field name.
--> You've create a transformation (a custom field mapping) but your field is repeating and you haven't created a field mapping for each repetition.
> > record lock
> > validation
--> You've sent a field that doesn't exist in the destination. Remove the field from the sync layout on the source side (the sending side) or add it to the receiving side.
--> The field exists but has a different name in the destination. See "Custom Field Mapping" above to transform the field name.
--> You've create a transformation (a custom field mapping) but your field is repeating and you haven't created a field mapping for each repetition.
> > record lock
> > validation
Changed lines 20-23 from:
If you have records in your inbox that aren't processing
-> Record is Missing.
-> Record is Missing.
to:
If you have records in your inbox that aren't processing, export the raw error log to see what the issue is (I like to check "Automatically open file" when exporting). Many of the errors will be self explanatory, but the guide below may help.
-> '''102 Field Missing.''' This is most likely because one or more of your table occurrences in the Packing and UnPacking section of the relationship graph in Connector do not have "Allow creation of records in this table..." checked. This needs to be "on" for each tale on your file's side of the relationship.
-> '''102 Field Missing.''' This is most likely because one or more of your table occurrences in the Packing and UnPacking section of the relationship graph in Connector do not have "Allow creation of records in this table..." checked. This needs to be "on" for each tale on your file's side of the relationship.
Changed lines 15-16 from:
[[#Troubleshooting]] ! Troubleshooting Your Mapping
to:
[[#Troubleshooting]]
! Troubleshooting Your Mapping
! Troubleshooting Your Mapping
Changed lines 15-16 from:
[[#Troubleshooting]]! Troubleshooting Your Mapping
to:
[[#Troubleshooting]] ! Troubleshooting Your Mapping
Changed lines 15-16 from:
[[#Troubleshooting]] ! Troubleshooting Your Mapping
to:
[[#Troubleshooting]]! Troubleshooting Your Mapping
Changed lines 15-16 from:
! Troubleshooting Your Mapping
to:
[[#Troubleshooting]] ! Troubleshooting Your Mapping
Changed lines 19-20 from:
to:
If you have records in your inbox that aren't processing
Changed lines 1-2 from:
(:title Tips for Field Mapping Scripts:)
to:
(:title Custom Field Mapping:)
Changed lines 5-85 from:
We call these "Set XXXX Fields" scripts because you may have scripts called "Set Invoice Fields", "Set Customer Fields", etc.
The data you have to work with has, by this point, been unpacked into one $variable for every field name in your source table. Well not "every" field name, of course, just those included on the tabs of your source's Field Mapping layout. (If you're sending data up to your server form mobile, your source table is the table and field names in your mobile file.)
!! Watch a Video
Here is a short video showing how you can add a field to an existing mapping. Watch this after reading through this article and you'll see all the elements here in action: the field mapping layout, the data dictionary, and the Set Field script steps. %newwin% [[http://www.youtube.com/watch?v=3qIpHXeT_dU | Adding a field to a zynced file]].
!! Set Fields
So if your mobile file has a field named "thing" on its Field Mapping layout, you'll have a variable named $thing as GoZync's scripts unpack the document in GoZyncConnector. Your job is now to make sure $thing gets sent to the right field in your solution.
You could do it like this:
-> @@Set Field [ MyTable::FirstName; $thing]@@
But GoZync actually does it like this...
-> @@Set Field [ MyTable::FirstName; zyncvariable ( "thing" ) ]@@
...so that we can trap for errors like misspelling "thing". That is why each SetField() statement in these scripts is followed by the same Perform Script line calling our Error Log script.
Thus, for every field you want to get from your mobile file, you'll have a "SetField / Perform Script Error Log:" pair of lines in your Set XXX Fields scripts in GoZyncConnector. (There are similar scripts in your mobile file to set the fields you get down from connector when pulling data into your mobile file.)
! Using a Dictionary
(:include TheDataDictionary:)
! Tips & Tricks
!! "Transforming" Data
Remember that you don't have to simply send the $variable data from the mobile file into your database as is: you can perform calculations and transformation on the data in your "Set XXX Field" scripts. Here is a simple example..,
-> Let's say your local field has two fields for a contact's name, NameFirst and NameLast, but your served database has only one: FullName. You could set FullName to this: $NameFirst & " " & $NameLast.
Transformations like these are one of the real strengths of GoZync in that they allow you to build mobile files that have a completely different structure from your served files. "Splitting Tables", below, is another popular transformation.
(:include SplittingRecords:)
!! Handling Related Records
> > Notes about saving the IDs of newly created parent records so you can make their children
!! Forcing Lookups
There may be times when lookup data doesn't fill in when you process records. This can happen when you're [[splitting records]] and the record (a customer, for example) hasn't been committed as FileMaker tries to lookup their information in a related record like an invoice.
This is a side effect of making ''all'' of GoZync transactional and you may want to back off this a bit, especially when it is the FileMaker-to-FileMaker communication of processing records in the InBox. "Backing off" in this case means adding a commit records script step to make sure you commit a record (like a customer) before using their information in a lookup.
To do this in any "Set XXXX Field" script, add the commit records script step right before the comment "Cleaning Up". In our customer-and-invoices example, where the customer data might not be getting looked up into the invoice, you'd add this in the "Set Customer Fields" script to commit the customer record.
!! Working with Photos
> > In serialize,
Am I a container field
If it is a container
In the text, we put <attachment> attachment number </attachment>\
We then put these into the same repetition in inbox.
Repeating field has the container.
When unpacking
If there is <attachment> attachment number </attachment> in our document content we grab that rep from the repeytion in in box.
So as I'm building a mapping layout I do[n't need to worry about images.
It may be that what I did by hand is something we need to bring into unpack.
!! More
Coming Soon.
to:
If the field and table names in your mobile and hosted files match, GoZync will move the data between them automatically. And if the field names are the same, but your table occurrence names are different, you identify that during the integration when you select your table occurrence names in GoZyncHosted. So the only time you need to get into custom mappings is when the field names in your mobile file and those in your hosted file differ.
> > general description
!! Repeating Fields
GoZync syncs repeating fields without issue, but if your names differ, you'll need to create a custom field mapping for each repetition of the field. As shown here for "date" and "orderdate"
%width=500 newwin% [[http://www.seedcode.com/rootimages/stikipad/gozync/mappedrepeats.png | http://www.seedcode.com/rootimages/stikipad/gozync/mappedrepeats.png]]
> > general description
!! Repeating Fields
GoZync syncs repeating fields without issue, but if your names differ, you'll need to create a custom field mapping for each repetition of the field. As shown here for "date" and "orderdate"
%width=500 newwin% [[http://www.seedcode.com/rootimages/stikipad/gozync/mappedrepeats.png | http://www.seedcode.com/rootimages/stikipad/gozync/mappedrepeats.png]]
Added lines 11-14:
!! Video
Here is a short video showing how you can add a field to an existing mapping. Watch this after reading through this article and you'll see all the elements here in action: the field mapping layout, the data dictionary, and the Set Field script steps. %newwin% [[http://www.youtube.com/watch?v=3qIpHXeT_dU | Adding a field to a zynced file]].
Here is a short video showing how you can add a field to an existing mapping. Watch this after reading through this article and you'll see all the elements here in action: the field mapping layout, the data dictionary, and the Set Field script steps. %newwin% [[http://www.youtube.com/watch?v=3qIpHXeT_dU | Adding a field to a zynced file]].
Added lines 7-8:
We call these "Set XXXX Fields" scripts because you may have scripts called "Set Invoice Fields", "Set Customer Fields", etc.
Changed lines 17-18 from:
> > Set Field [ MyTable::FirstName; $thing]
to:
-> @@Set Field [ MyTable::FirstName; $thing]@@
Changed lines 21-22 from:
> > Set Field [ MyTable::FirstName; zyncvariable ( "thing" ) ]
to:
-> @@Set Field [ MyTable::FirstName; zyncvariable ( "thing" ) ]@@
Added lines 9-24:
!! Set Fields
So if your mobile file has a field named "thing" on its Field Mapping layout, you'll have a variable named $thing as GoZync's scripts unpack the document in GoZyncConnector. Your job is now to make sure $thing gets sent to the right field in your solution.
You could do it like this:
> > Set Field [ MyTable::FirstName; $thing]
But GoZync actually does it like this...
> > Set Field [ MyTable::FirstName; zyncvariable ( "thing" ) ]
...so that we can trap for errors like misspelling "thing". That is why each SetField() statement in these scripts is followed by the same Perform Script line calling our Error Log script.
Thus, for every field you want to get from your mobile file, you'll have a "SetField / Perform Script Error Log:" pair of lines in your Set XXX Fields scripts in GoZyncConnector. (There are similar scripts in your mobile file to set the fields you get down from connector when pulling data into your mobile file.)
So if your mobile file has a field named "thing" on its Field Mapping layout, you'll have a variable named $thing as GoZync's scripts unpack the document in GoZyncConnector. Your job is now to make sure $thing gets sent to the right field in your solution.
You could do it like this:
> > Set Field [ MyTable::FirstName; $thing]
But GoZync actually does it like this...
> > Set Field [ MyTable::FirstName; zyncvariable ( "thing" ) ]
...so that we can trap for errors like misspelling "thing". That is why each SetField() statement in these scripts is followed by the same Perform Script line calling our Error Log script.
Thus, for every field you want to get from your mobile file, you'll have a "SetField / Perform Script Error Log:" pair of lines in your Set XXX Fields scripts in GoZyncConnector. (There are similar scripts in your mobile file to set the fields you get down from connector when pulling data into your mobile file.)
Changed lines 1-2 from:
(:title Tips for Field Mapping:)
to:
(:title Tips for Field Mapping Scripts:)
Added lines 29-37:
!! Forcing Lookups
There may be times when lookup data doesn't fill in when you process records. This can happen when you're [[splitting records]] and the record (a customer, for example) hasn't been committed as FileMaker tries to lookup their information in a related record like an invoice.
This is a side effect of making ''all'' of GoZync transactional and you may want to back off this a bit, especially when it is the FileMaker-to-FileMaker communication of processing records in the InBox. "Backing off" in this case means adding a commit records script step to make sure you commit a record (like a customer) before using their information in a lookup.
To do this in any "Set XXXX Field" script, add the commit records script step right before the comment "Cleaning Up". In our customer-and-invoices example, where the customer data might not be getting looked up into the invoice, you'd add this in the "Set Customer Fields" script to commit the customer record.
There may be times when lookup data doesn't fill in when you process records. This can happen when you're [[splitting records]] and the record (a customer, for example) hasn't been committed as FileMaker tries to lookup their information in a related record like an invoice.
This is a side effect of making ''all'' of GoZync transactional and you may want to back off this a bit, especially when it is the FileMaker-to-FileMaker communication of processing records in the InBox. "Backing off" in this case means adding a commit records script step to make sure you commit a record (like a customer) before using their information in a lookup.
To do this in any "Set XXXX Field" script, add the commit records script step right before the comment "Cleaning Up". In our customer-and-invoices example, where the customer data might not be getting looked up into the invoice, you'd add this in the "Set Customer Fields" script to commit the customer record.
Changed lines 23-30 from:
You have a a very simple mobile file with only one or two tables (something a database designer would call a fairly "flat" file
For an example of how this works, check out the "Set Invoice Fields" script in a clean copy of GoZyncConnector. The scenario here is that our mobile file keeps the invoiced contact and their address IN the invoice table, while our sample served solution (Invoices.fp7) has a separate customer table. So you'll find a piece of GoZyncConnector's "Set Invoice Fields" script where we leave the invoice, create a customer record, and return to use the newly created customer ID in our invoice. This happens between the comment "Splitting Tables..." and "...End Splitting Tables".
Notice that we can create additional "Set XXXX Fields" scripts, for entities that don't exist in our mobile file: the Data Dictionary form our mobile file didn't mention a customers table, because the mobile file didn't have one, but we can still create a "Set Customer Fields" script in GoZyncConnector and split the invoice data into an invoice record and a related customer record.
to:
(:include SplittingRecords:)
Changed lines 37-38 from:
> > Ask todd
to:
> > In serialize,
Am I a container field
If it is a container
In the text, we put <attachment> attachment number </attachment>\
We then put these into the same repetition in inbox.
Repeating field has the container.
When unpacking
If there is <attachment> attachment number </attachment> in our document content we grab that rep from the repeytion in in box.
So as I'm building a mapping layout I do[n't need to worry about images.
It may be that what I did by hand is something we need to bring into unpack.
Am I a container field
If it is a container
In the text, we put <attachment> attachment number </attachment>\
We then put these into the same repetition in inbox.
Repeating field has the container.
When unpacking
If there is <attachment> attachment number </attachment> in our document content we grab that rep from the repeytion in in box.
So as I'm building a mapping layout I do[n't need to worry about images.
It may be that what I did by hand is something we need to bring into unpack.
Added lines 5-8:
When you're editing the "Set XXXX Fields" scripts in GoZyncConnector or in your mobile file, you're mapping the data sent in a [[TheDocument | document]] to the real fields in your table.
The data you have to work with has, by this point, been unpacked into one $variable for every field name in your source table. Well not "every" field name, of course, just those included on the tabs of your source's Field Mapping layout. (If you're sending data up to your server form mobile, your source table is the table and field names in your mobile file.)
The data you have to work with has, by this point, been unpacked into one $variable for every field name in your source table. Well not "every" field name, of course, just those included on the tabs of your source's Field Mapping layout. (If you're sending data up to your server form mobile, your source table is the table and field names in your mobile file.)
Changed lines 7-8 from:
to:
(:include TheDataDictionary:)
Changed line 43 from:
-> Good post but error anyway: set a calc etc.
to:
-> You may have situations where an inbox record is posted to your file correctly, but you see an error anyway. This is likely because one of the fields you've mapped to in one of your "Set XXXX Fields" is a calc. Our script only traps the first set field statement to make sure the record is editable, subsequent set field statements aren't error trapped so they aren't invisible, Failing loudly should help you debug them.
Changed lines 25-26 from:
Notice that we can create additional "Set XXXX Fields" scripts, for entities that don't exist in our mobile file: the [[Data
to:
Notice that we can create additional "Set XXXX Fields" scripts, for entities that don't exist in our mobile file: the Data Dictionary form our mobile file didn't mention a customers table, because the mobile file didn't have one, but we can still create a "Set Customer Fields" script in GoZyncConnector and split the invoice data into an invoice record and a related customer record.
Changed lines 41-43 from:
--> Record is Missing. This is most likely because one or more of your table occurrences in the Packing and UnPacking section of the relationship graph in Connector do not have "Allow creation of records in this table..." checked. This needs to be "on" for each tale on your file's side of the relationship.
--> Good post but error anyway: set a calc etc.
to:
-> Record is Missing. This is most likely because one or more of your table occurrences in the Packing and UnPacking section of the relationship graph in Connector do not have "Allow creation of records in this table..." checked. This needs to be "on" for each tale on your file's side of the relationship.
-> Good post but error anyway: set a calc etc.
-> Good post but error anyway: set a calc etc.
Changed lines 21-26 from:
to:
You have a a very simple mobile file with only one or two tables (something a database designer would call a fairly "flat" file), while your served solution may us many tables to represent the same data (it may be more "relational"). Go Zync provides a method for splitting the data from one table into many tables. Though this is most often done on the served side, you can split tables coming down onto the device as well.
For an example of how this works, check out the "Set Invoice Fields" script in a clean copy of GoZyncConnector. The scenario here is that our mobile file keeps the invoiced contact and their address IN the invoice table, while our sample served solution (Invoices.fp7) has a separate customer table. So you'll find a piece of GoZyncConnector's "Set Invoice Fields" script where we leave the invoice, create a customer record, and return to use the newly created customer ID in our invoice. This happens between the comment "Splitting Tables..." and "...End Splitting Tables".
Notice that we can create additional "Set XXXX Fields" scripts, for entities that don't exist in our mobile file: the [[Data
For an example of how this works, check out the "Set Invoice Fields" script in a clean copy of GoZyncConnector. The scenario here is that our mobile file keeps the invoiced contact and their address IN the invoice table, while our sample served solution (Invoices.fp7) has a separate customer table. So you'll find a piece of GoZyncConnector's "Set Invoice Fields" script where we leave the invoice, create a customer record, and return to use the newly created customer ID in our invoice. This happens between the comment "Splitting Tables..." and "...End Splitting Tables".
Notice that we can create additional "Set XXXX Fields" scripts, for entities that don't exist in our mobile file: the [[Data
Changed lines 13-14 from:
to:
Remember that you don't have to simply send the $variable data from the mobile file into your database as is: you can perform calculations and transformation on the data in your "Set XXX Field" scripts. Here is a simple example..,
Changed lines 17-18 from:
to:
Transformations like these are one of the real strengths of GoZync in that they allow you to build mobile files that have a completely different structure from your served files. "Splitting Tables", below, is another popular transformation.
Changed lines 34-35 from:
to:
Upload a single from Mobile to GoZyncConnector (you can even do this in FileMaker Pro, instead of Go) and then try to process that 1 record from the [[TheInbox | Inbox]] in GoZyncConnector. If it fails, you'll see the first FIleMaker error reported right in the record's row in Inbox. Here are come common errors:
Changed lines 7-8 from:
!! Making your Field Mapping simpler
to:
!! Making your Field Mapping easier
Added lines 11-21:
!! "Transforming" Data
-> Remember that you don't have to simply send the $variable data from the mobile file into your database as is: you can perform calculations and transformation on the data in your "Set XXX Field" scripts. Here is a simple example..,
-> Let's say your local field has two fields for a contact's name, NameFirst and NameLast, but your served database has only one: FullName. You could set FullName to this: $NameFirst & " " & $NameLast.
-> Transformations like these are one of the real strengths of GoZync in that they allow you to build mobile files that have a completely different structure from your served files. "Splitting Tables", below, is another popular transformation.
!! Splitting Tables
-> Remember that you don't have to simply send the $variable data from the mobile file into your database as is: you can perform calculations and transformation on the data in your "Set XXX Field" scripts. Here is a simple example..,
-> Let's say your local field has two fields for a contact's name, NameFirst and NameLast, but your served database has only one: FullName. You could set FullName to this: $NameFirst & " " & $NameLast.
-> Transformations like these are one of the real strengths of GoZync in that they allow you to build mobile files that have a completely different structure from your served files. "Splitting Tables", below, is another popular transformation.
!! Splitting Tables
Changed lines 34-38 from:
Upload a single from Mobile to GoZyncConnector (you can even do this in FileMaker Pro, instead of Go) and then try to process that 1 record from the [[TheInbox | Inbox]] in GoZyncConnector. If it fails, you'll see the first FIleMaker error reported right in the record's row in Inbox. Here are come common errors:
-> Record is Missing. This is most likely because one or more of your table occurrences in the Packing and UnPacking section of the relationship graph in Connector do not have "Allow creation of records in this table..." checked. This needs to be "on" for each tale on your file's side of the relationship.
-> Good post but error anyway: set a calc etc.
-> Record is Missing. This is most likely because one or more of your table occurrences in the Packing and UnPacking section of the relationship graph in Connector do not have "Allow creation of records in this table..." checked. This needs to be "on" for each tale on your file's side of the relationship.
-> Good post but error anyway: set a calc etc.
to:
-> Upload a single from Mobile to GoZyncConnector (you can even do this in FileMaker Pro, instead of Go) and then try to process that 1 record from the [[TheInbox | Inbox]] in GoZyncConnector. If it fails, you'll see the first FIleMaker error reported right in the record's row in Inbox. Here are come common errors:
--> Record is Missing. This is most likely because one or more of your table occurrences in the Packing and UnPacking section of the relationship graph in Connector do not have "Allow creation of records in this table..." checked. This needs to be "on" for each tale on your file's side of the relationship.
--> Good post but error anyway: set a calc etc.
--> Record is Missing. This is most likely because one or more of your table occurrences in the Packing and UnPacking section of the relationship graph in Connector do not have "Allow creation of records in this table..." checked. This needs to be "on" for each tale on your file's side of the relationship.
--> Good post but error anyway: set a calc etc.
Changed lines 25-26 from:
-> Record is Missing. This is most likely because one or more of your table occurrences in the Packing and UnPacing section of the relationship graph in Connector do not have "Allow creation of records in this table..." checked. This needs to be "on" for each tale on your file's side of the relationship.
to:
-> Record is Missing. This is most likely because one or more of your table occurrences in the Packing and UnPacking section of the relationship graph in Connector do not have "Allow creation of records in this table..." checked. This needs to be "on" for each tale on your file's side of the relationship.
Changed lines 23-24 from:
to:
Upload a single from Mobile to GoZyncConnector (you can even do this in FileMaker Pro, instead of Go) and then try to process that 1 record from the [[TheInbox | Inbox]] in GoZyncConnector. If it fails, you'll see the first FIleMaker error reported right in the record's row in Inbox. Here are come common errors:
Changed lines 3-6 from:
! Overview
!! What field mapping does
!! What field mapping does
to:
!! Overview
Added lines 3-12:
! Overview
!! What field mapping does
! Using a Dictionary
!! Making your Field Mapping simpler
! Tips & Tricks
!! What field mapping does
! Using a Dictionary
!! Making your Field Mapping simpler
! Tips & Tricks
Changed lines 17-18 from:
-> Record is Missing. This is most likely because one or more of your table occurrences in the Packing and UnPacing section of the relationship graph in Connector do not have "Allow creation of records in this table..." checked. This needs to be "on" for each tale on your file's side of the relationship.
to:
-> Record is Missing. This is most likely because one or more of your table occurrences in the Packing and UnPacing section of the relationship graph in Connector do not have "Allow creation of records in this table..." checked. This needs to be "on" for each tale on your file's side of the relationship.
-> Good post but error anyway: set a calc etc.
-> Good post but error anyway: set a calc etc.
Changed line 17 from:
Record is Missing. This is most likely because one or more of your table occurrences in the Packing and UnPacing section of the relationship graph in Connector do not have "Allow creation of records in this table..." checked. This needs to be "on" for each tale on your file's side of the relationship.
to:
-> Record is Missing. This is most likely because one or more of your table occurrences in the Packing and UnPacing section of the relationship graph in Connector do not have "Allow creation of records in this table..." checked. This needs to be "on" for each tale on your file's side of the relationship.
Added lines 1-17:
(:title Tips for Field Mapping:)
!! Handling Related Records
> > Notes about saving the IDs of newly created parent records so you can make their children
!! More
> > More
! Troubleshooting Your Mapping
!! Common problems
Send a record from Mobile to GoZyncController (you can even do this in FileMaker Pro, instead of Go) and then try to process 1 record. If it fails, you'll see the first FIleMaker error reported right in the record's row in Inbox. Here are come common errors:
Record is Missing. This is most likely because one or more of your table occurrences in the Packing and UnPacing section of the relationship graph in Connector do not have "Allow creation of records in this table..." checked. This needs to be "on" for each tale on your file's side of the relationship.
!! Handling Related Records
> > Notes about saving the IDs of newly created parent records so you can make their children
!! More
> > More
! Troubleshooting Your Mapping
!! Common problems
Send a record from Mobile to GoZyncController (you can even do this in FileMaker Pro, instead of Go) and then try to process 1 record. If it fails, you'll see the first FIleMaker error reported right in the record's row in Inbox. Here are come common errors:
Record is Missing. This is most likely because one or more of your table occurrences in the Packing and UnPacing section of the relationship graph in Connector do not have "Allow creation of records in this table..." checked. This needs to be "on" for each tale on your file's side of the relationship.
