Neodash - cypher results in MarkDown

Integrations
,
1

Parameter question:

I have a parameter selection like "Client".

Once the user selects a client, I'd like to set more than one parameter values to use:

  1. In other queries substituting the query - that's easy out-of the box already, but

  2. I'd like to build a Markdown report pulls several stats/values from the above query/parameter selection to display some information once the "client" is selected.

    Thanks!

2

Hi @pdrangeid ,
Thanks for using NeoDash!
As you may have seen, it's already possible to substitute the selected parameter in a markdown report (see attached screenshot). Unfortunately it's not yet possible to generically send query results to other reports, but it sounds like an interesting addition, I will add this to the backlog. Am I understanding correctly that this would solve your challenge?

If yes, let me know, and I can keep you posted on this thread with the progress on the feature.

Best,
Niels

3

Yes that would work. Aside from that, An idea I had was to add a "non-interactive" Parameter Report type that would help solve this (unless there is already a way to do what I intend).
This report would have (or default to)a "hidden:true" so in read-only mode you don't see the UI.
Within this report you would write a CYPHER query that can use other $neodash_param
and the resulting output would set $another_neodash_param to the results of the cypher query.

Is there already a way to SET a $neodash_parameter to the results of a CYPHER query other than the interactive Parameter report method?

4

Hi @pdrangeid , great, I've noted it down. The hidden reports feel like a nice way to do this, it's essentially a "trigger" that updates parameters dynamically based on the dashboard state changing.

_> Is there already a way to SET a $neodash_parameter to the results of a CYPHER query other than the interactive Parameter report method?

_Unfortunately not, parameter select reports are the only means of doing this. What you could do, however, is "hack" the save file of a NeoDash dashboard and change the query used by a parameter select report to be no longer bound to the node property itself. (The line to change is marked in grey here in the screenshot.) In this query, the value "$input" will always be set to the property selected by the user, and you can return any "value" which will be the dashboard parameter that is set.

This is a little unintentional / undocumented feature, but I've seen people do it successfully.

Best of luck and thanks again for the feedback,
Niels

5

I've attempted this workaround, but it does not appear to work properly. I don't think I'm quite grasping the manual edits to make this work correctly:

{
            "title": "",
            "query": "MATCH (n:`M365user` {displayname:$neodash_m365user_displayname}) RETURN DISTINCT n.`lastsignin` as value",
            "width": 3,
            "height": 2,
            "x": 0,
            "y": 4,
            "type": "select",
            "selection": {},
            "settings": {
              "nodePositions": {},
              "autorun": true,
              "replaceGlobalParameters": true,
              "type": "Node Property",
              "entityType": "M365user",
              "propertyType": "lastsignin",
              "parameterName": "neodash_m365user_lastsignin",
              "clearParameterOnFieldClear": false,
              "manualPropertyNameSpecification": false,
              "helperText": "some custom helper text"
            }
          }
6

Hi @pdrangeid ,

Thanks for the details.

I tried it out and you're right, it seems like the parameters are not used by the query that populates the suggestions for the parameter select. It's therefore not possible to have a conditional parameter selector at the moment, which I thought was working.

I have created an issue on the project to fix the problem:

https://github.com/neo4j-labs/neodash/issues/338

Feel free to track this one as we get to the feature.

Best regards,
Niels