Quantcast
Channel: NodeXL: Network Overview, Discovery and Exploration for Excel
Viewing all articles
Browse latest Browse all 4386

Created Unassigned: Feature request for Worksheet Import (of another open Excel file) [25304]

$
0
0
This is a feature enhancement request.

I understand that currently, worksheet import only supports edge data, specifically, 2 columns: Vertex1 & 2.

My request is that it support importing other columns which would be associated with the individual vertices on the Vertices worksheet.

So for example:

Input:
vertex1, vertex2, Vertex1Label, Vertex1LabelPosition, [optionally shape, size, colour, etc.], Vertex2Label, Vertex2Shape, [optionally size, colour, etc.], [__optional custom columns, to be used for filtering purposes__]

Output, Edges worksheet:
Vertex1, Vertex2

Output, Vertices worksheet:
Vertex, Label, LabelPosition, [optionally shape, size, colour, etc.], [optional custom columns]


My scenario is that I've a database of IT system information: servers, applications, database names, and mappings between them. At the moment, I need to:
- export 2 workbooks: 1 for edges with 2 colums, 1 for vertices with my various columns noted above,
- import the 1st workbook, which automatically creates values in the Vertices worksheet
- sort both the automatically generated and my generated vertices worksheets by the same columns/order
- manually copy/paste my additional columns into the far right side of the NodeXL Vertices worksheet (& validate the rows align (ie. that I didn't generate any duplicate vertices))
- manually copy/paste my label fields into NodeXL's columns for this,
- finally generate the diagram.

By having the import process use the proposed structure, much manual effort could be avoided.

Thanks,
Steven.

Viewing all articles
Browse latest Browse all 4386


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>