Report Actions not setting FALSE boolean value to PARAMETERS accurately

[pdrangeid]

• NeoDash version: v2.4.9-labs
• Neo4j Database version: Aura

Summary

When using Report Actions in NeoDash, assigning a parameter to the boolean value false causes NeoDash to incorrectly substitute the parameter with a different column's string value

Reproduction Steps

1. Use a table widget with a query like:

   RETURN f.name AS Feature, f.isMVP AS __mvp
   
   

2. add a report action: { "condition": "Click", "field": "Feature", "value": "__mvp", "customization": "set variable", "customizationValue": "feature_new_ismvp" }

3. Click on a row where f.isMVP = false.

4. Use a markdown or debug panel to display {{feature_new_ismvp}}.

Expected The parameter feature_new_ismvp is set to boolean false.

Actual The parameter is set to the Feature name string, such as "🧩 Backup Validation Module".

Workaround Return 'false' as a string in the source query: RETURN CASE f.isMVP WHEN true THEN true ELSE 'false' END AS __mvp

Then in Cypher queries or forms, cast it back: toBoolean($feature_new_ismvp)

Notes This bug does not occur for true, only false. We suspect a React rendering issue where falsy values are causing a fallback to another column’s content.