How do I Review Customer Domain for Accuracy After Interop Reconciliation?

Overview:

To reconcile any differences between Granular and Corteva after creating a Corteva Connection, the following updates were made during the one-time reconciliation:

• Farms and field boundaries were added when they existed in one product, but not the other
• Fields may have moved between farms when farms differed between products
• Boundary edits made in one system, but not the other, are now reflected across all systems 
  • Corteva/F360 Boundaries and Farm/Field structure trump Granular's

We recommend that you review operations that have the Corteva/Granular connection. This will help ensure that farms, fields, and boundaries are accurate and complete in advance of critical business activities, such as adding crop zones, writing fertility prescriptions, importing harvest data, seeding prescriptions, or generating reports. Below are a few helpful tips to make this process as efficient as possible. 

Process:

Start by accessing your customer’s operation in Field360. 

1. Check Set Domain Status to see if there are any farms and fields that have been turned off that need to be re-activated. 
   
   • • 
     • 

2. Check Recover Domains to see if there is anything that needs to be recovered. Set ‘Begin Date/Time’ to date Corteva Connection was made (Date can be found in Corteva Fields.) Once recovered, you may need to check Set Domains status again.

   • 

3.  Go through each farm, field-by-field to verify that the field boundary is correct and/or matches the crop zone boundary. Using the color of the field boundary icon, is an easy way to assist in identifying acreage differences. For more information on this and to set a field’s boundary to be the same as the crop zone, follow these instructions. 

   • • 
4. Check the ‘created date’ for ERU/Soil Type layers. If created on or after the Corteva Fields connection date, this may indicate a new field created from the one-time reconciliation.  
   • • 
     • 
     • 
5. Review the farm and field hierarchy for accuracy. If the hierarchy is incorrect, fields can be moved by right-clicking on the field and selecting Transfer Domain to move it to the correct farm.
   • 
   • 
6. Once edits are made in Field360, those edits will be reflected throughout all of that customer’s accounts, including Corteva Fields and Granular Insights.

Tips and Tricks:

• Merge isn't an existing function anymore. The best solution is to create a new field in Insights and Archive the old fields. If working in F360 as well, you'd use Set Domain Status to turn off the old fields.
• Another option to merge fields, use the boundary editor and either draw additional polygons or import shapefiles directly into the field to get the boundary you want.
  • • 

    • The “Default Farm” is created when fields exist in Granular Insights without a farm name. "Default Farm” cannot be edited or deleted. Use Transfer Domain to move the field to the correct farm or to a new farm if needed. After the field has been moved out of “Default Farm,” use Set Domain Status to turn off the “Default Farm”.

    • Only raw data and not field operations data move from system to system, which is why yield maps aren’t identical. Machine data will need to be uploaded via Corteva Fields Web Upload tool or Granular Insights. If using Granular Insights, please check the Corteva data connection and verify that ‘Send Field Data’ is selected for the data to flow to Corteva.
    • It IS ok to Delete your Insights Operation and start with a new/blank Insights operation and Connect your F360 operation to the new operation if you feel your existing Insights account isn't accurate.