Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

SQL query incorrect

Hello

I called the vendors dataset from sql into this report. For some reason the syntax or something is not correct. Can anyone help solve this?

Heres the sql statements

SELECT n.caption, ni.NodeID, ni.IPAddress , n.Location, n.Vendor
FROM Orion.Nodes n
join Orion.NodeIPAddresses ni ON n.nodeid=ni.nodeid
order by ni.nodeid asc

Heres the error within report writer

Columns with problems:

VENDOR - 'Vendor Icon (Watermark)' data presenter requires 'Orion.Vendors|Icon' field(s) to be present within the datasource

Find more posts tagged with

Accepted answers

All comments

Seashore

If you want to display the vendor icon in the report, you have to include that in the dataset, the query. Otherwise that info is not available to the report. Many times it's also good to include "detailsUrl" in the dataset. Like this:

SELECT 
    n.caption
    ,ni.NodeID
    ,ni.IPAddress
    ,n.Location
    ,n.Vendor

    ,n.VendorIcon
    ,n.DetailsUrl
FROM Orion.Nodes n
join Orion.NodeIPAddresses ni ON n.nodeid=ni.nodeid
order by ni.nodeid asc

StillGoing

The issue is that when you create a custom table that includes the Vendor column, the report wizard automatically assigns the Vendor Icon (Watermark) display setting to that column; e.g.

That display setting is dependent on the VendorIcon column being included in the SWQL query, as per the error; e.g.

SELECT n.caption, ni.NodeID, ni.IPAddress , n.Location, n.Vendor, n.Vendoricon

So you have two options; either hit the trash icon to remove the display setting, or go back to your SWQL query and include the missing column.

Hope that helps!