We grow pedigreed seed, so our varieties must be kept separate. Would be nice if the harvest data showed both varieties instead of merging them to just one.

Ability to track water volume on spray activities. Several customers have requested this lately as it will give a more accurate representation of costs.

We use the crop plan when communicating with advisors. It would be nice to have the total sum of acres in the crop plan. This would allow us to ensure each field is accounted for and no duplicates. An easy work around is to download the crop plan,...

Allow for subfield selection under field for crop planning. The subfields where put in place because of the intention to manage the areas differently. Would be able to get a more complete picture of input requirements.

When forage crop is planted, generally it is in the ground for at least 2 years and often more. It would save a lot of time to be able to apply a crop from a previous year to the next year or carry it forward some how when you start a new crop year.

be able to choose crop year when entering a contract

We apply inputs in the fall with input dollars being spent on the next spring's crop. It would be nice to add on to next year crop input costs.

During harvest activities we could add a checkbox to indicate what it was for, such as sileage/feed or hay, and then on the activities landing page include a sortable column to represent this data. Users find it helpful to quickly see and sort the...

1. Bale Count Entry for All Baling Types When recording baling activities on crop-share fields, the system only allows me to enter acres baled unless the baling is linked to a harvest event (such as hay). For straw baling, since the crop was alrea...

When adding fields to your crop plan it is easy to select fields twice. This throws off the cost/ac calculations and total acres. Not all fields are always seeded to the same crop or variety so it would be nice to be able to select a field and the...