1. Home
  2. Release Notes
  3. Feature / Hotfix Release: 8/23/24

Feature / Hotfix Release: 8/23/24

Fruit Sampling

Fruit sampling events can now be created in AgVerdict Next Web. There are a couple of differences from Tissue and Soil Sampling.

There are a couple of options present here:

  1. Variety: Specify the variety of the commodity. If the variety is already set on the land, it will automatically be set here. Setting the variety will help with threshold comparisons in the result analysis stage.
  2. Avg Fruit Size: Currently set up for apples and with weight buckets every 10g.
  3. Harvest sample: Indicate whether or not the sample is from harvest.
  4. Sampling Methodology: Default is an Average Composite sample. If you wish to capture more information during the sampling process, select “Scientific” for more options

This information will all be captured and included on the check-in sheet in a new section.

Sampling events can be marked as “Complete” using Edit on AgVerdict Next. Support for collecting fruit samples will also be present in the AgVerdict Next iOS application.

For uploading results, users will need to go through the Bulk Upload workflow in AgVerdict Classic for uploading csv files. We have added several new elements and UOMs to cover commonly used fruit measurements.

Lab Check-in Sheets

Lab check-in sheets have gotten a facelift. All of the previous information is still present, but has been rearranged to make better use of the space on the page and to provide room for a new feature: the QR Code. The QR Code on the sheet contains the Wilbur Ellis event ID for the sampling event, enabling labs to quickly scan the barcode to retrieve the identifier and connect with AgVerdict’s partner API to automatically download event data.

Update to Sampling Creation

The sales and inventory branches are no longer required for submitting a sampling event.

Addressed Issues

  • Fix for an issue where selecting the zone layer for Zone Composite sampling events would require users to set sample points in order to save the layer. This erroneous check has been removed.
  • The system was not displaying the correct payment term when creating an Order from a REC for certain Customers. The correct payment term is now displayed when creating an Order from a REC for all relevant customers, ensuring accurate and consistent payment information.
  • Previously, users had trouble removing all previous “bill to” and “ship to” addresses from a Growers account.
    • Users can now delete existing “bill to” addresses.
    • After deleting a “bill to” address, users can save their changes.
    • Users can then re-add a “bill to” address.
    • The system will update all “bill to” and “ship to” addresses for that grower to match the information on the Grower details page.

Was this article helpful?

Related Articles

Leave a Comment