Skip to main content

Version 9.1.219.5 (Support Release - 2 April 2026)

Communication Portal

Resolved Incorrect object null message (#147387)

Problem

  • The problem with the Dapper query binding to the record was fixed on master, but on release, this issue arose. Could nit-pick over the base on a large development change

 

Solution

  • Change from the init constructor to properties

 


Performance Management

Resolve edge case where modifying objectives after approval and adding and/or removing items causes item weights to not sum to 100 (#147159)

Problem

  • There are specific conditions where a user may modify previously approved objectives, and then proceed to add/remove perspectives, kpas and/or kpis. 
  • This manipulation after the fact messes with the previously calculated weights, and adding a new item results in the new weight calculated being either less than 0 or greater than 100 for the relevant item's KPA / Level2.
  • This is mostly applicable to contracts where the Weighted over Section setting is enabled.
  • This leads to a further edge case where, due to the mixture of high and low percentages on the weights, the calculated weighted averages of the KPAs end up as large decimal values with +10 precision, which all sum to 1 (100%). 
  • However, DB only permits decimals up to 4, and implicit truncation happens and causes the calculation to go out by 0.0002. 
  • This will create outliers during rating, where the item score may be out by a range of 0.001 - 0.01 when calculated.

 

Solution

  • When the level2weight in this instance is less than zero, make it zero. 
  • This is done only when the weighted over-section setting is in use, and can be set to zero since the approval function will redistribute the weights accordingly.
  • When the redistribution happens during the objectives approval, do a check to see if, from that perspective, the total kpa weight is not 100 (exceeds margin of error), and if so, redistribute the missing margin to the last kpa - > kpi item. 
  • Eg, Last KPI goes from weight 0.0745 to 0.0747. Low enough difference in score to not have a major effect.