Legacy Notion "Search Objects" filter: removing a condition always fails with "Database ID must not be empty"

:bullseye: What is your goal?

Remove one condition from an AND filter on a Notion “Search Objects” (legacy Database mode) module and save, so the scenario processes all matching records instead of a single hardcoded test record.

:thinking: What is the problem & what have you tried?

Module: Notion Search Objects, connector mode Database (Legacy). The filter has two AND conditions: Status = X, Name = Y. I remove only the second condition (click the x) and click Save. Result: validation error ‘Database ID: Value must not be empty’, even though the Database ID field is visibly populated with the correct value and was not touched. Reproduced 4+ times across separate sessions, including waiting several seconds before saving, and clicking into the Database ID field then pressing End (to touch it without changing it) before saving - same error every time. As a workaround I also tried changing the removed condition’s operator from equals to not-equals instead of deleting it (to keep the array length the same) - that made the entire Filter section disappear from the UI instead (would have removed both conditions if saved, which is worse), so I cancelled without saving. Make itself shows a banner on this module recommending migrating from Database (Legacy) to the new Data Source mode to avoid errors from databases with multiple data sources - which suggests this might be a known regression in the legacy connector’s filter-save validation. I have not attempted the Data Source migration yet since it requires re-mapping all downstream field references. Is this a known bug, and is migrating to Data Source mode the only fix?

Hi Marcelo!
I haven’t encountered this exact issue before, but based on the validation error and the migration banner, it does seem like the legacy Database connector could be the cause rather than the filter itself. If it were me, I’d duplicate the scenario first and test the Data Source migration there before making changes to the production version. I’d be interested to know whether anyone from the Make team has confirmed if this is a known issue with the legacy connector.