InventoryManager: Version History


This page seeks to document updates and enhancements to the InventoryManager product. In some cases the updates will have been automatically applied to current InventoryManager sites. This is the case where the update was implemented to fix a software defect, or where it could not be made as an optional (opt-in) upgrade. In many cases the upgrade will be available, but not yet implemented on a particular site. If there are upgrades in this list that have not been implemented on your site, please submit a request to have this functionality enabled for your site and include relevant information on an particular pages (e.g., specific map pages), user roles, or other details on how or where the functionality should be enabled.

Note that client-specific enhancements, such as modifications to compilation or reporting, may not be included in this list.

8/31/2022 Updates (Available on next site refresh)

  • Plot Layout Enhancements

    • Improved plot layout for complex geometries (multipart polygons with donut holes)

    • Added ability to read and apply target plot counts from a stand-level attribute

    • Added ability to configure default values and hidden parameters

7/25/2022 Updates (Available on next site refresh)

  • Tree and Log list improvements

    • Added ability to ‘insert’ trees into list, rather than only adding them to the end of the list

    • Automatically renumber higher numbered Tree_IDs when a tree is inserted or deleted

    • Autoload of Trees and Logs tables when using the < and > arrows in Query Results panel

    • Improved Trees and Logs tables behavior when Check Cruise trees present.

      • Tree and log records use blue font

      • Standard trees are read-only when any Check trees present on a plot to prevent accidental editing of Standard trees after Check Cruise conducted

      • Cruise_Type field autopopulates to ‘Standard’ when no Check trees present, ‘Check Cruise’ when any Check Cruise trees present

    • Improved handling of integers vs. decimal (only allow decimals when supported) when editing trees and logs to match Esri data model

6/3/2022 Updates (Available on next site refresh)

  • Plot Layout

    • Added admin configuration to enable pre-population, setting inputs to read-only, or hiding inputs. This configuration is a one-time configuration per map page and is only available to system administrators. Scenarios:

      • If your organization always requires a minimum of 5 plots per stand, can set Min Plots to 5 and make input read-only so users cannot change it

      • If your organization does not allow stand buffers can set this input to hidden

5/26/2022 Updates (Available on next site refresh)

  • Tree and Log list improvements

    • Added support for cascading delete of logs when the parent tree is deleted from the tree list below the map. This had been supported in MobileMap but not yet in InventoryManager.

    • Added support for updating the Tree_ID field on logs when their parent Tree is renumbered due to a lower number tree being deleted from the tree list below the map.

5/20/2022 Updates (Available on next site refresh)

  • Admin Menu

    • Added new toolbar for Site Admin role with radio buttons to display user interfaces for Rules, Check Rules, Related Domains.

5/16/2022 Updates (Available on next site refresh)

  • Plot Layout

    • Added Min Plots, Max Plots and Stand Buffer parameters

    • Added new plot density option - Plots per Acre

    • Added message below ‘Lay Out Plots’ button that reports number of plots created

5/16/2022 Updates (Available on next site refresh)

  • Map Filter

    • Added new map filter option that can be used to subset the features of any map layer based on a single value in a single field that utilizes a Coded Value Domain.

    • Scenarios

      • Configure for the Stands layer and the Status field (where values include Planned, Active, Cruised, Checked, Archived), then use to hide from the map all Stands that are not in the Planned status

      • Configure for Contractor field (where values the represent each of the contractors), then use to hide from the map all Stands not assigned to a particular contractor

3/19/2022 Updates (Available on next site refresh)

  • Export Inventory Data - added new Export function YEAR() that can be used to retrieve the year component of an Esri Date field. Useful when populating the 'Inv_Year' field for FVS. If the cruise date is recorded in the field, or even if the created_date is used, this will get just the year for use as Inv_Year.

12/10/2021 Updates (Available on next site refresh)

  • Export Inventory Data - Added the following new functions for export (similar to previous ADD and SUBRACT): MULTIPLY, DIVIDE, SQRT, POWER, MIN, MAX, YEAR, ABS, BASALAREA.

12/3/2021 Updates (Available on next site refresh)

  • Import Shapefile - Added new tool for importing Stand polygons from shapefile. Shapefile can be in any projection (requires *.prj file). Loads polygons into Source Stands layer to avoid required fields which are typically found in Stands layer but may not be present in Shapefile.

10/27/2021 Updates (Available on next site refresh)

  • Copy Tool - Added support for admin configuration of copy tool to support automated population of values in source or target feature.

    • Scenario:

      • When remeasuring a previously measured Stand, can configure tool to support copy of Stand from Stands layer to new Stand feature in same Stands layer while changing the Status of the previous stand from Cruised to Archived and setting the status of the new Stand to Planned.

10/14/2021 Updates (Available on next site refresh)

  • Plot Validation - Enhanced Plot Validation tool to add Unique_ID values to any plot that does not have them. These Plots should not have trees, since you shouldn't be able to create trees that don't have a Parent_ID value. This enhancement means that plots can be copied from a Shapefile or FGDB and the Plot Validation can create the Unique_ID while it is adding the Parent ID and Stand ID. When combined with the Copy Tool which will create Unique_ID for Stands when copying from Source Stands, it should eliminate the need to create Unique_ID values in Python for Plots that are created outside of InventoryManager.

  • InventoryManager - Stand Copy tool. Improved support for bulk copy. Now allows bulk copy even when a field is required and has multiple values within the set of source features. Previously that failed validation. Now it will pass validation so long as all inputs have a non-null value.

10/14/2021 Updates (Available on next site refresh)

  • Copy Tool - fixed bug that prevented polygons with holes from being copied using Copy Tool

4/30/2021 Updates (Available on next site refresh)

  • Shapefile Export - Added admin configurable export to include functions found in InventoryManager export, including LOOKUP and SUBTRACT.

4/30/2021 Updates (Available on next site refresh)

  • Export - Check cruise data and score calculation. Changed this option from a single checkbox to enable check cruise score calculation, to a new dropdown with 5 options:

    • Exclude - is the default and check cruise trees (and their column headers) are not included.

    • Include - will export standard trees and include the check cruise trees (and the relevant column headers) in the Excel export.

    • Prefer - this option will export one tree record (not both) for each tree, replacing the standard cruise tree with the values from the check cruise tree. Use this option when you prefer the check cruise trees over the standard trees for plots that have been check cruised.

    • Include and score - this option will include the check cruise trees in the Excel export and will calculate their score at the tree and plot level based on Check Rules found in the Check_Rules table.

    • Include, score and update - is selected, export will additionally send the plot level score, details and date at which score was updated to the Plot feature layer. The update option currently requires the following fields in the Plot layer 'Check_Score' data type ‘esriFieldTypeDouble’ that will store score 'Check_Details' data type ‘esriFieldTypeString’ with length of 1000-2000 (in case there are lots of details), 'Check_Score_Date' data type ‘esriFieldTypeDate – this will store the date in which the tool was last run. If any of these fields are missing or are named differently they will not be updated.