Data Syncing FAQs
What happens when a farm is deleted? |
When a farm is deleted in Field360 Studio/Corteva Fields, fields of the farm are also deleted
- The farm and fields will be deleted from Granular
- In Field360 Studio/Corteva Fields, these are flagged as soft-deletes, and can be recovered by Support.
- Note, because all deletes in granular are hard-deletes, reactivating will create new farm and fields in Granular and prior data within the Granular Insights platform will be lost.
Default Farms
- Default farms in Field360 Studio/Corteva Fields cannot be edited or deleted
- In both systems, a field must belong to one and only one farm
- Users are currently unable to remove a farm in Insights. If no fields exist for a farm, the farm will not be visible in the Granular Insights platform.
Can I recover farms and boundaries in Field360 Studio/Corteva Fields? |
Deleting a boundary in Insights will soft delete the field in Field360 Studio/Corteva Fields. The boundary can be re-added in F360 Studio by calling Support.
- Support can be reached at 1-833-933-1733
- Option 3 - Granular Agronomy Support (Nitrogen, Fertility, and Field360 Studio)
Can I deactivate by Crop Year? |
In Field360 Studio/Corteva Fields, farms and fields can be activated and deactivated on a crop year basis. Whenever a field or farm is added to Field360 Studio/Corteva Fields, a crop year has to be specified.
- Activation and deactivation of farms and fields by crop year in Field360 Studio/Corteva Fields are ignored in the Insights platform.
In the Insights platform, there is no Crop Year activation of farm and field.
- Modifications to inactive farms and fields continue to be synchronized between the two systems.
When a field or farm is added to the Insights platform, it is added to Field360 Studio/Corteva Fields in the current calendar year crop year and all following defined crop years.
- Defined crop year means a BusinessCropYear record exists for the year. If the most recently defined crop year is before current calendar year, the field or farm is only assigned to the most recently defined crop year.
If there are inconsistent boundaries between systems or a boundary in one system and not the other, what happens? |
There are four scenarios to consider:
- Corteva boundaries exists, no Granular boundaries
- Corteva is the initial source of truth; all Farms/Fields will be created in Granular.
- Granular boundaries exist, no Corteva boundaries exist
- Granular is the initial source of truth; all Granular fields will be created in Corteva (Field360 Studio/Corteva Fields)
- Boundaries exist in both systems with significant (greater than or equal to 80%) spatial overlap
- 75% of time, Corteva boundary will be used
- Corteva, Deere, Autogen all update Granular boundary to match Corteva
- Exception: If a user edited the boundary in Insights for any reason, the Insights boundary will be used
- Boundaries exist in both systems without significant (less than) spatial overlap
- The result will be overlapping boundaries that will be reflected in both systems
- User may interpret as duplicate or incorrect
- Mitigation: User can delete boundary
What is interoperability? |
Simply put, this means that our Corteva systems (Corteva Fields, Pioneer Seeds, and Field360 Studio) and our Granular systems (Insights) are able to share data back and forth.
Why is this necessary? |
It’s a better user experience. Surveys show the #1 indicator of product satisfaction is confidence in [field] data, ie: our products visualize what actually occurred on the field. Making data consistent between digital products saves customers and advisors time, ensures accurate recommendations, and leads to higher data confidence and satisfaction in our portfolio of products.
There are four scenarios to consider:
- Corteva boundaries exists, no Granular boundaries
- Corteva is the initial source of truth; all Farms/Fields will be created in Granular.
- Granular boundaries exist, no Corteva boundaries exist
- Granular is the initial source of truth; all Granular fields will be created in Corteva (Field360 Studio/Corteva Fields)
- Boundaries exist in both systems with significant (greater than or equal to 80%) spatial overlap
- 75% of time, Corteva boundary will be used
- Corteva, Deere, Autogen all update Granular boundary to match Corteva
- Exception: If a user edited the boundary in Insights for any reason, the Insights boundary will be used
- Boundaries exist in both systems without significant (less than) spatial overlap
- The result will be overlapping boundaries that will be reflected in both systems
- User may interpret as duplicate or incorrect
- Mitigation: User can delete boundary
What if farm names do not match between systems? |
IF the collection of fields are the same, and farm name is different, THEN update Granular with the Farm name from Corteva
IF a collection of fields under a farm is different between the two systems, THEN update Granular so that the field collection is the same as Corteva.
What do you mean by farm/field sync? |
As an Insights user with a Corteva Connection...
- When I upload, draw, or claim a CLU boundary in Insights, that boundary is added in Corteva
- When I create, modify or delete a boundary in Insights, that boundary is modified or [soft] deleted in Corteva
As a Corteva user with a Granular Connection...
- When I upload, draw, or claim a CLU boundary in Corteva, that boundary is added in Insights
- When I create, modify or delete a boundary in Corteva, that boundary is modified or deleted in Insights
When I add or delete a farm or field in either system, the change will be reflected in the other.
