-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parameter Select not searching after upgrade from 2.2.5 to 2.3.1 #563
Comments
Hi @luzidl , This should be already fixed on the version 2.3.2 that we are expecting to release today 😀 |
You get a preview of it on |
Cool, thanks for the feedback! I did not see any open bug, thus I opened it. Looking forward to the fix. |
I just released 2.3.2. Can you confirm this is solved for you now? |
Nope, it is still not working. Same as before, no results found when pasting a number or typing a number. |
@BennuFire any thoughts when this will be fixed? :-) It is an essential functionality in my AML&Fraud Demo. Thx in advaned! |
Hi @luzidl, This bug worried me, so I tried to replicatie it on my dashboard. I took a random property of a random node with type "integer" and it seems to work fine: Are you sure you didn't inadvertently change something in the settings? (just trying to think along...) Guido |
@luzidl I'm still trying to replicate the issue with no success. Can you share you dashboard json? |
For sure @BennuFire, will send it via email in a moment. |
Fixed on 2.3.5 |
@BennuFire, not entirely as I can see. I can not find the accountIds, but the queries are not finding anything. It seems, that parameter is not set correctly. I also tried to convert it explicitly to a number format and to a String format, but nothing works. Queries do not return any data. See screenshot below: |
After upgrading a couple of Dashboards from 2.2.5 to 2.3.1 parameter select seems to not take input that is stored as number in the database. Cut and paste of an accountID (data type: number, eg. 55716) provided a result in NeoDash 2.2.5, but did not find it in 2.3.1. Searching by typing the same account ID number does not work either. (See graphics attached below):
NeoDash version: 2.2.5 --> 2.3.1
Neo4j Database version: 4.4. 3 (Enterprise).
Steps to reproduce
Migrate a DB (4.4.3) from NeoDash 2.2.5 to 2.3.1 using a parameter select visualization on a node property that is a data type number and try to search a number in both.
Expected: Number is found immediately if pasted or partially if it it typed.
NeoDash 2.2.5:
![image](https://private-user-images.githubusercontent.com/8035021/260417053-1babbb20-8ad2-484e-98dc-ed2161b94c0b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk1Mzg5OTksIm5iZiI6MTcxOTUzODY5OSwicGF0aCI6Ii84MDM1MDIxLzI2MDQxNzA1My0xYmFiYmIyMC04YWQyLTQ4NGUtOThkYy1lZDIxNjFiOTRjMGIucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDYyOCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA2MjhUMDEzODE5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YmQxNzA4MzM2NWZlNjRjYTBkZGIzZWYxMGQ0OTVkOWU1YzY2YjVhNDc5ZWQxZDY1MzIxNjYxNzk4Y2Q0YjQ0OSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.VY5dYxwZ5wSxj0xq9HbtFGLdVrYx-EqGlAz4-JB6BP4)
NeoDash 2.3.1:
![image](https://private-user-images.githubusercontent.com/8035021/260417855-12cb3ddb-c406-4a64-a2b4-f5d43922dc5f.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk1Mzg5OTksIm5iZiI6MTcxOTUzODY5OSwicGF0aCI6Ii84MDM1MDIxLzI2MDQxNzg1NS0xMmNiM2RkYi1jNDA2LTRhNjQtYTJiNC1mNWQ0MzkyMmRjNWYucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDYyOCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA2MjhUMDEzODE5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NmIwNDQzODNiMWM4ZTgxY2I0ZjA4ZjkzMWQ5YTAzNDE3ZTdlNmMzNzg3NjhkMDU4NWIwZTRkZWNiYTA2NmIzMyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.waTSC-usqq3uZwjFmRV6xPWRJOAxQsk26VYcR87WtNo)
The text was updated successfully, but these errors were encountered: