Network Management
Breaking change in reports and widgets based on IPAM Events and IP History objects in IPAM 2026.1
This article discusses a breaking change in reports and widgets for IPAM Events and IP History objects, effective 2026.1.
First published date
Last published date
Overview
Starting from 2026.1, the username no longer appears in IPAM-related events.
If you migrate from 2025.4 or earlier to 2026.1 or later and use any reports or widgets based on IP History or IPAM Events objects, you need to adjust the underlying data source.
For reports, edit the report to change the data source. For widgets, recreate them using the new entities described below.
Product section
Cause
Data from IPAM_IPHistory and IPAM_Events tables are migrated to different tables beginning in 2026.1 so existing reports will need adjustments to continue working as expected.
Resolution
In the case of IPAM Events, events were migrated to global Event object type.
Needed changes:
-
Dynamic Query Builder
Change the data object from IPAM Event to Event and adjust properties in the conditions
-
Advanced Database Query
a. SWQL
If your SWQL query depends on the IPAM.Event entity, you need to change the query to use the Orion.Events entity instead.
b. SQL
If your SQL query depends on the IPAM_Events table, you need to change the query to use the Events table instead.
In the case of IP History objects and selection method:
-
Dynamic Query Builder
If you have any condition on the History Primary Key property, change it because this property no longer exists.
-
Advanced Database Query
a. SWQL
If your SWQL query includes the HistoryId column, update the query to omit this column.
b. SQL
Make the following changes to your query:
1. Omit the HistoryId column as it no longer exists.
2. Rename the Time column to Timestamp.
3. Rename the table from IPAM_IPHistory to IPAM_IPHistory_CS_cur.
Example of the affected widget; the affected report shows a similar error when opened.