Hi Cirrus,
Yeah, you’re on the right track — and you’ve already hit the key limitation.
In Workspace, the “New” button is controlled by Declarative Actions, not by list control settings, and those actions are applied at the table level, not per related list instance. That’s why:
- Disabling it removes it everywhere
- Action exclusions also apply globally for the table
There’s no OOTB way to hide the “New” button for only one related list when both are on the same table.
What you can do (workarounds)
1. Use condition on Declarative Action (best option)
Instead of disabling the action, add a condition to the “New” declarative action so it only shows in the correct context.
You can check things like:
- Parent record context
- Relationship conditions
- Encoded query / parameters
Example idea:
- Show “New” only when the related list is based on
parent - Hide when it’s coming from
top_project
This usually involves checking the context passed to the component (like parent record sys_id or relationship field).
2. Create a custom Declarative Action
If the OOTB one is too generic:
- Clone the “New” action
- Add your own condition logic
- Disable OOTB one
This gives you full control over when it appears.
3. UI Builder override (advanced)
If conditions aren’t enough:
- Go to UI Builder → Workspace page
- Locate the related list component
- Override actions for that specific component
This is the only way to get true per-related-list control, but it requires customization.
4. Defensive backend logic (recommended anyway)
Since users might still find ways to create records:
- Add a Business Rule:
- If created via top_project context → correct or block it
