Resolved issues

Issue: Customer was seeing multiple request entries in the ABE queue for the same billing MRO request.

Resolution: An update to the ABE queue caused formula channels to be show up in the queue along with physical meter request. Code was enhanced to only show requests with meter ID in the queue.

Issue: The billing determinant aggregation on SQL Server platform was rounding after 16 decimal places causing in consistency in the expected total value.

Resolution: IEE has been enhanced to only calculate up to precision of 15 decimal places and truncate all digits after.

Issue: AMI Billing Export (ABE) Timeseries (TS) cancellations are not completing successfully. Operators should be able to cancel the time series request as long as the request is in exception state and not being accessed by another user or a bulk reprocessing task. Operators cannot cancel requests when at least one ABE item is in ready status and other ABE items for the TS request are in exception status. For example, the cancellations are failing when some of the entities, with matching correlation IDs, are in Export/Ready state.

Resolution: The ABE cancellation logic works in several steps:

* Cancel all TS requests entities with the same correlation ID and freeflowbycorrelationID request.

* Cancel requests in Ready/Export state.

* Cancel remaining requests with exceptions.

* Cleanup process will handle the Ready/Export requests.

Issue: Customers using ADE export may encounter an issue with the Export where additional channels are being skipped. The ADE export does not contain all the channels that should have been exported.

Resolution: Code was updated to allow linked channels to inherit the source channels export date allowing which will allowing ABE to find the data.

Issue: The ADE is not properly exporting via the Interval Push service (UtilitiesTimeSeriesERPItemBulkCreateRequest_Out) when using Dynamic Groups. This issue is specific to Oracle DBMS customers.

Resolution: A database index hint was added.

Issue: The High-Volume Data Push using AMI Data Export (ADE) and SAP Web Service Writer is not sending values with the proper decimals, which causes reading value discrepancies between IEE and SAP.

Resolution: The ADE logic was changed to increase the precision of the readings.

Issue: The Contingency Read Monitor appears to show incorrect status and the intervals imported. This scenario can happen when a contingency read request is created within a minute of a reading file being imported for the same meter/service point. Currently, if the contingency read request fails and the reading file import is successful, the overall status of the request will be "Success" which is not correct.

Resolution: The Contingency Read Monitor logic was changed to prioritize the contingency request status over the imported reading file status. In other words, the contingency read request failure is shown in the monitor when the contingency read request and imported reading file occur in the same minute.

Issue: Performance issue with formula constant window. The window was taking long time to with large system > 1 million SPCs, each with formula constant to display.

Resolution: The window has been updated to follow IEE standards and utilize the System Settings > NumberOfQueryResult parameter when returning large amounts of data. This change will limit the number of rows returned.

Issue: The meter program editor no longer allows, as it did in version 8.2, for of the Time Zone or Description to be edited if the program has been used.

Resolution: UI has been updated to allow for modification to the Time zone and description fields.

Issue: While importing a configuration with meter change, we copied all the properties, except the multipliers and the Monitoring Meter Program ID.

Resolution: The configuration import logic was enhanced to copy all properties, including the multipliers and Monitoring Meter Program ID.

Issue: Customers using formula channels may encounter an issue switching service point programs. This issue occurs when the prior channel had a formula defined but when switching the program, the formula is not defined. IEE was attempting to create a version with a blank formula.

Resolution: The system will now remove / ignore a formula version when blank.

Issue: The Configuration Export Task template is not saving changes made to the 'Since Last Export' checkbox. This setting determines the behavior of the task when it runs.

Resolution: The Configuration Export Task template UI was corrected so the checkbox settings are properly saved.

Issue: When issuing multiple two-way controls, for example a demand reset + contingency read, it may result in an exception stating, "Unexpected Exception: Cannot access a disposed object". This essentially means the first request succeeds and closes the connection, then the next command is not able to use the closed (i.e. disposed) connection.

Resolution: The retry logic was changed to keep the connection open until all requests have completed.

Issue: Customer running Oracle19c(19.11.0.0.210420)/Exadata/RAC may encounter issues connecting to the Oracle database.

Resolution: Updated Oracle Driver included in release.

Issue: When running reading purge by partition customer was encountering the following error ORA-01422: exact fetch returns more than requested number of rows This was due to duplicate "empty" status codes in the readingreadingstatus table. The issue was returning multiple rows being returned to a stored procedure when it only expected one, causing it to error.

Resolution: Code was enhanced to return one row and handle use case of multiple empty statuses in the readingreadingstatus

Issue: Customer had set the Effective start date and Effective end date to the same value. The system would error when retrieving readings due to the same ate being used.

Resolution: Update the logic to ignore records where the Effective start date = Effective end date.

Issue: The Validation Queue displays an Oracle 'column ambiguous' message after estimation. The complete message is: ORA-00918: column ambiguously defined ORA-06512: at "ITRONEE.VALIDATIONWORKQUEUE_UPDATE", line 600 ORA-06512: at line 1 Attempt to load collection with the following statement failed: ValidationWorkQueue_Update.

Resolution: The related stored procedure was corrected to prevent the ambiguous columns.

Issue: The IEE 10.2 External System Type Map tables in the UI have extra columns; the Category Value and External System columns should not be visible. Actual Result: After fix, Category Value and External System columns is not be visible.

Resolution: The Category Value and External System columns of External System Type Map tables are no longer visible.

Issue: The ReadingReadingStatus statusid 61 is incorrectly marked as VEESET1PV=0. This may cause issues for custom queries and IEE product SQL that depends on the ReadingReadingStatus table's VEESET1PV value. This issue was introduced in IEE 10.2 upgrade scripts.

Resolution: The IEE 10.3 upgrade scripts will correct ReadingReadingStatus statusid 61.

Issue: Riva meters event mapping added to support the following events: Temperature Threshold Exceeded->6J Extreme Temperature In-Service->6J Meter Inversion Detected on Startup->FP.

Resolution: Added mapping as standard product offering.

Issue: The Device Events configuration does not allow mapping multiple external category codes to the same device event, even across multiple external systems.

Resolution: The Device Events configuration was changed to allow mapping of the same external category codes to multiple events from different external systems.

Issue: The device event mapping script has duplicate entries, where the same external code is mapped twice to different IEE event code. The majority of duplicate mappings were found in OpenWay mapping script.

Resolution: The device event mapping script has been modified to correct the duplicate event mappings. Each external code is now mapped to one IEE event code. When the older event code is not used in any other mapping, the script also corrects existing event filters that refer to this older event code so that the filters refer to the new event code instead. Some of the older event codes are used in other mappings, in which case event filters that refer to them are not corrected. See: Correcting Duplicate Event Mappings.

Issue: On a SQL Server environment, if the database server is also used as application server, the database upgrade and the application installation must be performed separately. However, IEE SQL Server Upgrade Guide does not indicate this. Attempting to install database and application result in an error: SQL query failed: create database ItronEE on primary… This issue only affects SQL Server environments.

Resolution: The IEE Upgrade Guide has been updated to clarify this.

Issue: The Edit Interval Data 'Restore Earlier Version' logic is not working for multiple row selections.

Resolution: The 'Restore Earlier Version' logic has been enhanced to work with multiple row selections.

Issue: The Edit Log screen summary is not showing the correct date range of the edited usage. The issue occurs while a new reading alternate group is created, the system was still fetching the old alternate group to show on the Edit Logs screen.

Resolution: The Edit Log screen was changed to fetch the latest timestamp of the newest alternate key to display on Edit Log screen List.

Issue: The Scale Unscaled Estimations (SUE) process was not scaling properly when the selected readings crossed interval length changes. As a result, the resulting register read values were applied to the wrong configuration which, in turn produced invalid billing determinants.

Resolution: The SUE logic was modified to assign readings to correct service point.

Issue: When using the ISAIM adapter the incorrect user id / pw was being passed to IEE.

Resolution: The ISAIM adapter now throws and exception when the username / password are invalid.

Issue: The Meter Reading Synchronizer (MRS) encounters the following error when UTC output time zone is selected. The error message is: "Encountered an error message “Your task will not be scheduled. Parameter “OutputTimeZoneKey” is not associated with Task Type “MeterReadingSynchronizer” when we’re trying to run MRS, and UTC output time zone is selected. Note: The output time zone works when using the “Use service point Channel ID” addressing mode.

Resolution: Added a new Time Zone parameter on the MRS task template so the operator can specify the appropriate time zone.

Issue: The Meter Reading Synchronizer (MRS) exports readings with the wrong time zone, but only when there are multiple service points, each with different time zones, and the MRS task template setting for Time Zone is set to "Use Service Point". In this scenario, MRS exports all service points with the time zone of first service point.

Resolution: MRS logic was corrected to export readings using the proper time zone for each service point.

Issue: Task Runners are not picking up all tasks which slows performance of the task system. This issue only effects SQL Server DBMS customers.

Resolution: The Task Runner procedures were optimized so they pick up all waiting tasks.

Issue: The SQL Server version of the Reading Purge by Partition task was successfully completing, but the purge didn't actually purge the partitions.

Resolution: The SQL Server Reading Purge by Partition logic was corrected so the partitions will be purged.

Issue: When executing a Rate Analysis when no curtailment events are available in the specified time period, the Rate Analysis tool attempts to calculate each bill determinant value when the 'Use Bill Determinant Aggregator' box is not checked. The Rate Analysis should not calculate bill determinants in this scenario.

Resolution: The Rate Analysis was enhanced to log warnings and show messages in a pop-up when one or more billing determinants cannot be calculated. After the user closes the dialog, the Rate Analysis generates billing determinants where curtailment events are present.

Issue: SRI-E import failed when a register read for the same channel was included twice in the import: once as the EndRead in the interval reads block, and again as a separate individual register read block. This was because IDM used incorrect sorting, such that SRI-E split the EndRead block and the linked register block into separate Meter Reading Documents, resulting in an error.

Resolution: IDM sorting logic has been corrected. SRI-E splits the readings correctly and the import is now processed successfully.

Issue: The Reading XML Import Enhanced (SRI-E) was storing a single register read on the wrong service point channel. In this scenario, the register read aligned to the effective start of the service point because it was part of a meter swap. In this scenario, the existing logic could not determine the channel to store the readings.

Resolution: The SRI-E logic was improved to handle the single register read scenario, so the reading is stored on the proper channel.

Issue: Banked reading queue was displaying incorrect time due.

Resolution: The banked data timestamp was not being converted to UTC prior to storing. Code has been enhanced to store the date / time stamp in UTC so users will now see the date/time based on local time zone.

Issue: The standard Reading XML Import Enhanced task (SRI-E) import does not work with EndPointUOMID when Full Config is False. This scenario results in the following warning message: “Import Task had an unexpected error: Invalid ArrayList passed to filters it must be an ArrayList of Guids.”

Resolution: The SRI-E import logic was corrected to avoid this warning scenario.

Issue: When using reading xml Import (SRI-E) across a configuration change the import process is only considering the earlier version of data and discarding the latter version of data. The scenario can be seen when there is a validation set assigned, the reading XML end read tag is not present and when there are more than one Contiguous Interval Sets present for the same channel in the same file. Only the first contiguous interval set is considered and imported the rest are ignored.

Resolution: Reading XML import (SRI-E) has been enhanced to consider all the versions present in the file, for the same channel and with multiple contiguous interval sets with no end read tag present.

Issue: When exporting readings via the reading xml adapter with the "aggregate on export" option selected users may encounter the following error "Failed to Save readings: [Validation] Problem saving reading related information: readingSaveFailed:True, eventsSaveFailed=False, resolveFailed=False, code=1 -- SPC: EDP_00002116_H:11050 , Daterange:2021-04-01T00:00:00+02:00--2021-04-01T00:00:00+02:00". This was caused by missing register readings for the time period of aggregation.

Resolution: The code now verifies for missing data and logs proper message in task monitor prior to attempting to aggregate and export data.

Issue: The standard Reading XML Import Enhanced (SRI-E) is throwing this error: Import Task had an unexpected error: Object reference not set to an instance of an object. This occurs when the SRI-E task is processing a non-Service Mode configuration when the Service Mode Import task template is True.

Resolution: The SRI-E task was enhanced to detect this scenario and process it as a non-Service Mode configuration, regardless of the Service Mode Import task template setting.

Issue: During a meter swap scenario, the logic did not properly determine the channel to store the last read. This prevents the UOM conversion.

Resolution: The logic was changed to store the last read on the old meter, which allows the UOM conversion to work.

Issue: Register reads that are imported with date-time matching the effective start time are banked in error.

Resolution: The import logic was changed to determine the proper channel, which allows the register read to be save, not banked.

Issue: The MV90 Mainframe Export is not formatting the file correctly if one of the channels has no channel statuses but the other channels do.

Resolution: The MV90 Mainframe Export logic has been corrected to properly format the file in this situation.

Issue: The MV90 Spreadsheet export encountered an unexpected exception when exporting MV90 Spreadsheet task with meter group. Exporting using a service point group works as expected. The error message details are shown below:

2022-07-15 11:14:38,491 (null) DEBUG [taskservice2] Itron.EE.Facade.ImportExport.Adapter.MV90Spreadsheet.MV90SpreadsheetExportAdapter:0 InitializeIntervalRow TaskID: 253800 - IntializingInitializing Interval Row:8969

2022-07-15 11:14:38,506 1000 ERROR [taskservice2] Itron.EE.Common.TaskManagement.Manager.TaskAdapterBase:0 QueryRunTask String[] {Unexpected Exception: Object reference not set to an instance of an object. - Unexpected exception cause file processing to die - file: C:\Users\johndoe\Desktop\test_group-2.csv, Object reference not set to an instance of an object.}

Resolution: The MV90 Spreadsheet export task, for meter groups, now checks and removes null characters.

Issue: The Enhanced XML Import task (SRI-E) fails with the following message: "Unexpected System Exception:#OverflowException - Value was either too large or too small for a Decimal. received - contact Application manager. This issue occurs when there is meter program change for previous register read and current register read for RollOverCheck and DeltaLowLimit validation rules.

Resolution: Since we cannot calculate usage due to the meter program change, we skip the RollOverCheck and DeltaLowLimit validation rules.

Issue: Meter Reading Detail report does not properly align registers with Time based UOMs correctly. As a result, the Minutes on Battery is not showing properly.

Resolution: The Meter Reading Detail report has been corrected so the sub report aligns properly.

Issue: Service Mode interrogation scheduled via data driven schedule get stuck in submitted state when meters are set with an inactive state / status.

Resolution: The system now avoids creating interrogation task for disconnected / inactive meters in data-driven schedule.

Issue: The DB_RG.exe file was not included in the Service Mode installer.

Resolution: The DB_RG.exe file has been added to the Service Mode installer.

Issue: Service Mode customers utilizing daisy chaining may encounter an error in the SQL Server Database and failure to interrogate the meters due to duplicate entries.

Resolution: Code has been updated to only add the current version of recorders to slave list avoid duplicate entries.

Issue: The Send Settlements submissions do not properly calculate DST start and end dates when the task is configured when using offsets in minutes. This issue does not affect manual DST-day submissions; they are working properly.

Resolution: The Send Settlements task's logic was corrected to calculate start and end dates, regardless of the offset types (Days, Hours, or Minutes).

Issue: Code table setup screen was displaying in correct information in the tasktype, taskrunnertype and taskrunnertypetasktype columns.

Resolution: Screen has been updated.

Issue: When making a UDA searchable, a critical error is thrown in UI. This happened because the logic was not updating the FlatConfigSettlement table.

Resolution: The searchable UDA logic was corrected to properly update the FlatConfigSettlement table.

Issue: When reviewing SAP Billing Export task in the task monitor customer received the following error: Error populating log data Index was outside the bounds of the arrange. The tasks ends in a Warning state, and no warning or error logged in messagelog.

Resolution: The issue was a limitation in the code which did not allow for more then 11 pipe "|" symbols to be sent. Code has been updated to support a scenario where more the 11 pipe "|" delimiters are sent.

Issue: The Aggregation task was incorrectly completing with a warning status. Since the task went into warning this was neglected and was not noticed until data was not exported. This requires extra effort to manually find tasks that actually failed.

Resolution: The aggregation task was enhanced to log aggregation failures and complete with a failed status.

Issue: The Task Monitor column widths are not saved between sessions, so the operators need to adjust column widths each time they open the Task Monitor.

Resolution: The Task Monitor logic now saves the column width changes between sessions.

Issue: The following new UOM codes are needed:

KW_DEL_CUM_RATE_A, KW_DEL_CUM_RATE_B, KW_DEL_CUM_RATE_C

W_REC_CUM_RATE_A, W_REC_CUM_RATE_B, W_REC_CUM_RATE_C

KW_REC_CUM_RATE_A, KW_REC_CUM_RATE_B, KW_REC_CUM_RATE_C

W_ELE_DEL_CUM, W_ELE_REC_CUM

KW_DEL_CUM, KW_REC_CUM

VAR_ELE_REC_MAX

Resolution: The Add_UOMs script now includes the new UOM codes. Refer to UOM Update Script for a complete list of UOM IDs.

Issue: Gas meter reads that are converted from CF to DCF are not being stored correctly.

Resolution: Enhanced the Unit table so the conversion logic so it uses higher precision.

Issue: Units of Measure (UOM) have been added.

Resolution: Added 2 new UOMs: KWH_I3_1, KWH_I4_1.

Issue: When readings arrive for an hour or less in workbin0, the reading import fails because it could not determine the DST transition.

Resolution: The SRI-E import logic was improved to check for this condition of DST transitioning.