-
-
Notifications
You must be signed in to change notification settings - Fork 143
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]: Using Filter expression on value relation widget always give an empty list #2589
Comments
Maybe a duplicate of this issue... #2561 |
@mathieubossaert do you have lizmap-plugin installed as a QGIS Server plugin ? |
This issue is missing some feedbacks. 👻 |
Oups if forgot to answer your question. No I do not have any plugin installed |
It's now highly recommended to have Lizmap as a QGIS server plugin as well. Otherwise, a few features are not working since LWC 3.4. |
ok Thanks @Gustry I will update my install and test it. |
You should install a few plugins in QGIS Server to enable more features in Lizmap : https://docs.lizmap.com/current/fr/install/pre_requirements.html#qgis-server-plugins To install them, https://www.3liz.com/news/qgis-plugin-manager.html the tool qgis-plugin-manager can help |
What is the bug?
I have a PostgreSQL table that stores available values for the attributes of my tables.
After upgrading from an EOL Lizmap version to the last one I face this problem 👍
All value relation widget provide an empty list.
No error in logs.
Alter a lot of tries, I had the idea to clear the "Filter expression" and I get all values from the table.
The workaround is to create a view for value each and to call this view in the value relation widget.
Steps to reproduce the issue
Create a filed with a value relation widget that uses a filter and try to edit a feature to see the list is empty.
Lizmap version
both 3.4 and 3.5
QGIS desktop version
3.16.13
QGIS server version
3Liz 3.16 docker image
Operating system
debioan 10
Browsers
Firefox
Browsers version
Firefoc 94 on ubuntu
Relevant log output
No response
The text was updated successfully, but these errors were encountered: