I’m running into what seems like a bug or unexpected behavior when using Advanced Actions on a Collection component.
Here’s the scenario:
- I have a detail screen showing information from a parent record (let’s call it Parent).
- Below that, I display a Collection of related child records (let’s call them Child records).
- Using Default Actions, the “+” button on the Collection’s title bar correctly opens a form to add a new Child record — which is what I want.
- But as soon as I switch to Advanced Actions, the “+” button opens the form to add a new Parent record instead — even though I’m clearly working within the Collection context.
It seems like the title bar action gets tied to the parent screen’s data instead of the Collection’s source table when Advanced Actions are enabled. The behavior for item-level actions remains correct — it still targets the Child items.
I’ve confirmed this across multiple layouts, and even renamed the button to “+ Add Child” for clarity — but it still launches the wrong form when using Advanced Actions.
Is anyone else seeing this? Is there a workaround to make Advanced Actions respect the Collection’s data source instead of defaulting to the screen’s main source?
Thanks in advance for any insight or fixes!