Use this article when an expected numeric column is no longer recognized as numeric in results returned through WebReports, especially when every value in that column is NULL.
This guide covers WebReports results and VDM receiving results through a WebReports connection. It addresses the numeric-type issue fixed in version 2026.10.12.
Identify the affected result
Confirm whether all of the following apply:
- The affected result column is expected to have a numeric data type.
- Every returned value in that column is
NULL. - The results are returned through WebReports, either to a WebReports report or to VDM using a WebReports connection.
- The column loses its numeric type in those returned results.
For example, a numeric Amount column can contain only NULL values for the selected reporting period. Its values are missing, but the column should still retain its numeric type.
A column containing only missing values is not, by itself, evidence of this issue. Confirm that the data type is incorrect as well.
What changed in 2026.10.12
An issue could cause numeric columns containing only NULL values to lose their numeric type when returned through WebReports. The corresponding fixes are documented in the VDM 2026.10.12 release notes and WebReports 2026.10.12 release notes.
| Component | Fix included in 2026.10.12 |
|---|---|
| WebReports | Preserves numeric column types when all returned values are NULL (Bug 2011). |
| VDM receiving WebReports results | Preserves numeric column types when receiving all-NULL numeric columns through WebReports (Bug 2010). |
The fix preserves the column's data type. It does not replace NULL with zero or supply values missing from the source data.
Update the affected components
- Record the installed WebReports version and, if VDM receives the results, the installed VDM version.
- Have the WebReports administrator update the server to 2026.10.12 or a later release containing the fix.
- For a VDM-to-WebReports workflow, update VDM to 2026.10.12 or a later release containing the fix as well, so both components include their corresponding corrections.
- After the updates, reopen VDM when applicable and run the affected report again using the same connection and parameter values.
- Review the newly generated results and confirm that the expected numeric column retains its numeric type.
Use newly generated results for this check rather than relying only on a saved output from before the update.
For downloads and upgrade instructions, see VDM Version History Archive, WebReports Version History Archive, and Update WebReports to the Latest Version.
If the type is still incorrect
- Confirm the version on the WebReports server that actually processes the report and on the VDM workstation receiving the results.
- Ask the report author or database administrator to verify the expected data type of the query's output column.
- Record whether the issue occurs only when every returned value is NULL or also when the column contains numeric values.
- If you can compare the same query directly against its data source, use the same connection settings and parameters and note whether its output type differs from the WebReports result.
If the problem continues, contact BridgeWorks Support with the WebReports and VDM versions, report or View name, affected column name, expected and observed types, and steps to reproduce the issue. Include the exact error message if one appears.
Use sanitized examples. Do not include database passwords, connection-string credentials, API keys, or confidential report data.
Comments
0 comments
Please sign in to leave a comment.