Glossary

-> '''Butterfly''' - Used to describe the type of relationship graph used in GoZyncMobile where from one context (the GoZync table occurrence) you can manipulate both hosted and local records. When you're on the GoZync table occurrence you're at "the center of the butterfly".

-> '''Primary TO or Parent TO''' - The parent table occurrence for your entity. For example, "Invoice" in a record made of an invoice record and one or more invoice line item records. It is a list of Zynced primary TO layouts you see in the configuration of GoZyncHosted: "child" TOs are indented in that list.

-> '''Primary TO''' - The parent table occurrence for your entity. For example, "Invoice" in a record made of an invoice record and one or more invoice line item records. It is a list of Zynced primary TO layouts you see in the configuration of GoZyncHosted: "child" TOs are indented in that list.

-> '''API''' - "Application Programming Interface" - These are scripts written so developers can tell GoZync what to do without getting deep into all the scripts that do it. =) More on the idea of an API from %newwin% [[http://en.wikipedia.org/wiki/API | wikipedia]].

-> '''Foreign Key''' - the primary key from another table, used inside a child table to link records together. So if we have Invoices and Invoice Line Items, the line items table contains a field for the invoice id: that is, the foreign key in the line items table.

-> '''Source Layout''' - The layout were we get

-> '''Primary TO''' - The parent table occurrence for your entity. For example, "Invoice" in a record made of an invoice record and one or more invoice line item records. It is a list of Zynced primary TO layouts you see in the dashboard of GoZyncHosted.

-> '''Mothership''' - our shorthand name for your hosted solution. We use this name because it (correctly) implies that your mobile solution is usually / should be a much simpler, mission-specific, version of your, more complicated, hosted solution: the "%newwin% [[http://en.wikipedia.org/wiki/Mother_ship | mothership]]."

-> '''Mothership''' - our shorthand name for your hosted solution. We use this name because it (correctly) implies that your mobile solution is usually / should be a much simpler, mission-specific, version of your, more complicated, hosted solution: the "mothership."

-> '''API''' - "Application Programming Interface" - these are scripts written so developers can tell GoZync what to do without getting deep into all the scripts that do it. =) More on the idea of an API from %newwin% [[http://en.wikipedia.org/wiki/API | wikipedia]].

-> '''Entity''' - More than a record, an entity is the database's depiction of a real-world object, usually comprising more than one record. So a "contact" is an entity comprised of a contact record and possibly one or more address records. An "invoice" is  comprised of the invoice record, one or more invoice line item records, and perhaps several related photo records. GoZync is transactional at the "entity" level. Whole entities are passed from mobile to host and back so you never have a "partial" entity-- an invoice with only some of it's line items, for example.

-> '''Foreign Key''' - the primary key from another table, used inside a child table to link records together. So if we have Invoices and Invoice Line Items, the line items table contains a field for the invoice id: that is the foreign key in the line items table.

-> '''Package''' - the text object GoZync created to represent your entity when syncing. Think of it as a textual description of the record. You can see an export packages on the inbox layout of GoZyncHosted.

-> '''Primary Key''' - this is the unique ID or serial number for your record. A contact's ID in a contact's database. This is probably a field you're already using to relate tables to each other.

-> '''Primary TO''' - the parent table occurrence for your entity. For example, "Invoice" in a record made of an invoice record and one or more invoice line item records. It is a list of Zynced primary TO layouts you see in the dashboard of GoZyncHosted.

-> '''TO''' - short for "table occurrence" - a representation of a table on the "Relationships" tab of "Manage / Database"

-> '''Entity''' - More than a record, an entity is the database's depiction of a real world object, usually comprising more than one record. So a "contact" is an entity comprised of a contact record and possibly one or more address records. An "invoice" is  comprised of the invoice record, one or more invoice line item records, and perhaps several related photo records. GoZync is transactional at the "entity" level. Whole entities are passed from mobile to host and back so you never have a "partial" entity-- an invoice with only some of it's line items, for example.

-> '''Primary Key''' - this is the unique ID or serial number for your record. A contacts's ID in a contact's database. This is probably field you're already using to related tables to each other.

-> '''Primary TO''' - the parent table occurrence for your entity. For example, "Invoice" in a record made of an invoice record and one or more invoice line item records. It is a list of zynced primary TO layouts that you see in the dashboard of GoZyncHosted.

-> '''Primary TO''' - the parent table occurrence for your entity. For example, "Invoice" in a record made of an invoice record and one or more invoice line item records.

-> '''Transaction''' - see the article "[[transactional]]".

...for things we might not have been explicit about elsewhere

-> '''Entity''' - more than a record, an entity is the database's depiction of a real world object, usually comprising more than one record. So a "contact" is an entity comprised of a contact record and possibly one or more address records. An "invoice" is  comprised of the invoice record, one or more invoice line item records, and perhaps several related photo records. GoZync is transactional at the "entity" level. Whole entities are passed from mobile to host and back so you never have a "partial" entity-- an invoice with only some of it's line items, for example.