h3. How to reproduce
To avoid steps the first two steps, and having to create data for the livetable, you can import [^bugReport_02112023.WebHome.xar]
# Create a Live Data on a class which has a database list property (called myList after)
# Configure the Live Data to filter myList with operator "equals" instead of the default "contains", as in the example code below
{code:java}
{{liveData
id="bugReport_02112023"
properties="doc.title,myList"
source="liveTable"
sourceParameters="className=bugReport_02112023.databaseListClass"
}}{
"query": {
"filters": [
{
"property": "myList",
"constraints": [
{
"operator": "equals"
}
]
}
]
}
}
{{/liveData}} {code}
# Open the filter panel (button with vertical "..." >> Filter... )
# View that myList has a default "Equals" operator for the filter, like in the following screenshot !beforeSelect.png|width=553,height=257!
# Select one of the values in the list to the right
# See that the operator changed back to "Contains", like in the following screenshot
# !afterSelect.png|width=556,height=258!
h3. Expected behaviour
The operator should be kept to its configured default value after the select instead of switching to "Contains".
The expected behaviour happens with text properties. |
|
