> For the complete documentation index, see [llms.txt](https://docs.geopard.tech/geopard-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geopard.tech/geopard-tutorials/product-tour-web-app/john-deere-operations-center-integration/11.-synchronize-a-field-with-john-deere-operations-center.md).
# 11. Synchronize a Field with John Deere Operations Center
GeoPard lets you synchronize a single field with John Deere Operations Center on demand.
Use it right after adding a field. Use it again after changing the boundary or updating the client and farm hierarchy.
GeoPard decides automatically whether to create the field in John Deere Operations Center or re-sync an existing one. You do not need to check its current state first.
{% hint style="info" %}
The **Synchronize field with John Deere Operations Center** action is visible only when your GeoPard account is connected to John Deere. If you do not see it, complete [Connect to John Deere Operations Center](https://docs.geopard.tech/geopard-tutorials/product-tour-web-app/john-deere-operations-center-integration/2.-connect-to-john-deere-operations-center).
{% endhint %}
### Before you start
Synchronization depends on two setup steps. If either one is missing, the sync will fail.
#### 1. Map GeoPard labels to the John Deere hierarchy
GeoPard organizes fields with labels. John Deere uses an **Organization → Client → Farm** hierarchy.
On the John Deere integration page, map your GeoPard labels to these John Deere levels:
* `organization` → Organization
* `client` → Client
* `farm` → Farm
If a matching label does not exist yet, create it first. See [Add a label](https://docs.geopard.tech/geopard-tutorials/product-tour-web-app/farm-and-field-setup/add-a-label).
#### 2. Add matching labels to the field
Open the field and check **Field Details** → **Labels**.
The field must contain the values that match your mapping. For example:
* `organization: AgriCore Solutions`
* `client: GreenField`
* `farm: Green Valley Farm`
These values place the field in the correct **Organization → Client → Farm** path in John Deere Operations Center.
### Synchronize a field
1. Open the field you want to send to John Deere Operations Center.
2. Click **Export** → **Synchronize field with John Deere Operations Center**.
3. Wait for the result notification.
### What happens when you click
GeoPard checks whether the field is already linked to John Deere Operations Center.
* If the field does not already exist in John Deere Operations Center, GeoPard creates it automatically based on the field's farm and client labels.
* If the field already exists in John Deere Operations Center, GeoPard updates its boundary, farm, and client information automatically during synchronization.
### Results you will see
After the action runs, GeoPard shows one of these notifications:
* **Field created in John Deere Operations Center** — the field had no John Deere link and was created successfully.
* **Field re-synced with John Deere Operations Center** — the field was already linked and its boundary and hierarchy were updated.
* **Synchronization failed** — the field could not be synchronized.
### Troubleshooting
If synchronization fails, check these items first:
* Your GeoPard account is connected to John Deere. See [2. Connect to John Deere Operations Center](https://docs.geopard.tech/geopard-tutorials/product-tour-web-app/john-deere-operations-center-integration/2.-connect-to-john-deere-operations-center).
* Your John Deere organization is enabled in GeoPard. See [3. Connect to John Deere Organizations](https://docs.geopard.tech/geopard-tutorials/product-tour-web-app/john-deere-operations-center-integration/3.-connect-to-john-deere-organizations).
* The field has all mapped labels, with the correct values.
* The label mapping matches the intended **Organization → Client → Farm** path.
The most common failure cause is missing or mismatched field labels.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.geopard.tech/geopard-tutorials/product-tour-web-app/john-deere-operations-center-integration/11.-synchronize-a-field-with-john-deere-operations-center.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.