microsoft/powerbi-visuals-networknavigator

Network Navigator custom visual for PowerBI

NetworkNavigator

Network Navigator lets you explore node-link data by panning over and zooming into a force-directed node layout (which can be precomputed or animated live). From an initial overview of all nodes, you can use simple text search to enlarge matching nodes in ways that guide subsequent navigation. Network nodes can also be color-coded based on additional attributes of the dataset and filtered by linked visuals.

This visual is experimental and not actively being developed, only major issues will be addressed.

Usage

• Fork this repo
• Install node.js 16+
• Install yarn
• Run yarn on the project directory, which will install all the dependencies
• Run yarn package which compile the network-navigator, and network-navigator-powerbi packages.
  • Compiling network-navigator-powerbi will also create a .pbiviz file in the packages/network-navigator/powerbi/dist directory, which can be imported directly in Power BI

Test

• Run yarn test

Lint

• Run yarn lint

powerbi-visuals-networknavigator's Issues

Add Node Scaling

We have Max & Min sizes, but if all the numbers are very large for the nodes, no information can be gleaned. Provide min and max scales, so that the numbers can be scaled for a users dataset.

Fix READMEs

Node graph does not display Targets connected to "blank" source

One of my use cases is to display Targets which have no assigned source. I've tried selected "Show items with no data" but that does not work.

It needs to be able to display Targets connected to "blank". The other visual I use is the Microsoft's Force Directed Graph and it shows the blank labels, but doesn't do other features I need.

Add ability to provide a "Node Label" column

This will allow for users to have a different label than the node name.

Generate node colors from report palette

I'm a big fan of visuals that allow us to pass color codes - thank you. However for a quick solution most users would prefer to use a categorical field (e.g. country code) which would generate the usual progression of colors following the report palette.

Limit in displayed nodes?

From my early tests it seems that only a limited amount of nodes are drawn in the visualization. Is there a hard limit in the number of items that can be displayed?
Some context;
I would like to display about 80k items in the framework of data migration.
My idea is to show sources tables, destination tables and the scripts that link them -that amounts to 80k nodes. I cannot simplify the data -I need the full data to cluster the tables / scripts to orchestrate a migration.
Can someone point me to a workaround?

Add tooltip support

Optionally add a "tooltip" column to customize what to show in the tooltip

Yarn test error

Hello,

I am trying to compile the repo but I'm facing errors upon running the "yarn test" command.
npm version : 5.0.3
Node.js version : 8.1.1

Here is what it says (I have attached screenshots of the error lines you see below at the bottom of the post)

@essex/network-navigator: webpack: bundle is now VALID. @essex/network-navigator: 19 06 2017 11:38:20.733:INFO [PhantomJS 2.1.1 (Windows 8 0.0.0)]: Connected on socket /#Vzhv8M2Q2dvoMwvxAAAA with id 57074436 PhantomJS 2.1.1 (Windows 8 0.0.0): Executed 22 of 22 SUCCESS (0.211 secs / 0.283 secs) @essex/network-navigator: @essex/network-navigator: > @essex/[email protected] docs C:\Users\vchau\Desktop\PowerBI_Valentin\PowerBI-visuals-NetworkNavigator-develop\packages\network-navigator @essex/network-navigator: > typedoc --out docs --ignoreCompilerErrors ./ --externalPattern **/node_modules/**/*.* --exclude **/src/**/*.spec.ts > /dev/null || exit 1 @essex/network-navigator: @essex/network-navigator: Le chemin d'acc�s sp�cifi� est introuvable. @essex/network-navigator: npm ERR! code ELIFECYCLE @essex/network-navigator: npm ERR! errno 1 @essex/network-navigator: npm ERR! @essex/[email protected] docs: typedoc --out docs --ignoreCompilerErrors ./ --externalPattern /node_modules//. --exclude /src//*.spec.ts > /dev/null || exit 1@essex/network-navigator: npm ERR! Exit status 1 @essex/network-navigator: npm ERR! @essex/network-navigator: npm ERR! Failed at the @essex/[email protected] docs script. @essex/network-navigator: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. @essex/network-navigator: @essex/network-navigator: npm ERR! A complete log of this run can be found in: @essex/network-navigator: npm ERR! C:\Users\vchau\AppData\Roaming\npm-cache\_logs\2017-06-19T09_38_22_391Z-debug.log @essex/network-navigator: ERROR: "docs" exited with 1. @essex/network-navigator: npm ERR! code ELIFECYCLE @essex/network-navigator: npm ERR! errno 1 @essex/network-navigator: npm ERR! @essex/[email protected] verify:npm run clean && tsc && npm-run-all lint karma:once docs@essex/network-navigator: npm ERR! Exit status 1 @essex/network-navigator: npm ERR! @essex/network-navigator: npm ERR! Failed at the @essex/[email protected] verify script. @essex/network-navigator: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. @essex/network-navigator: @essex/network-navigator: npm ERR! A complete log of this run can be found in: @essex/network-navigator: npm ERR! C:\Users\vchau\AppData\Roaming\npm-cache\_logs\2017-06-19T09_38_22_463Z-debug.log @essex/network-navigator: npm ERR! code ELIFECYCLE @essex/network-navigator: npm ERR! errno 1 @essex/network-navigator: npm ERR! @essex/[email protected] test:npm run verify @essex/network-navigator: npm ERR! Exit status 1 @essex/network-navigator: npm ERR! @essex/network-navigator: npm ERR! Failed at the @essex/[email protected] test script. @essex/network-navigator: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. @essex/network-navigator: @essex/network-navigator: npm ERR! A complete log of this run can be found in: @essex/network-navigator: npm ERR! C:\Users\vchau\AppData\Roaming\npm-cache\_logs\2017-06-19T09_38_22_518Z-debug.log NpmUtilities.runScriptInPackageStreaming("test", [], {"_package":{"name":"@essex/network-navigator","version":"0.11.2","description":"","main...) Command exited with status 1: npm run test Errored while running RunCommand.execute Command exited with status 1: npm run test error Command failed with exit code 1.

Inside 2017-06-19T09_38_22_391Z-debug.log

0 info it worked if it ends with ok 1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe', 1 verbose cli 'C:\\Users\\vchau\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js', 1 verbose cli 'run', 1 verbose cli 'docs' ] 2 info using [email protected] 3 info using [email protected] 4 verbose run-script [ 'predocs', 'docs', 'postdocs' ] 5 info lifecycle @essex/[email protected]~predocs: @essex/[email protected] 6 silly lifecycle @essex/[email protected]~predocs: no script for predocs, continuing 7 info lifecycle @essex/[email protected]~docs: @essex/[email protected] 8 verbose lifecycle @essex/[email protected]~docs: unsafe-perm in lifecycle true 9 verbose lifecycle @essex/[email protected]~docs: PATH: C:\Users\vchau\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;C:\Users\vchau\Desktop\PowerBI_Valentin\PowerBI-visuals-NetworkNavigator-develop\packages\network-navigator\node_modules\.bin;C:\Users\vchau\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;C:\Users\vchau\Desktop\PowerBI_Valentin\PowerBI-visuals-NetworkNavigator-develop\packages\network-navigator\node_modules\.bin;C:\Users\vchau\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;C:\Users\vchau\Desktop\PowerBI_Valentin\PowerBI-visuals-NetworkNavigator-develop\packages\network-navigator\node_modules\.bin;C:\Users\vchau\Desktop\PowerBI_Valentin\PowerBI-visuals-NetworkNavigator-develop\node_modules\.bin;C:\Users\vchau\AppData\Local\Yarn\config\link\node_modules\.bin;C:\Users\vchau\Desktop\PowerBI_Valentin\PowerBI-visuals-NetworkNavigator-develop\node_modules\.bin;C:\Users\vchau\AppData\Local\Yarn\config\link\node_modules\.bin;C:\Users\vchau\AppData\Local\Yarn\bin;C:\Program Files\lib\node_modules\npm\bin\node-gyp-bin;C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\Yarn\bin;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\nodejs\;C:\Program Files\Git\cmd;C:\Users\vchau\AppData\Local\Microsoft\WindowsApps;C:\Program Files (x86)\Microsoft VS Code\bin;C:\Users\vchau\AppData\Local\Yarn\bin;C:\Users\vchau\AppData\Roaming\npm 10 verbose lifecycle @essex/[email protected]~docs: CWD: C:\Users\vchau\Desktop\PowerBI_Valentin\PowerBI-visuals-NetworkNavigator-develop\packages\network-navigator 11 silly lifecycle @essex/[email protected]~docs: Args: [ '/d /s /c', 11 silly lifecycle 'typedoc --out docs --ignoreCompilerErrors ./ --externalPattern **/node_modules/**/*.* --exclude **/src/**/*.spec.ts > /dev/null || exit 1' ] 12 silly lifecycle @essex/[email protected]~docs: Returned: code: 1 signal: null 13 info lifecycle @essex/[email protected]~docs: Failed to exec docs script 14 verbose stack Error: @essex/[email protected] docs: typedoc --out docs --ignoreCompilerErrors ./ --externalPattern /node_modules//. --exclude /src//.spec.ts > /dev/null || exit 114 verbose stack Exit status 1 14 verbose stack at EventEmitter.<anonymous> (C:\Users\vchau\AppData\Roaming\npm\node_modules\npm\lib\utils\lifecycle.js:283:16) 14 verbose stack at emitTwo (events.js:125:13) 14 verbose stack at EventEmitter.emit (events.js:213:7) 14 verbose stack at ChildProcess.<anonymous> (C:\Users\vchau\AppData\Roaming\npm\node_modules\npm\lib\utils\spawn.js:40:14) 14 verbose stack at emitTwo (events.js:125:13) 14 verbose stack at ChildProcess.emit (events.js:213:7) 14 verbose stack at maybeClose (internal/child_process.js:897:16) 14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:208:5) 15 verbose pkgid @essex/[email protected] 16 verbose cwd C:\Users\vchau\Desktop\PowerBI_Valentin\PowerBI-visuals-NetworkNavigator-develop\packages\network-navigator 17 verbose Windows_NT 10.0.15063 18 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\vchau\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "docs" 19 verbose node v8.1.1 20 verbose npm v5.0.3 21 error code ELIFECYCLE 22 error errno 1 23 error @essex/[email protected] docs:typedoc --out docs --ignoreCompilerErrors ./ --externalPattern /node_modules//.* --exclude /src//*.spec.ts > /dev/null || exit 1 23 error Exit status 1 24 error Failed at the @essex/[email protected] docs script. 24 error This is probably not a problem with npm. There is likely additional logging output above. 25 verbose exit [ 1, true ]

Inside 2017-06-19T09_38_22_463Z-debug.log
0 info it worked if it ends with ok 1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe', 1 verbose cli 'C:\\Users\\vchau\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js', 1 verbose cli 'run', 1 verbose cli 'verify' ] 2 info using [email protected] 3 info using [email protected] 4 verbose run-script [ 'preverify', 'verify', 'postverify' ] 5 info lifecycle @essex/[email protected]~preverify: @essex/[email protected] 6 silly lifecycle @essex/[email protected]~preverify: no script for preverify, continuing 7 info lifecycle @essex/[email protected]~verify: @essex/[email protected] 8 verbose lifecycle @essex/[email protected]~verify: unsafe-perm in lifecycle true 9 verbose lifecycle @essex/[email protected]~verify: PATH: C:\Users\vchau\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;C:\Users\vchau\Desktop\PowerBI_Valentin\PowerBI-visuals-NetworkNavigator-develop\packages\network-navigator\node_modules\.bin;C:\Users\vchau\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;C:\Users\vchau\Desktop\PowerBI_Valentin\PowerBI-visuals-NetworkNavigator-develop\packages\network-navigator\node_modules\.bin;C:\Users\vchau\Desktop\PowerBI_Valentin\PowerBI-visuals-NetworkNavigator-develop\node_modules\.bin;C:\Users\vchau\AppData\Local\Yarn\config\link\node_modules\.bin;C:\Users\vchau\Desktop\PowerBI_Valentin\PowerBI-visuals-NetworkNavigator-develop\node_modules\.bin;C:\Users\vchau\AppData\Local\Yarn\config\link\node_modules\.bin;C:\Users\vchau\AppData\Local\Yarn\bin;C:\Program Files\lib\node_modules\npm\bin\node-gyp-bin;C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\Yarn\bin;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\nodejs\;C:\Program Files\Git\cmd;C:\Users\vchau\AppData\Local\Microsoft\WindowsApps;C:\Program Files (x86)\Microsoft VS Code\bin;C:\Users\vchau\AppData\Local\Yarn\bin;C:\Users\vchau\AppData\Roaming\npm 10 verbose lifecycle @essex/[email protected]~verify: CWD: C:\Users\vchau\Desktop\PowerBI_Valentin\PowerBI-visuals-NetworkNavigator-develop\packages\network-navigator 11 silly lifecycle @essex/[email protected]~verify: Args: [ '/d /s /c', 11 silly lifecycle 'npm run clean && tsc && npm-run-all lint karma:once docs' ] 12 silly lifecycle @essex/[email protected]~verify: Returned: code: 1 signal: null 13 info lifecycle @essex/[email protected]~verify: Failed to exec verify script 14 verbose stack Error: @essex/[email protected] verify: npm run clean && tsc && npm-run-all lint karma:once docs14 verbose stack Exit status 1 14 verbose stack at EventEmitter.<anonymous> (C:\Users\vchau\AppData\Roaming\npm\node_modules\npm\lib\utils\lifecycle.js:283:16) 14 verbose stack at emitTwo (events.js:125:13) 14 verbose stack at EventEmitter.emit (events.js:213:7) 14 verbose stack at ChildProcess.<anonymous> (C:\Users\vchau\AppData\Roaming\npm\node_modules\npm\lib\utils\spawn.js:40:14) 14 verbose stack at emitTwo (events.js:125:13) 14 verbose stack at ChildProcess.emit (events.js:213:7) 14 verbose stack at maybeClose (internal/child_process.js:897:16) 14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:208:5) 15 verbose pkgid @essex/[email protected] 16 verbose cwd C:\Users\vchau\Desktop\PowerBI_Valentin\PowerBI-visuals-NetworkNavigator-develop\packages\network-navigator 17 verbose Windows_NT 10.0.15063 18 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\vchau\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "verify" 19 verbose node v8.1.1 20 verbose npm v5.0.3 21 error code ELIFECYCLE 22 error errno 1 23 error @essex/[email protected] verify:npm run clean && tsc && npm-run-all lint karma:once docs23 error Exit status 1 24 error Failed at the @essex/[email protected] verify script. 24 error This is probably not a problem with npm. There is likely additional logging output above. 25 verbose exit [ 1, true ]

Inside 2017-06-19T09_38_22_518Z-debug.log

0 info it worked if it ends with ok 1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe', 1 verbose cli 'C:\\Users\\vchau\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js', 1 verbose cli 'run', 1 verbose cli 'test' ] 2 info using [email protected] 3 info using [email protected] 4 verbose run-script [ 'pretest', 'test', 'posttest' ] 5 info lifecycle @essex/[email protected]~pretest: @essex/[email protected] 6 silly lifecycle @essex/[email protected]~pretest: no script for pretest, continuing 7 info lifecycle @essex/[email protected]~test: @essex/[email protected] 8 verbose lifecycle @essex/[email protected]~test: unsafe-perm in lifecycle true 9 verbose lifecycle @essex/[email protected]~test: PATH: C:\Users\vchau\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;C:\Users\vchau\Desktop\PowerBI_Valentin\PowerBI-visuals-NetworkNavigator-develop\packages\network-navigator\node_modules\.bin;C:\Users\vchau\Desktop\PowerBI_Valentin\PowerBI-visuals-NetworkNavigator-develop\node_modules\.bin;C:\Users\vchau\AppData\Local\Yarn\config\link\node_modules\.bin;C:\Users\vchau\Desktop\PowerBI_Valentin\PowerBI-visuals-NetworkNavigator-develop\node_modules\.bin;C:\Users\vchau\AppData\Local\Yarn\config\link\node_modules\.bin;C:\Users\vchau\AppData\Local\Yarn\bin;C:\Program Files\lib\node_modules\npm\bin\node-gyp-bin;C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\Yarn\bin;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\nodejs\;C:\Program Files\Git\cmd;C:\Users\vchau\AppData\Local\Microsoft\WindowsApps;C:\Program Files (x86)\Microsoft VS Code\bin;C:\Users\vchau\AppData\Local\Yarn\bin;C:\Users\vchau\AppData\Roaming\npm 10 verbose lifecycle @essex/[email protected]~test: CWD: C:\Users\vchau\Desktop\PowerBI_Valentin\PowerBI-visuals-NetworkNavigator-develop\packages\network-navigator 11 silly lifecycle @essex/[email protected]~test: Args: [ '/d /s /c', 'npm run verify' ] 12 silly lifecycle @essex/[email protected]~test: Returned: code: 1 signal: null 13 info lifecycle @essex/[email protected]~test: Failed to exec test script 14 verbose stack Error: @essex/[email protected] test: npm run verify14 verbose stack Exit status 1 14 verbose stack at EventEmitter.<anonymous> (C:\Users\vchau\AppData\Roaming\npm\node_modules\npm\lib\utils\lifecycle.js:283:16) 14 verbose stack at emitTwo (events.js:125:13) 14 verbose stack at EventEmitter.emit (events.js:213:7) 14 verbose stack at ChildProcess.<anonymous> (C:\Users\vchau\AppData\Roaming\npm\node_modules\npm\lib\utils\spawn.js:40:14) 14 verbose stack at emitTwo (events.js:125:13) 14 verbose stack at ChildProcess.emit (events.js:213:7) 14 verbose stack at maybeClose (internal/child_process.js:897:16) 14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:208:5) 15 verbose pkgid @essex/[email protected] 16 verbose cwd C:\Users\vchau\Desktop\PowerBI_Valentin\PowerBI-visuals-NetworkNavigator-develop\packages\network-navigator 17 verbose Windows_NT 10.0.15063 18 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\vchau\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "test" 19 verbose node v8.1.1 20 verbose npm v5.0.3 21 error code ELIFECYCLE 22 error errno 1 23 error @essex/[email protected] test:npm run verify23 error Exit status 1 24 error Failed at the @essex/[email protected] test script. 24 error This is probably not a problem with npm. There is likely additional logging output above. 25 verbose exit [ 1, true ]

Note : I noticed that the packages aren't updated to the wanted version when I display the packages version with the "yarn outdated" command

It's been since 15/06/2017 that I've been trying to compile this repo to no avail, any help will be appreciated !

CSS is not loading correctly

Network Navigator throws an unexpected exception in Power BI Desktop

Customer’s repro steps:
Click on data drilldown and then click on a node and the error occurs every time.
I would also note that the functionality that would be implied by the Visualization pane does not seem to always work for the network visualization…IE none of the color data fields seem to have any effect.

JS Error Message:
Cannot read property 'metadata' of undefined

Stack Trace:
Microsoft.PowerBI.Client.Windows.JavaScriptException: An error occurred while rendering the report.
TypeError: Cannot read property 'metadata' of undefined
at Object.getSelectorsByColumn (ms-pbi://pbi.microsoft.com/minerva/scripts/VisualHostCore.js:2812:103)
at VisualContainerController.onSelect (ms-pbi://pbi.microsoft.com/minerva/scripts/exploreui.js:12813:93)
at Object.onSelect (ms-pbi://pbi.microsoft.com/minerva/scripts/exploreui.js:12275:42)
at SelectionManager.sendSelectionToHost (ms-pbi://pbi.microsoft.com/minerva/scripts/visuals.js:34858:53)
at SelectionManager.select (ms-pbi://pbi.microsoft.com/minerva/scripts/visuals.js:34826:77)
at t.persistNodeSelection (https://visuals.azureedge.net/prod/NetworkNavigator1550434005853.js:25:4372)
at t. (https://visuals.azureedge.net/prod/NetworkNavigator1550434005853.js:25:1581)
at delayed (ms-pbi://pbi.microsoft.com/minerva/scripts/powerbi.common.externals.js:28456:27)

Migrate to new build system

Add ability to persist layout to PBI

Support selection on Source and Target nodes

When you select a node in NN, it will filter the "Source Node" column if the node was a "Source" node, and will filter the "Target Node" column if the node was a "Target" node. Allow for the option to select nodes in both the source and target columns when a single node is selected.

Retrieve node label

How to retrieve the Node label of the node clicked on the graph? I need it in lookup value formula.
When clicked on the node in the graph I get both labels from "from" and "to" columns.

Vertex size limits

Add options to limit the max and min vertex size.

The "Clear filter and selection" button isn't vertically centered in its box (bottom of circle should match bottom of "Enter text filter", or centre it exactly)

Level by level

Hi, i havefollowing problwlem I have more than 100 nodes.In such case it"s not clear which root is connected to whic node.Could you make update that we can drill deeper and deeper and not see all level at one moment?

Make sure node labels do not overlap their node

The problem being that if the node labels and the node color are the same color, then you can't see the entirety of the node label.

[Feature] Add starting X,Y

Allow nodes to be placed in a starting position before gravity simulation takes hold. This way geospatial data represented as a schematic is more realistic (things in the north stay in the top part of the chart, things in the south stay in the bottom part of the chart)

Update versioning tasks to look like TimeBrush

https://github.com/Microsoft/PowerBI-visuals-TimeBrush/blob/develop/package.json#L15-L18

Power BI - Change node color in a network navigator chart

I've created a network navigator chart with the node colors as Green(#67D4CC). It works fine on my Power BI desktop(2.88.1682.0 64-bit ). However, after publishing the report onto the web version , the nodes inside the network chart changes to Black color automatically.

I've tried opening in Google Chrome/other browsers, it doesn't seem to work.
Reference: https://community.powerbi.com/t5/Report-Server/Network-Navigator-Colors/m-p/237925

Is there a way to change this on web version? Any clues will be much appreciated.

Thanks in advance.

This repo is missing important files

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

Feature Request: Add Label for Edges / Lines

Hi

Please may you include the option to add Labels to Edges (Lines) that connect two nodes?

Thank you

UI Consistency

Make consistent with all of the other visuals: Padding, Margin, Borders, Font Colors/Sizes...

Add ability to specify edge color

You can pull off edge coloring using a gradient scale, but there is no way to just say, I want this edge to be red.

The Graph needs Tooltips

As stated, the graph currently does not display tooltips, nor have tooltips options. Please add tooltips.

Migrate to new API

Add additional options to sort/render

size of node, an arrow for directed graphs, weight connections that affect distance between nodes, being able to assign tiers to a hierarchy that sort the nodes in the visual e.g. a tree view for a special type of network

Certified custom visual

Hi,

I was wondering if you planned to certify this custom visual. At my company we are only allowed to use certified Custom visuals in Power Bi and I would like to use this custom visual in my current Power Bi report.

Regards,
Luca

Use lodash modules instead of the kitchen sink

"githubUrl" needs to be filled out

maxNodeCount of > 1000 is not taking effect in Power BI Embedded

• We are increasing our maxNodeCountto 10,000 (in the Network Navigator settings in Power BI Desktop), which is what we need, but it is not taking affect in the graph (we are using Power BI Embedded)
• Decreasing it to 10 does take affect - so it seems like the variable is correctly read in the code, when set in Power BI

Has anyone encountered this and any pointers?