Fieldprint Platform UI Release Notes
Version 5.0.12
Released: March 11th, 2026
Version 5.0.12 introduces intelligent date validation for activity data entry. Activity dates are now validated in the context of adjacent crop intervals, helping users catch and correct date conflicts between crop years. When a non-harvest activity date falls outside the expected range for its crop interval, the platform surfaces a clear error message and — where applicable — offers a one-click option to move the activity to the correct interval. Harvest dates are validated to ensure they fall within the harvest year and do not overlap with the next crop interval’s activities. This release also fixes an issue where switching between fields could leave stale data visible on screen.
| Area | Description | Type |
| Activity Date Validation – Cross-Interval Checks | Activity dates are now validated against adjacent crop intervals. Clear error messages guide users when a date falls outside the expected range for the current interval. | Enhancement |
| Activity Date – Move to Interval | When a non-harvest activity date conflicts with an adjacent interval and the date is within that interval’s range, a checkbox offers to move the activity to the correct interval with one click. | Enhancement |
| Harvest Date Validation | Harvest dates are now validated to fall within the calendar year of the harvest interval and to precede the first activity of the following crop interval. | Enhancement |
| Field Switching – Stale Data Fix | Navigating between fields now forces a full remount of the field component, preventing stale data from a previous field persisting on screen. | Bug Fix |
1. Activity Date Validation – Cross-Interval Checks
When entering or editing the date for an activity, the platform previously performed only a basic check — confirming the date was present and in a valid format. There was no check to ensure the date made sense within the context of the crop year being recorded, or in relation to adjacent crop intervals on the same field.
In v5.0.12, activity date validation now takes the surrounding crop intervals into account. The platform checks the date you enter against the harvest dates and activity dates of the previous and next crop intervals on the same field, and displays a specific, context-aware error message when a conflict is detected. Affected activity types include: Nutrient Commercial, Nutrient Manure, Nutrient Other, Planting Cover, Residue Management, Tillage, and Crop Protectant Spraying.
Examples of validation messages you may see:
- “Activities for 2024 Corn should be after 2023 Soybeans harvest on 10/15/2023.” — shown when an activity date falls on or before the previous year’s harvest date.
- “Activities for 2024 Corn should be before the harvest date of 11/01/2024.” — shown when an activity date falls on or after the current year’s harvest date.
2. Activity Date – Move to Interval Option
In some cases, an activity that was saved under one crop interval may actually belong to an adjacent interval — for example, a tillage or nutrient application entered in the wrong crop year. When the new date validation detects this situation — specifically, when the date falls within the range of an adjacent interval rather than the current one — the platform now offers a direct option to move the activity.
A checkbox appears below the date field with a label such as: “Move this activity to the 2023 Soybeans interval.” Checking this box reassigns the activity to the correct crop interval in a single step, without requiring the user to manually delete and re-enter the data.
This option is available for the following activity types (all non-harvest activities that accept a date): Nutrient Commercial, Nutrient Manure, Nutrient Other, Planting Cover, Residue Management, Tillage, and Crop Protectant Spraying.
3. Harvest Date – Year Boundary and Overlap Validation
The Harvest activity date field now has two additional validation checks specific to harvest dates:
Calendar year check:
The harvest date must fall within the calendar year of the crop interval. For example, a harvest date for a 2024 crop interval must be between January 1, 2024 and December 31, 2024. If the date falls outside this range, the platform displays: “Harvest date for 2024 Corn should be within the 2024 calendar year.”
Next-interval overlap check:
The harvest date must precede the earliest activity date in the following crop interval. If the harvest date falls on or after the first activity date of the next year’s interval, the platform displays: “Harvest date for 2024 Corn falls after the first 2025 Soybeans activity on [date]. Adjust the date for that activity before updating the harvest date.” This check prevents harvest and pre-plant activity dates from crossing over between crop years.
4. Field Switching – Stale Data Fix
When navigating from one field to another on the Dashboard, the field component was not always fully reloading. In some cases, data from the previously viewed field could persist on screen momentarily or cause the new field’s data to display incorrectly.
In v5.0.12, the field component is now forced to fully remount whenever the active field changes. This ensures the component always initialises fresh with the correct field’s data, eliminating the stale data issue entirely.
Version 5.0.11
Released: February 15th, 2026
Version 5.0.11 expands the Comprehensive Data Output (export) with a significant new set of source category columns for the Energy Use and Greenhouse Gas indicators. Project administrators and data users who download the Comprehensive Data Output will now find detailed breakdowns of energy use and GHG emissions by source category directly in the export file, eliminating the need to calculate these breakdowns manually from aggregate totals.
| Area | Description | Type |
| Comprehensive Data Output – Energy Use | 10 new source category columns added for Energy Use, covering on-farm mechanical, post-harvest, and upstream sources. | Enhancement |
| Comprehensive Data Output – Greenhouse Gas | 19 new source category columns added for Greenhouse Gas, covering on-farm mechanical, on-farm sources/sinks, post-harvest, and upstream sources. | Enhancement |
1. Comprehensive Data Output – Energy Use Source Category Columns
The Comprehensive Data Output previously included the overall Energy Use indicator score for each crop interval but did not break down that score by source category. In v5.0.11, 10 new columns have been added that report the Energy Use contribution from each individual source category, expressed in the same units as the overall indicator.
These columns allow project administrators and data analysts to understand the distribution of energy use across on-farm operations, post-harvest activities, and upstream supply chain inputs without needing to re-run or manually disaggregate the calculation.
| New Column Name | Source Category |
| Energy use associated with mobile on-farm machinery | On-farm Mechanical – Mobile |
| Energy use associated with stationary on-farm machinery | On-farm Mechanical – Stationary |
| Energy use associated with mobile post-harvest machinery | Post-Harvest – Mobile |
| Energy use associated with stationary post-harvest machinery | Post-Harvest – Stationary |
| Energy use associated with electricity generation and distribution | Upstream – Electricity |
| Energy use associated with production of fertilizers | Upstream – Fertilizers |
| Energy use associated with production of fuels | Upstream – Fuel Production |
| Energy use associated with production of pesticides | Upstream – Pesticides |
| Energy use associated with production of seed | Upstream – Seed |
| Energy use associated with transportation of agricultural inputs | Upstream – Inputs Transport |
2. Comprehensive Data Output – Greenhouse Gas Source Category Columns
Similarly, 19 new columns have been added for the Greenhouse Gas indicator, providing a detailed breakdown of GHG emissions by source category. These span on-farm mechanical sources, on-farm emissions and carbon sinks (including rice methane, soil N2O, lime and urea CO2, land use change, and biomass burning), post-harvest sources, and upstream supply chain emissions.
Together with the Energy Use additions, these columns give a complete picture of the source-level contributions that make up both indicators directly within the export file.
| New Column Name | Source Category |
| GHG associated with stationary on-farm machinery | On-farm Mechanical – Stationary |
| GHG associated with mobile on-farm machinery | On-farm Mechanical – Mobile |
| GHG associated with on-farm transportation of crop production | On-farm – Crop Transport |
| CH4 emissions from flooded rice cultivation | On-farm Sources/Sinks – CH4 Rice |
| CH4 flux from non-flooded soils | On-farm Sources/Sinks – CH4 Non-Flooded |
| CO2 from carbonate lime applications to soils | On-farm Sources/Sinks – Lime |
| CO2 from urea fertilizer applications | On-farm Sources/Sinks – Urea |
| Direct land use change emissions | On-farm Sources/Sinks – Land Use Change |
| Non-CO2 emissions from biomass burning | On-farm Sources/Sinks – Biomass Burning |
| Soil carbon stock changes | On-farm Sources/Sinks – Soil Carbon |
| Soil N2O | On-farm Sources/Sinks – Soil N2O |
| GHG emissions associated with stationary post-harvest machinery | Post-Harvest – Stationary |
| GHG emissions associated with post-harvest transportation of crop production | Post-Harvest – Crop Transport |
| GHG emissions associated with electricity generation and distribution | Upstream – Electricity |
| GHG emissions associated with production of fertilizers | Upstream – Fertilizers |
| GHG emissions associated with production of fuels | Upstream – Fuel Production |
| GHG emissions associated with production of pesticides | Upstream – Pesticides |
| GHG emissions associated with production of seed | Upstream – Seed |
| GHG emissions associated with transportation of agricultural inputs | Upstream – Inputs Transport |
Version 5.0.10
Released: January 8th, 2026
Version 5.0.10 introduces the ability to move a field from one farm to another directly from the Field Name dialog. Previously this dialog only allowed renaming a field. Users can now update both the field name and its parent farm in a single action.
| Area | Description | Type |
| Field Name Dialog – Move to Farm | The Edit Field Name dialog now includes a Farm dropdown, allowing users to reassign a field to a different farm in their account at the same time as renaming it. | Enhancement |
1. Field Name Dialog – Move Field to a Different Farm
When editing a field from the Dashboard, clicking the edit (rename) action opens the Field Name dialog. In previous releases, this dialog contained only a text field for updating the field name.
In v5.0.10, a Farm dropdown has been added to this dialog. The dropdown is pre-populated with the field’s current farm and lists all farms in the account. Users can select a different farm to reassign the field, either alongside a name change or independently.
How to use it:
- Navigate to your Dashboard and locate the field you want to move.
- Click the field’s action menu and select the rename/edit option to open the Field Name dialog.
- The current field name and current farm are pre-filled.
- Update the field name if desired.
- Select a different farm from the Farm dropdown to move the field.
- Click Save. The field will be renamed and/or moved to the selected farm.
Version 5.0.9
Released: January 5th, 2026
Version 5.0.9 is a focused patch release with three user-facing fixes. The Greenhouse Gas indicator detail page now displays the correct dynamic unit label in the emissions breakdown table. The Harvest activity form no longer crashes when yield unit data is absent. These two fixes resolve display and stability issues introduced or exposed in recent releases. The release also includes a backend infrastructure update adding structured schema validation for user flags and improved production logging configuration — neither of which affects standard user workflows.
| Area | Description | Type |
| GHG Indicator – Emissions Table Units | The column header in the Greenhouse Gas emissions breakdown table now displays the correct unit label sourced dynamically from the result data, rather than a hardcoded value. | Bug Fix |
| Harvest Activity – Yield Unit Safety | The yield field no longer throws an error when unit data is missing or not yet loaded for a crop interval, preventing a crash on the Harvest activity form. | Bug Fix |
| Backend – User Flags Schema | The user flags field now uses a structured JSON schema (with a defined “debug” boolean property), improving admin usability. No user-facing change. | Enhancement |
1. Greenhouse Gas Indicator – Emissions Table Unit Label Corrected
The Greenhouse Gas indicator detail page includes a breakdown table showing emissions by system boundary and source category, with a column displaying the emission value for each row. The column header for this value column previously displayed a hardcoded label of “lb CO₂e/lb” regardless of the actual units of the result data.
In v5.0.9, this hardcoded label has been replaced with a dynamic value sourced directly from the result table data (tableData.units). This ensures the column header always reflects the correct unit for the current crop interval’s GHG calculation, which may vary by crop type or system configuration.
2. Harvest Activity – Yield Unit Crash Fixed
When opening the Harvest activity form for a crop interval, the platform reads the previously saved yield unit to pre-populate the unit selector in the yield quantity field. In some circumstances — particularly when a crop interval is newly created or when the yield input object has not yet been fully initialized — the yield unit value could be undefined, causing the form to throw a JavaScript error and preventing the Harvest activity from loading.
In v5.0.9, the yield unit reference has been made safe by using optional chaining (activity.inputs.yield?.unit instead of activity.inputs.yield.unit). If the unit value is absent, the field gracefully falls back to its default unit rather than crashing.
Version 5.0.8
Released: December 29th, 2025
Version 5.0.8 is a focused maintenance release that reorganizes the navigation menu, removes the Import Crop Years option, fixes field property unit display labels, improves the ready-state detection for the Import Fields workflow, and updates the Import Fields documentation text. No new features are introduced, and no data entry changes are required.
| Area | Description | Type |
| Navigation – User Menu | Import Fields and Copy Intervals moved into the User Menu, shown only for real (non-delegate) users and impersonators. Import Crop Years removed. | Enhancement |
| Field Properties – Unit Labels | Soil property unit labels (slope, slope length, clay content) updated from units= to unitsVisual= so they display correctly without affecting submitted values. | Bug Fix |
| Import Fields – Ready State | The ready/loading state for Import Fields now tracks the farm summary query fetch status instead of a Redux sync flag, improving reliability after an import completes. | Bug Fix |
| Import Fields – Documentation | The Import Fields description text updated: column header renamed from “Plantable Acres (Size)” to “Plantable Acres,” Clay (%) column noted, and introductory wording tidied. | Enhancement |
| Import Fields – Post-import Refresh | After a successful field import, the farm summary query is now explicitly invalidated to ensure the Field Library refreshes immediately. | Bug Fix |
| Importer – Run Records Text | Post-import guidance text updated to say “confirm and add Crop intervals” instead of “adding Crop years” to align with current platform terminology. | Enhancement |
1. Navigation – User Menu Reorganization
The placement of the Import Fields and Copy Intervals navigation items has changed in v5.0.8. In v5.0.7, Copy Intervals appeared as a standalone item in the main left-side navigation drawer visible to all logged-in users.
In v5.0.8, both Import Fields and Copy Intervals have been moved into the User Menu (the dropdown accessible from the account icon in the top-right corner of the screen). Both items are now grouped together and are only shown to real users and authorized impersonators — they are hidden when accessing the platform via a delegate session.
Additionally, the “Import Crop Years” option that previously appeared in the User Menu has been removed in this release. The Import Fields capability remains fully available.
2. Field Properties – Soil Property Unit Labels Corrected
The Field Properties screen displays several soil-related data fields where values are entered alongside a unit label (for example, slope as a percentage, slope length in feet, and clay content as a percentage). These fields use a QuantityField component that distinguishes between a units= prop (which affects the submitted data value) and a unitsVisual= prop (which is display-only and does not alter the submitted value).
In v5.0.7 and earlier, the slope, slope length, and clay content fields were passing their unit labels via the units= prop, which could cause the unit suffix to be inadvertently included in the saved value in some circumstances. In v5.0.8, these fields have been updated to use the unitsVisual= prop instead, so the unit labels (%, ft) are shown purely for display purposes and have no effect on the underlying values stored.
3. Import Fields – Improved Ready State Detection
After completing a field import, the platform displays a “Refreshing Field Library” spinner while it waits for the data to reload before redirecting the user. Previously, the readiness check relied on a Redux sync flag (state.sync.ready) to determine when the reload was complete.
In v5.0.8, this check has been updated to instead track the fetch status of the farm summary query directly. The ready state is now derived from whether the farm summary query is currently fetching: the spinner shows while the query is loading, and clears when the fetch completes. This approach is more reliable and consistent with the platform’s current data-fetching architecture.
4. Import Fields – Updated Column Documentation
The Import Fields instructions page describes the columns expected in the import file. Two updates have been made to this documentation:
- The column previously listed as “Plantable Acres (Size)” has been renamed to “Plantable Acres” to match the current column header used in the import template.
- A new “Clay (%)” column has been added to the documented list of supported import fields.
- The introductory sentence describing Import Fields as a “new feature” has been updated to simply describe it as “a feature” since it is no longer newly introduced.
5. Import Fields – Field Library Refresh After Import
When a field import completes, the platform now explicitly invalidates the farm summary query cache in addition to the existing reload logic. This ensures the Field Library panel and any downstream components that depend on the farm summary data are fully refreshed immediately after an import, without requiring a manual page reload or waiting for a background sync cycle.
6. Importer – Post-Import Guidance Text Updated
After a field import completes successfully, the importer displays guidance text directing the user to the Field page to begin entering data. This text previously read: “From the Field Page, you can begin adding Crop years or use Modify Field Location…”
In v5.0.8, this text has been updated to: “From the Field Page, you can confirm and add Crop intervals or use Modify Field Location…” The terms “Crop years” and “adding” have been replaced with “Crop intervals” and “confirm and add” to align with current platform terminology and workflow guidance.
This is a text-only update with no functional change.
Version 5.0.7
Released: December 22nd, 2025
Version 5.0.7 introduces the Copy Intervals feature — a major new workflow that allows users to duplicate crop management data from one field and interval to multiple target fields across their account. This release also adds a “Copied Interval” chip to the crop year card when data has been copied, corrects a typo in the Nutrient Application Management section, fixes the Residue Management operation help text, and improves cache invalidation after field mutations.
| Area | Description | Type |
| Copy Intervals | New feature: duplicate crop management data from a completed source interval to one or more target fields and crop years across the account. Accessible from the main navigation and the crop year ellipsis menu. | Enhancement |
| Crop Year Card – Copied Chip | A “Copied Interval” chip now appears on crop year cards that were created or populated using the Copy Intervals feature. | Enhancement |
| Nutrient Application Management | Corrected a typo: “nutient” corrected to “nutrient” in the nutrient rate adjustment question. | Bug Fix |
| Residue Management – Help Text | Operation help text in the Residue Management activity now correctly reads from the ui_help_text field rather than the internal notes field. | Bug Fix |
| Field API – Cache Invalidation | Added support for a reload_all flag in field mutation responses, allowing the platform to fully refresh all queries when needed after a copy operation. | Enhancement |
1. Copy Intervals – New Feature
The Copy Intervals feature allows you to duplicate the complete crop management data from one field’s crop year into one or more target fields and crop years across your account. This is especially useful when you manage multiple fields with similar or identical management practices and want to avoid re-entering the same data for each one.
Accessing Copy Intervals:
The feature can be accessed in two ways:
- From the main navigation sidebar, select “Copy Intervals” (indicated by a copy icon).
- From the ellipsis (…) menu on any completed crop year card, select “Copy Interval Data.” This option is only available when both activities and additional data have been confirmed for the interval. Using this shortcut pre-populates the source selection with the selected interval.
How the Copy Intervals wizard works:
The feature uses a guided three-step wizard:
- Step 1 – Pick Source Interval: Select the source farm, field, and crop year you want to copy from. Only fully confirmed intervals (with activities and additional data both marked complete) are available as sources. Select the harvest year you wish to copy.
- Step 2 – Pick Target Intervals: Select one or more target fields from across all farms in your account. A table then displays those fields with columns for each recent crop year (the current year plus the next, and five prior years). For each field and year combination, the existing crop is shown. You can click any cell to select it as a copy target. Cells are disabled if the year already contains a different crop that does not match the source. A checkbox at the top of each year column lets you select or deselect all eligible targets for that year at once. A link to show historical years back to 2008 is also available.
- Step 3 – Confirm and Apply: Review a summary showing the source interval and all selected target intervals. A prominent warning reminds you that copying will permanently overwrite any existing data in the target intervals. Click Confirm to proceed.
After confirming:
The platform processes the copy in the background and displays a success or error message. From the confirmation screen you can return to the Dashboard or start another copy operation.
2. Crop Year Card – “Copied Interval” Status Chip
When a crop year interval has been populated using the Copy Intervals feature, a new “Copied Interval” chip appears on the crop year card in the dashboard. This chip is displayed in an informational (blue) style to distinguish it from other status chips (such as Analysis Complete or Data Submitted).
The chip gives you a clear visual indicator that the data in that interval was not entered manually but was duplicated from another source interval, which can be useful context when reviewing or auditing your data.
3. Nutrient Application Management – Typo Corrected
The Nutrient Application Management section includes a question asking: “Was the nutient rate adjusted based on any of the following?” The word “nutient” was a typographical error for “nutrient.” This has been corrected to read: “Was the nutrient rate adjusted based on any of the following?”
This is a display-only correction. No data or functionality has changed.
4. Residue Management – Operation Help Text Corrected
When selecting a residue management operation type, a help text description is displayed below the operation dropdown to provide guidance on what the selected operation represents. Previously, this text was being read from an internal “notes” field intended for developers rather than the “ui_help_text” field intended for user-facing display.
In v5.0.7, the help text now correctly reads from the “ui_help_text” field, ensuring the displayed description is the intended user-facing guidance rather than internal notes.
5. Field API – Full Cache Invalidation Support
When the platform performs field mutations (such as copying an interval), the server response can now include a “reload_all” flag. When this flag is present, the platform invalidates all cached queries, ensuring that the dashboard, field listings, and other views fully refresh to reflect the new data state. This prevents stale data from appearing in the interface after a copy operation completes.
Version 5.0.6
Released: December 10th, 2025
Version 5.0.6 delivers a broad set of improvements across data entry, field information display, reports, and platform data consistency. Key highlights include the Dashboard Map now showing the last crop year alongside the crop name, the printable report header now correctly sourcing field size and project name from calculated metadata, the Activity menu being renamed for clarity, Harvest drying systems now driven entirely by reference data, the Planting Cash operation filter being corrected to use crop-specific flags, Cover Crop growth options updated to use the new reference data key, Tile Drainage adding the “No tile drainage system” option back, the Nutrient Other product list updated to the new reference key, Water Regime Management updated to the new rice water management types key, and a large reference data restructuring that renames and consolidates several lookup tables. The debug-only “Preview Report” button has also been removed from the Analysis Results page.
| Area | Description | Type |
| Dashboard Map | Field popups on the map now show the last crop year alongside the crop name. Fields with no active crop intervals now fall back to CLU history data. | Enhancement |
| Printable Report Header | Field size and project name in the printable report header are now sourced from calculated result metadata, ensuring accuracy. | Bug Fix |
| Analysis & Report Navigation | The “View Analysis” and “Generate Report” menu items have been merged into a single “View Analysis & Report” option. The project name is also now passed into the PDF generation payload. | Enhancement |
| Harvest – Drying Systems | Drying system options are now fully driven by reference data rather than hardcoded lists. Two new Alfalfa-specific dryer types added: Hay Dryer Without Gas Heating and Hay Dryer With Gas Heating. | Enhancement |
| Harvest – Transport Fuel | Transport fuel types now reference the renamed TransportationFuelTypes reference data key. | Bug Fix |
| Harvest – Yield Minimum | The minimum yield validation now enforces a hard minimum of 0.5 with a user-facing error message. | Enhancement |
| Planting Cash – Operation Filter | The planting operation list is now filtered by crop-specific flag rather than UI group, correctly separating Rice and non-Rice operations. | Bug Fix |
| Planting Cover – Growth Options | Cover crop growth options now reference the renamed CoverCropGrowth reference data key. | Bug Fix |
| Tile Drainage | “No tile drainage system” option restored to the Tile Drainage selection. | Enhancement |
| Conservation Practices | The UI visibility filter has been removed; all conservation practices from reference data are now shown. | Enhancement |
| Land Use Changes | Forest dominant genus list now references the renamed ForestGenusTypes reference data key. | Bug Fix |
| Nutrient Manure | Animal source lookup updated to renamed ManureAnimalSources key; manure rate lookup logic improved with a fallback to generic limits when crop-specific limits are unavailable. | Bug Fix |
| Nutrient Other | Amendment product list updated to use the new OtherNutrientProducts reference data key (Compost and other products). | Enhancement |
| Water Regime Management | Rice water management options updated to reference the renamed RiceWaterManagementTypes reference data key. | Bug Fix |
| API Tool & Prefill | The “Defaults” API endpoint has been renamed to “Prefill Crop Intervals” throughout the platform. | Enhancement |
| Reference Data Restructuring | Several reference data tables renamed and consolidated; unused Operations table removed. | Enhancement |
1. Dashboard Map – Last Crop Year Now Displayed
The interactive map on the Field Dashboard displays popup cards for each field when you hover or click on them. Previously, the popup showed the last crop name but not the year it was grown. In v5.0.6, the popup now displays both the crop name and the harvest year (e.g., “Corn (2024)”).
Additionally, the logic for determining the last crop has been improved. Fields with no active crop intervals now fall back to CLU (Common Land Unit) history data, displaying the historical crop and year with a “CLU” indicator. Fields with no crop data at all show “None/Other.”
2. Printable Report – Field Size and Project Name Fixed
The header section of the printable Fieldprint Report includes key field metadata: plantable acres, field location, and project name. In previous releases, field size and location were being read directly from the field object rather than from the calculated result metadata, which could result in missing or inconsistent values if the field object was not fully populated at render time.
In v5.0.6, both field size and location are now sourced from the calculated result metadata (“boundaryAcres” and “location” fields), ensuring they always reflect the values used in the actual calculation. The project name is now also passed through the calculation payload and displayed in the report header when available, so the report clearly identifies which project the crop interval belongs to.
3. Crop Year Menu – “View Analysis & Report” Combined
The ellipsis menu on a crop year card previously offered two separate options: “View Analysis” and “Generate Report.” These navigated to related but different parts of the platform. In v5.0.6, these two items have been consolidated into a single option: “View Analysis & Report.”
Clicking this option navigates to the Analysis Results page, where both indicator analysis and the Generate PDF report button are accessible in one place. This consolidation reflects the workflow improvement introduced in v5.0.3 where PDF generation was integrated directly into the Analysis Results page.
4. Harvest – Drying Systems Now Reference-Data Driven
When recording crop drying in the Harvest activity, users select a drying system from a dropdown list. Previously, this list was hardcoded in the application with fixed options for standard crops and a separate hardcoded list for Alfalfa. In v5.0.6, drying system options are now fully driven by the platform’s reference data, using a flag to distinguish between standard and Alfalfa-specific systems.
Two new Alfalfa drying system options are now available as a result of this change:
- Hay Dryer Without Gas Heating
- Hay Dryer With Gas Heating
The existing seven drying system options for standard crops remain unchanged.
5. Harvest – Transport Fuel Types Updated
The transport fuel type dropdown in the Harvest activity previously referenced a reference data key called “HarvestTransportationFuel.” This key has been renamed to “TransportationFuelTypes” as part of the broader reference data restructuring in this release. The component now uses the updated key name. The available fuel type options are unchanged.
6. Harvest – Hard Minimum Yield Validation
The yield quantity field in the Harvest activity now enforces a hard minimum value of 0.5. In previous releases, the minimum value check used a generic “value cannot be less than 0” validation. The field has been updated to support a configurable hard minimum, and the Harvest activity now passes 0.5 as the hard minimum for yield, displaying a specific error message: “Value cannot be less than 0.5!” if a lower value is entered.
7. Planting Cash – Operation List Filter Corrected
The Planting Cash activity filters the list of available planting operations based on whether the crop is Rice or a standard crop. Previously, this filter used the operation’s “ui_group” field to determine which operations to show or hide. This approach was misaligned with how operations are actually categorized in the reference data.
In v5.0.6, the filter now correctly uses the “crop_specific” field on each operation, showing Rice-specific operations for Rice crops and operations marked “No” (i.e., not crop-specific) for all other crops. This ensures the correct set of planting operations is presented for each crop type.
8. Planting Cover – Growth Coverage Options Updated
The cover crop growth coverage dropdown previously referenced a reference data key called “GrowthCoverage.” This key has been renamed to “CoverCropGrowth” as part of the reference data restructuring in this release. The component now references the updated key. The available growth coverage options are unchanged.
9. Tile Drainage – “No Tile Drainage System” Option Restored
In v5.0.5, the Tile Drainage selection was updated to display all options from reference data. However, the reference data at that time only contained two options (Standard density and High Density). In v5.0.6, a third option — “No tile drainage system” — has been added back to the reference data, but the UI has been updated to explicitly exclude it from the selection list using a filter.
This means the displayed options in the Tile Drainage section now include:
- Standard density
- High Density
The “No tile drainage system” entry remains in the reference data for use in calculations but is intentionally not offered as a user-selectable option in the field setup form, as the absence of a selection serves the same purpose.
10. Conservation Practices – UI Filter Removed
The Conservation Practices section in the field setup previously applied a “ui_show” filter to the reference data, limiting the displayed practices to those explicitly marked for UI display. One practice — “Cover Crop” — was removed from the reference data in v5.0.5, which reduced the list to 40 items.
In v5.0.6, the “ui_show” filter has been removed entirely. All 40 conservation practices in the current reference data are now displayed directly without filtering. This simplifies the data model and ensures the displayed list always matches the full reference dataset.
11. Land Use Changes – Forest Genus List Updated
The Land Use Changes section includes a field for selecting the dominant forest genus type when a land use change involves forestland. This dropdown previously referenced a key called “DominantGenusTypes.” As part of the reference data restructuring, this key has been renamed to “ForestGenusTypes.” The component now uses the updated key name. The available genus options are unchanged.
12. Nutrient Manure – Animal Source Lookup and Rate Fallback Fixed
Two fixes were made to the Nutrient Manure activity in this release:
Animal source reference key renamed:
The animal source dropdown previously referenced a key called “ManureAnimalSource.” This has been renamed to “ManureAnimalSources” (plural). The component now uses the correct key. Available animal source options are unchanged.
Manure rate fallback logic improved:
When the platform looks up manure application rate limits for a given animal source and moisture designation, it previously required an exact match. If no match was found for a specific animal source, no limit was returned. In v5.0.6, the lookup now falls back to generic (“Any”) limits when no crop-specific limits are found for the selected animal source, ensuring rate guidance is always available regardless of the specific source selected.
13. Nutrient Other – Product List Updated
The Nutrient Other activity allows users to record the application of amendment products beyond commercial fertilizer and manure. The product type dropdown previously referenced a key called “AmendmentTypes.” This key has been replaced with a new “OtherNutrientProducts” reference data table, which currently contains two options: Compost and one additional product type.
14. Water Regime Management – Rice Water Management Types Updated
The Water Regime Management section for Rice crops includes a dropdown for selecting the water management type. This dropdown previously referenced a key called “RiceWaterRegimes.” As part of the reference data restructuring, this has been renamed to “RiceWaterManagementTypes.” The component now uses the updated key. Available water management options are unchanged.
15. API Tool – “Defaults” Renamed to “Prefill Crop Intervals”
The API Tool and related prefill functionality have been updated to use a renamed backend endpoint. What was previously called “Defaults” (accessible at “calc/Defaults”) is now named “Prefill Crop Intervals” and accessed at “FieldData/PrefillCropIntervals.” Similarly, the field history prefill endpoint “calc/FieldCropyears” has been renamed to “FieldData/PrefillFieldHistory.”
In the API Tool dropdown, the option previously labeled “Defaults” now appears as “Prefill Crop Intervals.” The functionality is the same — only the name and endpoint path have changed.
16. Reference Data – Tables Renamed and Consolidated
A significant restructuring of the platform’s reference data was completed in this release. Several lookup tables have been renamed for consistency, and the large “Operations” table has been removed and replaced with more specific operation type tables that were already in use. The overall reference data file size has been substantially reduced as a result.
Key renames:
- ManureAnimalSource → ManureAnimalSources
- HarvestTransportationFuel → TransportationFuelTypes
- RiceWaterRegimes → RiceWaterManagementTypes
- DominantGenusTypes → ForestGenusTypes
- AmendmentTypes → OtherNutrientProducts
- GrowthCoverage → CoverCropGrowth (restored)
Removed tables:
- Operations (replaced by existing specific operation type tables)
- AlfalfaDryingSystems, AlfalfaHarvestTypes (folded into DryingSystems with flags)
- RicePlantingMethods, AbandonmentReasons, CoverCropSeedingRates, GrowthCoverage (old key)
Version 5.0.5
Released: November 11th, 2025
Version 5.0.5 is a significant feature release for the Fieldprint Platform. The headline addition is a new Project Survey capability, allowing project administrators to configure supplemental questions for enrolled growers — with completion of that survey now required before growers can submit data to a project. This release also improves the Project Opt-Out workflow with a safety check that prevents opt-out when data is already associated, adds real-time progress tracking to the Admin recalculation tool, introduces the Fieldprint Project Report as a new downloadable report type, expands N Balance availability across more crops, removes the N Balance project flag from project setup, removes several data entry options that are no longer supported, and cleans up reference data by removing unused lookup tables.
| Area | Description | Type |
| Project Survey | A new supplemental survey panel appears on the Crop Year Activities page for growers enrolled in projects with survey questions configured. Survey completion is required before submitting data to the project. | Enhancement |
| Submit Data to Project | The Submit Data button now also checks whether the project survey (if applicable) has been completed before allowing submission. The status message updates accordingly. | Enhancement |
| Project Opt-Out | The Opt-Out button is now disabled when a project has associated data, preventing accidental removal. The tooltip clearly indicates why the button is unavailable. | Enhancement |
| Admin Recalculation | The Recalculate tool in Admin Details now shows live progress — including count, ETA, and error reporting — as crop intervals are processed. | Enhancement |
| Fieldprint Project Report | A new “Fieldprint Project Report” (HTML format) has been added to the Project Reports download options. | Enhancement |
| N Balance Availability | N Balance is now available for all supported crops without a year restriction, and no longer requires a project-level flag. The “Will this project report on N Balance?” checkbox has been removed from project setup. | Enhancement |
| Data Entry – Removed Options | Inter-seed Planter (planting operation), Baling and Grazing (residue management operations) have been removed from their respective activity dropdowns. | Enhancement |
| Reference Data Cleanup | Twenty-three unused reference data lookup tables have been removed from the platform, including HPI-related land type and surface water tables. | Enhancement |
1. Project Survey – New Supplemental Questions for Enrolled Growers
Project administrators can now configure supplemental survey questions for their projects. When a grower has a crop interval enrolled in a project that has surveys enabled, a new “Additional Survey Questions” panel appears on the Crop Year Activities page for that interval.
The survey panel displays a button labeled with the project name (e.g., “Additional Questions for [Project Name]”). Clicking it opens a dialog containing the survey questions. The current implementation includes questions specific to wheat production:
- Seed Variety Mix – Growers can enter up to three wheat seed varieties with percentage amounts. Amounts must total 100%. If “Other” is selected as a variety, a free-text field appears to capture the variety name.
- Use of Variable-Rate Technology – Growers select which variable-rate practices were used during the crop year: Seeding, Nitrogen Application, or None.
- Optional Notes – A free-text notes field is available for recording any additional context about conditions, management changes, or other factors that affected the crop year.
Survey responses are saved as part of the crop interval’s additional data. The survey panel only appears when the enrolled project has surveys enabled and the crop interval’s crop type matches one of the project’s configured crops.
2. Submit Data to Project – Survey Completion Now Required
The “Submit data to project” button on the crop year panel now checks two conditions before allowing submission: the crop interval analysis must be complete, and — if the project has a survey configured — the Project Survey must also be marked as reviewed.
If either condition is not met, the button is disabled and a message below it tells the grower exactly what needs to be completed. For example:
- “Complete analysis to submit data.” – Analysis has not been run yet.
- “Complete additional survey questions to submit data.” – Survey has not been completed.
- “Complete analysis and additional survey questions to submit data.” – Both are outstanding.
3. Project Dashboard – Safer Project Opt-Out
The Opt-Out button on the Project Dashboard (the cancel icon next to each enrolled project) previously allowed growers to opt out of a project at any time, including after data had already been submitted or associated with the project. This could lead to data integrity issues.
In v5.0.5, the platform checks whether any project data is associated with the project before allowing opt-out. If data exists, the Opt-Out button is visually disabled (shown in grey) and the tooltip changes from “Opt Out” to “Data Associated,” making it clear why the action is unavailable. If no data is associated, the button remains active and the opt-out flow proceeds as before with a confirmation dialog.
4. Admin Details – Recalculation Progress Tracking
Project administrators use the Recalculate tool in Admin Details to trigger a recalculation of indicator scores for all crop intervals in a project. Previously, clicking the recalculate button provided no real-time feedback — administrators had to wait without knowing how far along the process was.
In v5.0.5, the recalculation now runs in the background with live progress updates displayed in the Admin Details panel. As crop intervals are processed, the UI shows:
- A progress counter showing how many crop intervals have been processed out of the total (e.g., “Processed 47 of 312 crop intervals”).
- An estimated time remaining (ETA) for the recalculation to complete.
- An error count if any crop intervals fail to recalculate, so administrators can identify and follow up on problem records.
- A completion message when all intervals have been processed.
5. Project Reports – New Fieldprint Project Report
A new report type — the Fieldprint Project Report — has been added to the Project Reports download page. This report is available in HTML format and is designed to give project administrators a comprehensive, ready-to-share view of project sustainability performance.
The Fieldprint Project Report includes:
- Project snapshot: Entered acres, number of fields, grower participation rates, and maps showing the project footprint.
- Abridged documentation: Descriptions of indicators, functional units, and methodologies.
- Performance analysis: Charts and tables showing how enrolled fields perform across eight sustainability areas, including trend analysis and category breakdowns.
- Contextual analysis: Data on agricultural inputs (fertilizers, manure, irrigation, crop protectants), yield, soil properties, and conservation practices.
- Rich content: The report includes 4 maps, 52 charts, and 32 summary tables.
The existing report description text on the Reports page has also been updated to more clearly describe the report’s purpose and contents.
6. N Balance – Expanded Availability, Project Flag Removed
N Balance data collection and reporting has been updated in two ways in this release:
Expanded crop and year eligibility:
N Balance is now available for Corn, Soybean, and Wheat projects, using updated crop ID references aligned with the current platform crop list. The previous year restriction (requiring crop year 2024 or later) has been removed, making N Balance available for any qualifying crop interval regardless of year.
Project-level flag removed:
The project setup screen previously included a checkbox — “Will this project report on N Balance?” — that project administrators had to enable before N Balance would be collected for enrolled growers. This flag has been removed. N Balance availability is now determined automatically based on crop type alone, simplifying project configuration.
7. Data Entry – Removed Activity Options
Three activity options have been removed from data entry dropdowns in this release, following a review of supported operations:
- Inter-seed Planter (Planting Operations) – This planting operation type has been removed from the Planting activity operation dropdown. It was associated with the inter-seeded cover crop termination workflow that was also removed in v5.0.3.
- Baling (Residue Management Operations) – The Baling option has been removed from the Residue Management activity operation dropdown.
- Grazing (Residue Management Operations) – The Grazing option has been removed from the Residue Management activity operation dropdown.
8. Reference Data – Unused Lookup Tables Removed
Twenty-three unused reference data lookup tables have been removed from the platform in this release. These tables were associated with features that have been superseded or are no longer active, including HPI (Habitat Potential Index) land type classifications, surface water management options, and related land use categories.
This cleanup reduces unnecessary data loaded by the platform and has no impact on data entry, indicator calculations, or existing crop year data.
Removed tables include:
- HPI-related: CoverCrop, CoverCropTypes, CoverCropLegumeTypes, CoverCropGrowth, NoncultivatedLandTypes, GrasslandManagement, GrasslandConfiguration, ForestManagement, ForestConfiguration, GrazingIntensity, RiparianManagement, RiparianVegetation
- Surface water: SurfaceWaterManagement, SurfaceWaterPredominantUse, SurfaceWaterInstreamHabitat, SurfaceWaterChannelization, SurfaceWaterRiparianVegetation, SurfaceWaterBufferPercentage, SurfaceWaterAverageDepth
- Other: BankManagement, BankStability, WetlandManagement, NaturalWetlandRegime
Version 5.0.4
Released: October 28th, 2025
Version 5.0.4 delivers three targeted improvements to the Fieldprint Platform user interface. This release activates Project Benchmark comparisons on the Fieldprint Spidergram, allowing enrolled users to compare their indicator scores against their project’s benchmark group directly from the Analysis Results page. It also hides the Crop Failure / Abandonment activity type from the Add Activity menu, and fixes how project benchmark values are resolved when rendering the Spidergram chart. No new data entry is required and no existing scores are affected.
| Area | Description | Type |
| Spidergram – Project Benchmarks | The Project Benchmark toggle is now active on the Analysis Results Spidergram for crop intervals enrolled in a project with configured benchmarks. | Enhancement |
| Activity List – Crop Failure | The Crop Failure / Abandonment activity type has been hidden from the Add Activity menu. | Enhancement |
| Spidergram – Benchmark Values | Fixed how project benchmark scaled values are resolved per state, replacing an outdated data path with the correct field. | Bug Fix |
1. Spidergram – Project Benchmark Comparison Now Available
The Fieldprint Spidergram on the Analysis Results page displays a radar chart of your indicator scores, with optional overlays allowing you to compare your performance against state and national benchmarks. In previous releases, a Project Benchmark comparison option was present in the code but was disabled.
In v5.0.4, the Project Benchmark comparison is now fully activated. When a crop interval is enrolled in a project that has benchmark data configured for the matching crop type and irrigation status, a Project Benchmark toggle will appear in the “Compare to others” panel alongside the existing State and National benchmark options.
How it works:
- The platform checks whether the crop interval’s project has a benchmark group that matches the crop type and whether the field is irrigated.
- If a matching benchmark group is found, the “Project Benchmark” toggle appears in the comparison panel.
- Enabling the toggle overlays the project’s benchmark values on the Spidergram so you can see how your performance compares to the project’s established benchmarks.
- If no matching project benchmark data exists for the crop interval, the toggle does not appear and the Spidergram displays as before.
2. Activity List – Crop Failure / Abandonment Hidden from Add Menu
When adding activities to a crop interval, the Add Activity menu previously displayed a “Crop Failure / Abandonment” option. This activity type has been hidden from the menu in v5.0.4.
The Crop Failure / Abandonment activity type remains in the platform’s data model and any previously saved crop failure activities are not affected. Hiding it from the add menu prevents new entries of this activity type while the associated data handling and indicator calculation logic is reviewed.
3. Spidergram – Project Benchmark Scaled Values Fixed
The Spidergram chart renders benchmark overlay lines by reading scaled benchmark values for each indicator. In previous releases, the SpiderGram component was reading project benchmark values from an outdated data path on the crop year object (“project.project_benchmarks”). This path was no longer populated correctly with the new project data structure introduced in v5.0.2, which meant benchmark lines were not rendering correctly even when benchmark data was present.
In v5.0.4, the benchmark value lookup has been corrected to read from the “projectBenchmarks” prop passed directly from the Analysis Results component, and the scaled value is now resolved against the field’s state using the “scaled_value[state]” field — ensuring the correct state-specific benchmark value is used for each indicator on the chart.
Version 5.0.3
Released: October 26th, 2025
Version 5.0.3 is a focused release that introduces a redesigned PDF report generation experience, removes the Rice Ratoon Crop data entry question following a methodology review, expands Tile Drainage options in the Field setup screen, removes the “Coming Soon” notices that were added in v5.0.2 (replacing them with functional pages), removes the option to include old or uncalculated indicators in project reports, and adds a “Not Applicable” option to the Phosphorus Multi-Year Application question. This release also includes supporting data updates for the cover crop termination operation list and the PMultiYearApp reference data.
| Area | Description | Type |
| Analysis Results – PDF | The PDF download button has been redesigned into a two-step Generate/Download workflow with inline error feedback. | Enhancement |
| Harvest Activity – Rice | The “Did you harvest a ratoon crop?” question has been removed from the Harvest activity for Rice crops. | Bug Fix |
| Tile Drainage | All five tile drainage system options are now shown, replacing the previous two-option filter. | Enhancement |
| Project Pages | “Coming Soon” banners removed from Project Dashboard, Project Details, Admin Dashboard, Admin Details, Reports, and Insights pages. | Enhancement |
| Project Reports | The option to include crop intervals with old or uncalculated indicators has been removed from the report generation form. | Enhancement |
| Phosphorus Multi-Year | A “Not Applicable” option (id: 0) has been added to the Phosphorus Multi-Year Application question. | Enhancement |
| Cover Crop Termination | The “Sprayer in inter-seeded crop” termination operation has been removed from the Cover Crop termination options list. | Bug Fix |
1. Analysis Results – Redesigned PDF Report Generation
In previous releases, the PDF download button on the Analysis Results page opened a static report link in a new browser tab. This approach did not provide feedback during report generation and could leave users uncertain whether the report was ready.
In v5.0.3, the PDF workflow has been replaced with a two-step Generate and Download experience:
- Step 1 – Generate: When no report has been generated yet for the current crop interval, the button displays “Generate PDF” with a PDF icon. Clicking the button triggers report generation in the background. The button enters a loading state while the report is being prepared.
- Step 2 – Download: Once the report is ready, the button label changes to “Download PDF,” the button turns green, and clicking it downloads the report file directly to your device.
- Error Handling: If the report generation fails, a clear error message is displayed inline below the button so users know to try again.
2. Harvest Activity – Rice Ratoon Crop Question Removed
When entering Harvest activity data for a Rice crop, users previously saw the question: “Did you harvest a ratoon crop?” with Yes/No radio button options. Following a methodology review, this question has been removed from the Harvest activity form in v5.0.3.
3. Tile Drainage – All System Options Now Available
The Tile Drainage section in the Field setup screen previously filtered the list of available tile drainage systems to show only two options: “Standard density” and “High Density.” The full reference list contains five options, including “No tile drainage system,” “Standard density with Drainage Water Management,” and “High Density with Drainage Water Management.”
In v5.0.3, the filter has been removed and all available tile drainage system options from the reference data are now displayed. However, please note that the reference data for this release has been updated to include only two options (Standard density and High Density), meaning the displayed list in this release still shows two choices. Future releases may expand this list as additional system types are validated.
Current Tile Drainage options available:
- Standard density
- High Density
4. Project Pages – “Coming Soon” Notices Removed
Version 5.0.2 introduced “Coming Soon” banners across several project-related pages to indicate they were under active development. In v5.0.3, these banners have been removed from the following pages, indicating that development on these sections is now complete or sufficiently mature for use:
- Project Dashboard
- Project Details
- Admin Dashboard
- Admin Details
- Reports
- Insights
5. Project Reports – Old Indicators Checkbox Removed
When generating a project report, the report form previously included a checkbox option: “Include crop intervals with old or uncalculated metrics.” This option has been removed in v5.0.3.
Project reports will now consistently include only crop intervals with current, valid indicator calculations. This change ensures that all report outputs reflect up-to-date indicator results and avoids confusion from including intervals whose scores may be based on outdated calculation methods.
6. Phosphorus Multi-Year Application – “Not Applicable” Option Added
The Nutrient Management section includes a question about Phosphorus Multi-Year Application strategy. Previously, users were required to select from a set of defined application strategies, with no way to indicate that multi-year phosphorus application was not applicable to their operation.
In v5.0.3, a “Not Applicable” option has been added as the first choice in the Phosphorus Multi-Year Application dropdown. This allows users who do not use multi-year phosphorus application strategies to accurately represent their management without selecting an inapplicable option.
7. Cover Crop Termination – “Sprayer in Inter-Seeded Crop” Option Removed
The Cover Crop Planting activity included a termination operation option labeled “Sprayer in inter-seeded crop” (internally “Sprayer, kill cover in growing crop”). This operation type was intended to represent herbicide application that terminates a cover crop while leaving an inter-seeded cash crop to continue growing.
Following a review of the operation’s implementation and data handling requirements, this option has been removed from the termination operations list in v5.0.3. Users who previously selected this termination method should review their Cover Crop activity data and select the most appropriate alternative termination operation.
Version 5.0.2
Released: October 18th, 2025
This release focuses on accuracy and consistency in how project and field data is displayed, introduces new report download options in the API Tool, updates terminology from “metric” to “indicator” throughout the platform, and adds a “Coming Soon” notice to the Project Management page currently under development. No changes to underlying data models or Fieldprint scores are introduced.
| Area | Description | Type |
| Project Dashboard | Field count and acreage totals now calculate correctly using unique field data per project. | Bug Fix |
| Field Dashboard | Field size now displays plantable acres (not total field size); soil texture label now resolves correctly from reference data. | Bug Fix |
| Project Details | Filter controls for adding fields to a project have been updated to use standard Material UI components for improved reliability. | Enhancement |
| Project Facts | Entered Acres and Crops Analyzed now calculate accurately from live project data. | Bug Fix |
| API Tool | Two new download formats added (HTML Drilldown, CSV Drilldown); Excel output renamed; download button redesigned. | Enhancement |
| Terminology | “Metric” updated to “Indicator” across all indicator descriptions, tabs, and help text throughout the platform. | Enhancement |
| Project Management | “Coming Soon” notice added to the Project Management page while it is under development. | Enhancement |
1. Project Dashboard – Accurate Field Count and Acreage Totals
The Project Dashboard table displays a summary row for each project, including the number of fields enrolled and the total entered acres. In v5.0.1, these values were sourced directly from pre-aggregated project fields, which could result in inflated counts when the same field appeared in multiple crop intervals.
In v5.0.2, both values are now calculated from unique field records within the project’s data. The platform deduplicates fields by farm name and field label, retaining only the most recent harvest year entry for each unique field. This ensures that the field count and acreage totals accurately reflect the actual number of distinct fields enrolled — not the number of crop interval entries.
2. Field Dashboard – Plantable Acres and Soil Texture Display Fixes
Two display issues were resolved in the Field Dashboard summary card:
Plantable Acres (previously showing total field size):
The field size displayed in the Field Dashboard card was previously sourced from the total field size value. This has been corrected to use plantable acres, which is the area of the field available for crop production. This change provides a more meaningful and accurate acreage figure for each field.
Soil Texture Label (previously showing raw ID):
The soil texture displayed in the Field Dashboard was previously resolved from a raw text value stored with the soil inputs, which could display incorrectly or be missing. It is now looked up by ID against the platform’s reference data, ensuring the human-readable texture name (e.g., “Clay Loam,” “Silt Loam”) always displays correctly.
3. Project Details – Improved Field Filter Controls
The Project Details page includes filter controls that allow users to narrow down the list of available field crop intervals when enrolling fields into a project. These filters (Field and Year) previously used legacy custom form components that could behave inconsistently across browsers.
In v5.0.2, the filter controls have been rebuilt using standard Material UI Select components, providing a more reliable and visually consistent experience. The filter dropdowns now render cleanly with a white background, clear borders, and proper z-index layering so they appear correctly above other page elements.
Additionally, the help text on this page has been updated to clarify that the field listing is pre-filtered to show only crop intervals not already associated with a project, and only crops relevant to the project’s focus crop.
4. Project Facts – Corrected Acres and Crops Analyzed
The Project Facts summary panel displays key statistics about a project, including the number of participating farmers, crop intervals, entered acres, and the list of crops analyzed. In v5.0.1, the Entered Acres value was not being calculated, and the Crops Analyzed list was pulled from a pre-stored project field that could become stale or inconsistent.
In v5.0.2, these values are now computed dynamically from the project’s live data:
- Entered Acres is now summed across all included project data records, providing an accurate total rounded to the nearest acre.
- Crops Analyzed is now derived directly from the crop IDs present in the project data, resolved against the platform’s crop reference list — ensuring it always reflects the crops actually recorded in the project.
- The label “Crop Years” has been renamed to “Crop Intervals” to align with updated platform terminology.
5. API Tool – New Download Formats and Improved Download Button
The API Tool, used to generate and download calculation outputs, has been enhanced with additional report formats and a refreshed download experience.
New Download Formats:
Two new output formats are now available in addition to the existing Excel output:
- HTML Drilldown — an interactive HTML report for viewing detailed calculation breakdowns in a browser.
- CSV Drilldown — a comma-separated values file for importing detailed results into spreadsheet or data analysis tools.
Renamed Output:
The existing Excel output has been renamed from “Excel Debug Output” to “Excel Inputs + Outputs” to more accurately describe its contents.
Improved Download Button:
The download link has been replaced with a styled button that clearly indicates the file format being downloaded (e.g., “Download XLSX File,” “Download HTML File,” “Download CSV File”). The button now includes a download icon for easy recognition.
6. Terminology Update – “Metric” Renamed to “Indicator”
Throughout the Fieldprint Platform, the term “metric” has been updated to “indicator” across all indicator descriptions, help text, analysis tabs, and report content. This terminology change aligns the platform with the broader Field to Market framework and industry-standard language for sustainability assessment.
Affected areas include:
- All eight indicator description panels (Land Use, Soil Conservation, Soil Carbon, Irrigation Water Use, Energy Use, Greenhouse Gas Emissions, Water Quality, and Biodiversity).
- The Analysis Results tab label, which previously read “About the Metric” and now reads “About the Indicator.”
- The section heading that previously read “Metrics” and now reads “Indicators.”
- Contextual help text throughout the analysis and reporting sections.
7. Project Management – “Coming Soon” Notice
The Project Management page, accessible to project administrators, now displays a prominent notice informing users that this page is currently under development. The notice reads:
| “This page is under development. Please check back for updates.” |
Version 5.0.1
Released: September 22nd, 2025
This update addresses two issues identified following the Version 5.0.0 launch: a bug in the user registration flow and a spelling correction on the Soil Test data entry screen. No new features or configuration changes are introduced in this release.
| Area | Description | Type |
| User Registration | Corrected a typographical error in the registration consent text that prevented the page from rendering correctly in some browsers. | Bug Fix |
| Soil Test – Phosphorus | Fixed incorrect spelling of “phosphorus” displayed in the Soil Test data entry section. | Bug Fix |
1. User Registration – Consent Text Correction
A typographical error was present in the Terms of Use consent statement on the User Registration page. The phrase “By continuing with registartion” contained a misspelling of the word “registration.” While the registration form itself remained functional for most users, this error could cause display or validation issues in certain browsers.
| Before (incorrect) “By continuing with registartion, you agree to the Terms of Use.” | After (corrected) “By continuing with registration, you agree to the Terms of Use.” |
2. Soil Test – Phosphorus Spelling Correction
Two instances of the word “phosphorus” were displayed incorrectly as “phosphorous” within the Soil Test data entry section of the Field dashboard. The correct scientific noun form is “phosphorus.” This was a display-only issue and did not affect any underlying data, calculations, or Fieldprint scores.
| Before (incorrect) “…what was the phosphorous level of the soil.” “Were any of the two following phosphorous drawdown strategies implemented?” | After (corrected) “…what was the phosphorus level of the soil.” “Were any of the two following phosphorus drawdown strategies implemented?” |