multiple detailsURL links in a custom resource table?

From what I've gathered here on thwack, the "Details Page Link" display setting is a largely MIS-understood concept and that there is some behind the scenes work required when crafting your data source. (all of which from what I can tell is undocumented) Other thwackers (or geniuses) have figured out the behind the scenes required and I've followed their suggestions with some limited success.

Question, you can specify that multiple columns have a "Details Page Link" display setting. Has anyone successfully gotten this to work? My intention is to allow the user to click on the node name OR node interface to drill into the respective details page. However since there is no way to tell solarwinds which column to use for the "Details Page Link" my suspicion is that you can only have one, and that any subsequent columns where you turn on the "Details Page Link" causes your custom table query to roll over and die with the following message:

Find more posts tagged with

custom table resource

detailsurl

custom resource

Accepted answers

njoylif

yes, yes...you can do this, but you can do it without that specific setting when using custom sql....not sure about swql but I suspect yes as well.

I think you can only use detailsURL when using single object type like Nodes report or blah..blah..

to do this in SQL you need to build the link..as below using detailsURL (only if one link per row needed and want to use detailsURL):

	CONCAT('http://orion......com/Orion/APM/ApplicationDetails.aspx?NetObject=AA:',a.ID) as detailsURL
	, CONCAT('/Orion/APM/ApplicationDetails.aspx?NetObject=AA:',cp.applicationID) as DetailsURL

now, if you need multiple ones or want to go the complete manual route (include the text that will display for the link)...

CONCAT('<a href=''http://orion.......com/Orion/NetPerfMon/ActiveAlertDetails.aspx?NetObject=AAT:',ah.alertobjectID,'''>',ah.AlertActiveID,'</a>') as AlertActiveID

NOTE the object type...this is for an active alert.

CONCAT('<a href=''http://orion.....com/Orion/APM/ApplicationDetails.aspx?NetObject=AA:',id,'''>',id,'</a>') as id

NOTE this will display the ID of the application and allow you to click on it to go to the details page of that application.

All comments

njoylif

yes, yes...you can do this, but you can do it without that specific setting when using custom sql....not sure about swql but I suspect yes as well.

I think you can only use detailsURL when using single object type like Nodes report or blah..blah..

to do this in SQL you need to build the link..as below using detailsURL (only if one link per row needed and want to use detailsURL):

	CONCAT('http://orion......com/Orion/APM/ApplicationDetails.aspx?NetObject=AA:',a.ID) as detailsURL
	, CONCAT('/Orion/APM/ApplicationDetails.aspx?NetObject=AA:',cp.applicationID) as DetailsURL

now, if you need multiple ones or want to go the complete manual route (include the text that will display for the link)...

CONCAT('<a href=''http://orion.......com/Orion/NetPerfMon/ActiveAlertDetails.aspx?NetObject=AAT:',ah.alertobjectID,'''>',ah.AlertActiveID,'</a>') as AlertActiveID

NOTE the object type...this is for an active alert.

CONCAT('<a href=''http://orion.....com/Orion/APM/ApplicationDetails.aspx?NetObject=AA:',id,'''>',id,'</a>') as id

NOTE this will display the ID of the application and allow you to click on it to go to the details page of that application.

mesverrum

In cases like this where if you are going to go through all the trouble to do the data source completely in sql I feel like you are better served by just creating the whole table as a Custom Query in SWQL. They are a little bit faster to manipulate and set up than the Custom Table resource, and don't have the added complexity of having little quirky behaviors that you have to work around. They mostly just work right away or don't and the SWQL studio tool makes it really easy to test/build them. Plus you get the option to use searches.

Big plus side is just about every kind of object in swql tables has a detailsurl column by default so you dont have to look up exactly how build all those types of links manually. To get what I can see from the screen snip you could do something like:

select n.Caption,n.detailsurl as [_linkfor_Caption],'/Orion/images/StatusIcons/Small-' + n.StatusIcon AS [_IconFor_Caption],n.ip_address as [IP],n.detailsurl as[_linkfor_IP],i.Name as [Interface],i.detailsurl as [_linkfor_Interface],'/Orion/images/StatusIcons/Small-' + i.OperStatusLED AS [_IconFor_Interface]from orion.nodes njoin orion.npm.interfaces i on i.nodeid=n.nodeid

It will come out looking roughly like this (I'm using the NPM 12 RC right now so mine looks a little difference than it would in 11.5)

Add in whatever other columns you were pulling and whatever filters you needed as where conditions

-Marc Netterfield

Loop1 Systems: SolarWinds Training and Professional Services

LinkedIN: Loop1 Systems
Facebook: Loop1 Systems
Twitter: @Loop1Systems

ryan.davis26

Thank you guys both, I ended up going with what njoylif suggested as I'm not quite versed in SWQL just yet, I've tried once or twice before but can't seem to get it to work, not sure what I'm doing wrong. At any rate, I was able to come up with something I'm pretty happy with and I think our operations guys will really like it. Each interface or node is hoverable and of course clickable:

njoylif

Glad to be able to help. mesverrum and I chat offline and they brought up a great point about the links....

If you are going to use the report/resource within the website only, it is best practice to use a relative link like <a href="Orion/SummaryView.aspx?ViewID=2">.

I do this when it is not a report that will be mailed out. His example uses that type of link.

have fun!