July 2026 SKY Release Notes

  • SV-1794 / AP Approval Rules – Approval Rules can now be set up so Approvers can be applied to AP Bills.
    • Why – This allows Approvers to be applied to AP Bills based on Conditions such as the Vendor, GL Account, and Bill Amounts.
    • When/Where – Rules are set up in Agvance SKY Admin under Vendor.
    • Action Needed – Once Rules are set up, the Apply Approver Rules button must be selected when adding a Bill to pull in the applicable Approvers.
  • AN-3786 / Energy Force Transfer Report Dashboard – A new Energy Force Transfer Report dashboard is now available in Agvance SKY Analytics.
    • Why – This dashboard assists in reconciling inventory transfers between Energy Force and Agvance.
    • When/Where – This dashboard is found under Energy for those using Energy Force.
    • Action Needed – No action required.
  • AN-3773 / Credit Analysis Dashboard – A new Credit Analysis dashboard is now available in Agvance SKY Analytics.
    • Why – This dashboard provides a clear view of Customer credit exposure, helping to quickly identify high-risk accounts and prioritize collection or credit decisions.
    • When/Where – This dashboard is found under Customer in Agvance SKY Analytics.
    • Action Needed – No action required.
  • AN-3222 / Energy Contract Comparison Dashboard – A new Energy Contract Comparison dashboard is now available.
    • Why – This dashboard compares Agvance Bookings to Energy Force Contracts to confirm systems are aligned.
    • When/Where – This dashboard is found under Energy for those using Energy Force.
    • Action Needed – No action required.
  • SKYR-1316 / Canadian Provinces and Zip Codes – Ability to view and choose the Province (State) from a drop down menu and manually enter the alpha-numeric Postal Code (zip code) in Agvance SKY Energy. 
    • Why –  The ability to choose a Canadian Province in the State drop down menu and a 7 digit Alpha-numeric Postal (Zip) Code in Agvance SKY Energy was not available.
    • When / Where – Energy / Tanks
    • Action Needed – No action required.

Version 6.13

Web

  • HW-6167 / Cotton Harvest Event – Units display as expected when changing Yield Units from pounds per acre (lb/ac) to bails per acre (bl/ac) during an import of a Cotton Harvest Event.
    • Why – The Yield Unit and Lint % unit changes were not being saved.
    • When/Where – Harvest Events are imported under the Import tab.
    • Action Needed – No action required.
  • HW-12524 / Import Boundary Column Selection – A hard-coded Import Template called Column Selection (*.shp) of the Field Boundary Data Type was added to the Import Wizard.
    • Why – This upholds consistency and standardization on the Field Boundary Data Type.
    • When/Where – Field Boundaries are uploaded under the Import tab.
    • Action Needed – No action required.
  • HW-12677 / Field Setup Agvance Integration – Adding a Field works as expected.
    • Why – Adding a Field originally resulted in an error.
    • When/Where – Fields are added under the Fields tab by selecting the Ellipsis for a Customer then choosing Add New Field.
    • Action Needed – No action required.
  • HW-12680 / Export Event Summary – The Yield Avg for Cotton now displays as expected.
    • Why – The Yield Avg for Cotton was not displayed for manual and imported Events when using the Export Event Summary feature.
    • When/Where – The Export Event Summary option is available under the top context menu of the Events tab.
    • Action Needed – Access to the Export Event Summary feature must first be enabled for the User Role.

Mobile

  • HW-10302 / Soil Sampling – Soil Sampling Events surface as expected.
    • Why – This would result in partial surfaces on some Sampling Events.
    • When/Where – Sampling Events are added under the Events tab.
    • Action Needed – No action required.
  • HW-12684 / Imported Event and Default Test Weight – Importing Harvest Events not covering the entire Field and importing Planting Events work as expected. This now uses the Test Weight value of the User's Crop preference or defaults to the AgBytes value when not present.
    • Why – Importing Harvest and Planting Events was resulting in unnecessary prompts.
    • When/Where – Events are imported under the Import tab.
    • Action Needed – No action required.

Version 6.12

Web

  • HW-10070 / Customer Setup Agvance Integration – Adding and editing Fields works as expected for connected Customers.
    • Why – This was originally resulting in error messages.
    • When/Where – Fields can be added or edited on the Fields tab in SKY Mapping.
    • Action Needed – No action required.
  • HW-11825 / Recs Report Application – The Recs Report - Application and SKY Recs Report - Application reports now ignore the Sample Sites report parameter when Fields do not have a Sampling Event.
    • Why – Running these reports was resulting in error messages.
    • When/Where – The reports can be run in the Reports area of SKY Mapping.
    • Action Needed – No action required.
  • HW-12480 / Email Import Sampling – The Sampling Email import of Modus results with the same name import as expected.
    • Why – Modus files with the same name were not appearing after being sent from the lab.
    • When/Where – Modus files are imported under the Import tab.
    • Action Needed – No action required.
  • HW-12481 / Defined Legend for Harvest Events – A new User Role, Defined Legend, was added to the Setup area and includes two new menu options (Record Grid which navigates to a typical setup grid and Add/Edit Page which navigates to the Defined Legend add/edit page). Additionally, a Layer Type drop-down (Application, Harvest, Planting, Application Rec, Planting Recs), an Attribute drop-down (disabled until a Layer Type is selected), a Crop/Crop Purpose drop-down (Harvest, Planting, Planting Recs), and a Product drop-down for Application and Application Recs. A Color Ramp drop-down is also available that mirrors Edit Layer Properties and gives the ability to choose the number of classes. Saving the Defined Legends adds a Defined Legend Classification method option for the given Location and Attribute.
    • Why – This implements Defined Legends for Imported Harvest Events.
    • When/Where – The new menu options are available under the Setup menu.
    • Action Needed – The User logged in must have the Defined Legend User Role.
  • HW-12593 / Import EC Data – The EC Data Merge option completes EC Data merges and surfaces as expected.
    • Why – An error was occurring when merging EC Data.
    • When/Where – EC Data is imported under the Import tab.
    • Action Needed – No action required.

Mobile

  • HW-12240 / Field Setup – Recording an average accuracy value (in inches) was implemented for all GPS tracked boundaries when adding/editing Fields. Selecting and holding the header of the Field panel displays the User who last modified the boundary along with a timestamp. If the last modified boundary was GPS-tracked, a Tracked Accuracy value is displayed with two decimal places.
    • Why – This indicates the accuracy of added/edited boundaries.
    • When/Where – This is seen when adding/editing GPS-tracked Fields.
    • Action Needed – No action required.
  • HW-12658 / Manual Events – Manual Events load as expected.
    • Why – This was originally resulting in an error.
    • Action Needed – No action required.
  • SV-1849 / Import Warehouse Ticket into Purchase Receipt – Warehouse Tickets can now be imported into Purchase Receipts in Agvance SKY Product.
    • Why – This makes importing a Warehouse Ticket into a Purchase Receipt more efficient.
    • When/Where – An Import Warehouse Ticket button is available in the Products section when adding a Purchase Receipt.
    • Action Needed – No action required.
  • SV-2615 / Import EDN into Purchase Receipt – EDNs can now be imported into Purchase Receipts in Agvance SKY Product.
    • Why – This makes importing an EDN into a Purchase Receipt more efficient.
    • When/Where – An Import EDN button is available in the Products section when adding a Purchase Receipt.
    • Action Needed – Vendors must first be set up in B2B for EDNs.