Share your feedback...
Cannot create relationships in explore gui
Hi, i use the free Neo4J AuraDB Workspace Explore view. It seems that i cannot create relationships in the GUI between existing nodes. Example: i select two nodes right click -> create relationship -> i select one of the available relationship types the relationship create menu opens i click "create" to save the relationship, but nothing happens I use Microsoft Edge Version 120.0.2210.91. When i open the dev console, some error about "t.join is not a funciton" appears whenever i click to create the relationship, see the included picture for this. Everything else in the gui works as intended. Creating relationships with cypher queries also works fine, but i need to use the GUI for now. Am i doing it wrong, or is this a bug?
ValueError: Could not connect to Neo4j database. Please ensure that the url is correct
Getting this error but the url is correct. What should I do?
The "Inspect" function with nodes is not working. I've tried to use it with chrome and firefox and once that I try to inspect a node the explorer stops working.
AuraDB Enterprise should show the user their Role(s) just like Desktop
I had a user where he could log in but couldn't see anything. Turns out his role was Public instead of Public, Reader. In Desktop we can see the role when we make the database connection. I could not find this information in Query.
extremely slow for creating nodes/relationships
I have deployed an instance in azure and run my data load on a azure VM, and yet the process is extremely slow. On an empty db, creating 15 notes takes 30 seconds
Add option to hide relationships
Today it is possible to expand nodes and show outbound relationship, it would be great to contract/condense as well, instead of having to rerun the query. This will make data exploration easier.
Change color of nodes within a label in query output
Hello! I would like to be able to change the color of nodes within a specfic label in a query output. This will make it much easier to navigate within the nodes from the query output. Today is hard to navigate in a query output that contains more than 50+ nodes.