Bug report #3298
Rule-based renderer: if rule does not use correct case, "test" succeeds, but no features are rendered
|Affected QGIS version:||Regression?:||No|
|Operating System:||All||Easy fix?:||No|
|Pull Request or Patch supplied:||Resolution:||fixed|
|Crashes QGIS or corrupts data:||Copied to github as #:||13358|
Using the rule based renderer in the new symbology:
e.g. I have a layer with a field named ENVCLASS. If I set up rules based on this class, but all with incorrect case (e.g. EnvClass=1), then the "test" button says the rule works (returns 51 features or whatever), but no features are rendered.
If I change one of the rules to use the correct case (ENVCLASS), then all the features are rendered.
#4 Updated by Alister Hood almost 10 years ago
- Resolution deleted (
- Status changed from Closed to Feedback
The query builder is very nice, but the bug is still valid.
The user can still manually type in the rule (either in the rule properties window or in the query builder). If the case is incorrect the test button (either in the rule properties window or in the query builder) will say the rule works, but nothing will be rendered.