* Describe the bug
Linkage rules on action buttons are not evaluated per record in a List block. When a condition is set to show/hide a button based on a field value (e.g. Status is not "Offen" → hide button), the rule appears to apply the same result to all records instead of evaluating each record individually. As a result, the button is shown or hidden for all records regardless of their actual field value.
* Environment
- NocoBase version: 2.0.53
- Database type and version: PostgreSQL 16
- OS: MacOS Catalina 10.15.8
- Deployment Methods: Docker container
- Docker image version: 2.0.53
- NodeJS version: N/A
* How To Reproduce
- Create a List block on a collection that has a Single Select field (e.g.
status) with at least two different option values. - Ensure the list contains at least two records with different values in that field (e.g. one record with
offen, one withvergeben). - Add an action button (e.g.
Übernehmen) to the List block. - Open Linkage Rules for that button and add a rule: condition
Current record / status is not "offen"→ actionSet button state: Hidden. - Save the rule.
- Observe that the button visibility is the same for all records, regardless of their actual status value.
Expected behavior
The linkage rule should be evaluated independently for each record. The button should only be visible on records where status = offen, and hidden on all others.
Screenshots
(See attached screenshot — two records visible: one with status “Vergeben”, one with status “Offen”. The “Übernehmen” button is visible on both despite the linkage rule.)
Related Issues
This bug was discovered in the context of ([Bug] Linkage rule condition shows no options for Single Select field from SQL Collection despite correct field source being resolved)
(“[Bug] Linkage rule condition shows no options for Single Select
field from SQL Collection despite correct field source being resolved”)
Logs
N/A — no API errors observed. This appears to be a frontend evaluation issue with linkage rules in List blocks.