Bug: Adding entry in a view with active "contains" filter doesn't show the created entry

[Lisa Mittermair]

Hi,

when trying to add an entry in a view with an active filter that uses the "contains" operator, the add entry button seems to do nothing - in the background, it actually does create a new row. But it's not shown in the view with the active filter cause the correct value for the "contains" operator is not automatically filled in.

This only happens with the "contains" operator. If I use the "is" operator, it automatically fills in the correct value.

Screenshot 1: adding an entry while filters are applied to the selected view (button seems to do nothing)

Screenshot 2: the applied filters

Screenshot 3: the result in the database - the column with the "is" operator has the correct value but the column with the "contains" operator is empty.

[Pierre Biffaud]

It is because when you create the row, the value is blank and the filter filters it... A workaround i found is to add a filter (in your case) "Platform/App is empty" (with the match 'any filter') to see the newly created row.

[Yannick Rondeau]

Hi,

I've also found this to be an issue when filtering data by multiple columns.

In one of our databases, we filter based on the year of a date depending on the view, i.e., the date is after 01/01/2024 and before 12/01/2024. However, if we want to add a new entry, it wouldn't show up at all in all of the filtered views.

Thanks,

--

Update

One workaround I've found is to add default values to the filtered column. However, it would still be great if a new line would stay there until it is saved.