This document lists product fixes which have been made in InfoWorks WS Pro 2025.0.
See Known Issues for a list of limitations that we are aware of.
The fixes listed here are those that are viewed as likely to impact on users in an unexpected way, mainly changed simulation results, or differences in behaviour that might not be obvious.
Modifying selections
If an object on the map was selected and the associated control object, the control object would remain selected after unselecting the object on the map. This is fixed.
Grid report icons
Some grid reports (such as Hydrant Testing Report, CLA report) show a demand diagram icon in the top left. This is fixed.
Live Data
The live data graphing did not work properly when the pressure units were set to "cm". This is fixed.
Workspace and grids
When restoring grid views in a workspace, the grid position was sometimes not as expected. This is fixed.
WS Pro Exchange - row_objects_from_asset_id
The WS Pro Exchange method "row_objects_from_asset_id" did not filter by object type and also did not work with "_nodes" or "_links". This is fixed
WS Pro Exchange - odic_import_ex
The odic_import_ex command did not support flags over two character in length. The maximum length should be four characters. This is fixed.
WS Pro Exchange - crash
When using the single sign-on version of IExchange (WS Pro Exchange) and passing in the /WS command line option, WS Pro Exchange would exit. This is incorrect usage, the executable attempts to find a Thales license. This is fixed. An error message is now shown that this version can only be used with the /ADSK command line option
Help pages
The text in the "WS Pro Exchange for Autodesk" page was confusing. This is fixed.
Property pages
When the old style property pages were used in conjunction with the new style property tab, changes made in the old style property pages sometimes did not automatically update in the new style property tab. This is fixed.
UPC Scenario - in non-base scenarios
Regulators could not be added in non-base scenarios. This is fixed.
GMR Run context menu
The context menu on a GMR run was not allowing the results to be deleted. This is fixed.
Themes, particularly for Diagnostic Tables
If there was only a single value to theme, two bins would be created with the same value. This would result in an error message. This is fixed; only one bin is created now if there is only a single value. (Themes for diagnostic tables are particularly susceptible to this bug).
Open Data Export Centre for Control
The menu option "Open Data Export Centre (Control)" is available from "Network > Export" when no Control is open. This is fixed.
PST Operation graph and Result selector
If the Result selector is set to "standard reduction" for normal or water quality runs, the PST Operation Graph will fail to display for a simulation. An error will be reported stating that POWER results are not available. "Standard reduction" is the default for cloud runs so Cloud runs are particularly likely to generate this error. This is fixed. The workaround is to rerun with results selector set to full results.
Database context menu
A menu option "Copy IWLive workspace" was available on the database context menu for cloud databases. This option is not relevant for cloud databases and has been removed.
Live Data Configuration - ACE live data adaptor
When using the ACE live data adaptor, single floating point values could not be read. This is fixed.
Standalone databases
When opening a standalone database with the RootObjects.dat file missing as another database, WS Pro would crash. This is fixed.
Reservoir depth-volume table
The 'Reservoir depth volume data flag' field on wn_reservoir is not exposed to SQL, and not deliberately exposed to ODEC/ODIC. This is fixed.
Licensing for Remote Marshaller and Agent
If you are using a Remote Marshaller connection to run an engine, this will now use the remote Agent license configuration.
This means, for example, that the WS Pro UI can use an Autodesk Single Sign On while a remote engine could use a Thales license. This brings behavior in line with the more usual situation in which a Local Marshaller is used and the system invokes and engine on a remote Agent. In this situation it has always been the case that the remote Agent license settings are used for the engine.
Engine run on remote machine
When a run was invoked on a remote device the engine job could hang, incorrectly waiting for an impersonation token. This is fixed.
Offline Help being installed
Installations of InfoWorks WS Pro continued to include offline help. The offline help has been removed. Online help should be used.