Our company uses something called MRTG, which displays graphs of our customers bandwidth usage. Now I am getting the link from an External Data source(mysql) table in a field called "linkurl".

So as our employees page through our customers, they can go to a tab called MRTG which displays the graph using the webviewer. My problem is Each of our customers have 2 graphs assigned to them (in other words there are 2 related records for "linkurl" per customer and the webviewer is only displaying 1 of them. How can I show both related records in separate webviewers? If I just simply add 2 viewers it just displays the 1st record twice (or displays the same graph twice)

Any help would be appreciated.

Thanks

Well you can grab the second related record's data using GetNthRecord or List with ValueCount but this seems limiting as what happens when you have more than 2 records in the future? It doesnt really make it scalable does it?

If you want to compensate for it, you can use a portal to display the related child records and then use a button on the portal to set a global field to which related record's data you want to see in the web viewer.

A web viewer displays what you tell it to; and you want each web viewer to display different information. Therefore your web viewer setup for WV1 differs from the setup for WV2 in exactly what way?

I'm using values from an External Data source to supply the web address for the webviewer. The field is called linkurl. Each customer has 2 links (primary and secondary). Now essentially the webviewer is doing what its suppose to do. I specify that field ->(bandwidth::linkurl) under the webviewer setup. So its showing one of the graphs. How would I be able to setup 2 webviewers showing the separate links? It'd be easy enough to do if 1 field was called linkurl1 and the other linkurl2, but its not setup this way.

Edited March 17, 201015 yr by Guest

You're not providing enough information. You need to supply the web viewers with different sets of data. For the moment, the web viewer has nothing to do with the problem. What relation, or field name, or calculation, will separate the two different data sets? It's your data - we don't know what it looks like.