Server
- Seatable 6.0.10 Enterprise self hosted.
- Verified with Seatable cloud
The Problem
Sorry that I have to raise another issue, but I have found an unexpected behaviour on the API and need to verify whether it’s a bug, or just my expectations are wrong. Couldn’t find anything similar mentioned here.
To reproduce:
-
Create any table with a date column and populate with some data. The “created“ column will do.
-
Retreive the view via the API - I used Seatable’s integration into n8n as well as local python scripts in Seatable, using the internal API.
-
The records will be retrieved as expected.
-
Filter the view using the date column you have just created - use “Created is today“ or “Created is on exact date X“. All the records shown in the GUI are also retrieved via the API
-
Filter the view using the date column you have just created - use “Created is on or before today“ or “Created is on or before exact date X“. The GUI still shows the lines created today, but the API retrieves nothing!
-
Filter the same view with the date filter in a filter group like shown below. Again, the GUI shows the filtered rows as expected, while the API either returns “500 Server Error“
and sometimes this Error 400
Can anyone verify? Am I doing something wrong? I’m not setting any filters or SQL clauses - I’m just using plain old API calls on filtered views. In terms of python scripts:
from seatable_api import Base, context
base = Base(context.api_token, context.server_url)
base.auth()
mytable = context.current_table
# get filtered view
rows = base.list_rows('Table1', 'Default View')
That script crashes when the view is filtered like under 5. or 6.
