Skip to content
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

[Bug] Device groups found by name only with lowercase filters #7415

Closed
slibutti opened this issue Oct 12, 2022 · 2 comments
Closed

[Bug] Device groups found by name only with lowercase filters #7415

slibutti opened this issue Oct 12, 2022 · 2 comments
Assignees
Labels

Comments

@slibutti
Copy link

Description

Device groups are not found by name anymore, both with dashboard aliases and REST APIs, when their name is in uppercase.
Queries are successful only if startsWith field value is put in lowercase.
E.g., MYGROUP is not found when using startsWith = "MYG" but is found using startsWith = "myg".

Tested both with dashboard aliases (Device groups whose names start with 'XXX')
and REST APIs (/entity-query-controller/findEntityDataByQueryUsingPOST).

Server Environment

Thingsboard v3.4.1PE, both on-premise (ubuntu/docker) and on thingsboard.cloud

Client Environment

Tested on several browsers/OSs and with curl

To Reproduce (dashboad alias)

  1. Create a device group named, e.g., TESTGROUP;
  2. Create a dashboard alias "Device groups whose names start with 'TESTG'" (won't find anything);
  3. Create a dashboard alias "Device groups whose names start with 'testg'" (will work).

To Reproduce (REST)

Endpoint: /entity-query-controller/findEntityDataByQueryUsingPOST
Query: {"entityFilter":{"type":"entityGroupName","groupType":"DEVICE","entityGroupNameFilter":"TESTG"},"pageLink":{"page":0,"pageSize":1}}

  1. Create a device group named, e.g., TESTGROUP;
  2. Search for device using entityGroupNameFilter "TESTG" (won't find anything);
  3. Search for device using entityGroupNameFilter "testg" (will work).

Notes

The same aliases and REST calls were working in v.3.3.2pe, which I was using before upgrading to latest version.

@YevhenBondarenko
Copy link
Contributor

The fix will be released in v3.4.2

@Ultrazombie
Copy link

We inform you that your GitHub ticket has been inactive for some time, and we will close it. If you have any more concerns or encounter similar issues, please don't hesitate to contact us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants