Sustainability & Risk / Energy

Upgrading to V.23.1

Users of pre-23.1 releases of Energy who wish to upgrade to V.23.1 and later, but do not want to perform a full database upgrade from a prior schema, will need to modify the primary key structure of three Energy tables before they can successfully run the Update Weather Model routines and access the V.23.1 weather model-related report(s).

The following schema changes were made in V.23.1:

• added vendor and vendor account id fields to energy_bl_svc_period and energy_chart_point tables
• added bill_id to energy_bl_svc_period, energy_chart_point, and weather_model tables
• changed the primary key for energy_bl_svc_period, energy_chart_point, and weather_model tables to a new, auto_number field.

As designed, the three affected tables do not contain source data, but only derived data that the application truncates and repopulates with each execution of the weather model calculation workflow rule. If system integrators have modified the structure or use of these tables, then they should take care to examine potential impacts of this change.

It is likely you will be able to continue using these tables without modifying code unless you begin taking advantage of the capability in V.23.1 to enter and process multiple bills per bill type per building per month. The former primary key structure in these tables did not permit that use case. Beginning with V.23.1, the auto-incremented primary key guarantees record uniqueness, while relaxing the constraint provided by the original key fields. Custom workflow rules or reports built on these tables should be examined to ensure the new structure is fully compatible.