tables icon indicating copy to clipboard operation
tables copied to clipboard

Filter in Views - Metadaten

Open ISC-PRO opened this issue 2 years ago • 4 comments

Steps to reproduce

Problem aus "Fix/547 views filter metacolumns #558" besteht weiterhin: https://github.com/nextcloud/tables/issues/547

Mit Erstellung einer neuen Zeile wird automatisch das Standard-Feld "Erstellt am" und "Zuletzt bearbeitet am" mit demselben Wert vorbelegt - soweit in Ordnung. Dies machen wir uns zu nutze, damit neue Einträge in einer separaten Ansicht "New Items" für eine bestimmte Gruppe gefiltert angezeigt werden.

Aufbau der Tabelle

  1. Tabelle "Freigabe": Spalte "Titel" (Text, Pflichtfeld) und Spalte "System" (Auswahlfeld: DEV, TEST, PROD)
  2. View "New Items": Filter Spalte "Erstellt am", Bedingung "Ist gleich", Wert "Zuletzt bearbeitet am" kann nicht selektiert werden.
  3. Weiterhin funktioniert auch die selektierbare Vorauswahl "Heute" und "Jetzt" nicht - es wird kein Ergebnis angezeigt
  4. Auch die eigenständige Eingabe eines Datum als Wert (z. B. 2023-09-13) ist nicht möglich

Tabelle 2023-10-02_001

Ansicht 2023-10-02_002_without_Filter

Filter 2023-10-02_003_Filter_Settings

Ergebnis 2023-10-02_004_Filter_Result

Expected behavior

Vergleich vorhandener Metadaten-Spalten ("Erstellt am" = "Zuletzt bearbeitet am") => neuer Eintrag

Actual behavior

Filter funktioniert nicht.

Tables app version

0.6.0

Browser

Chrome 115.0.5790.111

Client operating system

No response

Operating system

No response

Web server

None

PHP engine version

None

Database

None

Additional info

No response

ISC-PRO avatar Oct 02 '23 11:10 ISC-PRO

Hi,

if possible, it would be nice if you could write in English. That way it would be possible for everyone to join and understand this issue.

Well, I see a bug, but some of your description should work with the right understanding:

  • [ ] 1. Today != now The app takes the "today" value as the start of the day (2023-11-15 00:00), to compare with equal don't show the expected entries. We should fix that.

  • [ ] 2. Using context data If I understand that right, you try to filter for a value (last edited) that comes from the row itself. This is not a bug, more a feature request. We need a separate issue for that and have to think about if this is a common and understandable way for those tricky filtering. But why not...

3. More magic values What you could do right now is to filter like "created at < today". Or set a fixed date (always means the day start like described in 1.) Here is the idea to add more magic values #600. That could make it possible like: "created at < today AND created at > yesterday" to get all created item from yesterday, or similar to get the new items from the last week etc. Maybe you can also filter out today updated items. (... AND last edited at < today)

Can you agree with this points?

datenangebot avatar Nov 15 '23 14:11 datenangebot

Hello, sorry for the late reply, but I also made my points in the last online session on January 30.

  1. Ok - fix it.
  2. All new items has the same value in field "created at" and "modified at".

Example: See Screenshots.

List Filter

NEW Item = WHEN "created at" = "modified at" EDIT Item = WHEN "created at" != "modified at"

Otherwise I agree.

ISC-PRO avatar Feb 14 '24 11:02 ISC-PRO

Good morning. Can you tell me what the further planning looks like?

ISC-PRO avatar Jan 06 '25 09:01 ISC-PRO

Good morning. Can you tell me what the further planning looks like?

Also here, nobody picked it up so far.

blizzz avatar Jan 06 '25 15:01 blizzz