Qdrant node Search Filter field bug - can't use expressions - can't delete field

[richardosborne14]

Describe the problem/error/question

When editing the Qdrant node in 'Get Many' form, adding a 'Search Filters' field works fine if using fixed data. Clicking 'expression' does not switch to an expression field. Clicking the trash icon on the Search Filters field does not delete the field.

What is the error message (if any)?

No error message. Nothing in browser Javascript console.

Please share your workflow/screenshots/recording

{
  "nodes": [
    {
      "parameters": {
        "mode": "load",
        "qdrantCollection": {
          "__rl": true,
          "value": "listings",
          "mode": "list",
          "cachedResultName": "listings"
        },
        "prompt": "={{ $json.chatInput }}",
        "topK": 20,
        "options": {
          "searchFilterJson": ""
        }
      },
      "type": "@n8n/n8n-nodes-langchain.vectorStoreQdrant",
      "typeVersion": 1,
      "position": [
        920,
        0
      ],
      "id": "422f62e2-2088-4a83-9a20-7a88dd50462c",
      "name": "Qdrant Vector Store",
      "credentials": {
        "qdrantApi": {
          "id": "UsWU3e6pGYv64xnx",
          "name": "QdrantApi account"
        }
      }
    }
  ],
  "connections": {
    "Qdrant Vector Store": {
      "main": [
        []
      ]
    }
  },
  "pinData": {},
  "meta": {
    "templateCredsSetupCompleted": true,
    "instanceId": "9705fb1753029493749953b8d12ef1657051de96991205f666d87180aefbcf1b"
  }
}

Share the output returned by the last node

Debug info

core

• n8nVersion: 1.75.2
• platform: npm
• nodeJsVersion: 20.18.1
• database: sqlite
• executionMode: regular
• concurrency: 5
• license: community

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: filesystem

pruning

• enabled: true
• maxAge: 168 hours
• maxCount: 2500 executions

client

• userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/131.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2025-01-22T13:44:08.537Z}

[Joffcom]

Hey @richardosborne14,

We have created an internal ticket to look into this which we will be tracking as "N8N-8202"

[jeanpaul]

@richardosborne14 Can you explain in more depth what you're doing? Maybe record a video? I don't have this issue: