Maven Release 2026.3.75.6260

Version: 2026.2.75.6260
Release Date:  April 20, 2026
Download Link: Download Now

  • Added improvement details to the subject’s improvement section.
  • Added a flow through checkbox. When enabled, changes to an approach’s values, lake land/improvement indication and indicated value are automatically propagated to the allocation. This eliminates the need to manually click “Apply” after every edit, streamlining the workflow for users who are actively adjusting approach values.

    Only one approach can be in flow-through mode at a time. Enabling flow-through on one approach automatically disables it on all others. When flow-through is active, allocation fields become read-only to prevent conflicting manual edits. For appraisals with a single approach, flow-through is enabled by default. The manual “Apply” button remains available and clears all flow-through flags when used.

    Allocation validation has been separated from other validation checks and is now non-blocking. Previously, any allocation discrepancy would prevent users from proceeding to preview. Now, large discrepancies (1% or more of the opinion of value) display a confirmation popup, allowing the user to choose whether to continue. Small discrepancies (less than 1%) show an informational message but do not block navigation. All other validation errors continue to block as before.

  • Updated the Quantarium approach tab to allow users to set indication or allocation per improvement and land, and pull in local sales to provide justification for the values.

    (example Quantarium approach with improvement and land row indications and allocations)

    Now each improvement and land row can be marked as “Valued Above”. This indicates that it is included in the indication from Quantarium (the “Primary Indication”). 

    When valued above improvements and land rows can have an allocation set. All allocations should add up to the primary indication (a warning will display if they do not). 

    Improvements and land rows that are not valued above allow the user to set the indication, which will be added to the primary indication to get the total indication. 

    Improvements and land rows both allow users to pull in sales from the Maven database to provide justification for the indication/allocation. Adding sales is similar to the Land Mix approach in that each sale added will add comparisons for all matching land rows or improvements. While sales added to the land match all land rows, and sales added to improvements match to all improvements, improvements and land are separate. Each comparison can be individually removed without affecting other comparisons. 

    All of the new fields are available in the report data. The land comparisons are accessible as a collection on Approach Land using the new ApproachLandComparisons property. The improvement are accessible as a collection on the Approach Improvement using the ApproachImprovementComparison property. The allocated values and Valued Above value are accessible on their respective objects as well (Approach Land and Approach Improvement).

  • Updated the Quantarium approach so that users can add sale comparisons using sales from the Maven database.


    These comps are treated the same as imported comps for the calculated indication. Because they are not known to Quantarium all adjustments must be manually entered. However, local sales are not removed during a reimport, but the adjustments will be cleared.

  • Improved handling for importing unimproved Quantarium valuations and split out default SCA units on the model into improved and unimproved.

    The import process now checks if the subject has a GLA. If so, the subject will use the improved unit. If not, then the subject will use the unimproved unit and the site area for the effective units. All imported sale comparisons base their SCA unit on the subject and effective on the subject’s SCA unit. This allows users to change the subjects SCA units and effective size as desired, and reimport to get sale comparisons with matching units.
  • Fixed issue for SQL Server 2016, 2017, and 2019 known bug where the error message “Microsoft.Data.SqlClient.SqlException (0x80131904): Invalid object name ‘ ‘. Caution: Changing any part of an object name could break scripts and stored procedures.” When running a migration.
  • Fixed issue where save errors would occur on a subject improvement when deleting a house detail or image.
  • Fixed issue where comments on a Population RoV were not being saved correctly.
  • Fixed issue with the quartile population RoV approach where the improvement box plot was not populating correctly.
  • The procedure for generating report PDFs has been moved from a separate process to being included in the Maven executable. This should not change anything.
  • Updated the post scripts so that DataLog can post sales with timber data to the enterprise database, and also updated the GetSaleXML to include timber data for export.