# Enabling advanced actions on a collection’s title bar causes the “+” button to open a form for the parent item instead of the correct child item

**URL:** <https://community.glideapps.com/t/enabling-advanced-actions-on-a-collection-s-title-bar-causes-the-button-to-open-a-form-for-the-parent-item-instead-of-the-correct-child-item/81749>\
**Category:** Report a Bug\
**Created:** [May 6, 2025, 6:38pm UTC](https://community.glideapps.com/t/enabling-advanced-actions-on-a-collection-s-title-bar-causes-the-button-to-open-a-form-for-the-parent-item-instead-of-the-correct-child-item/81749 "2025-05-06T18:38:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Inna\_berkovich](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/inna_berkovich/32/87842_2.png) [@Inna\_berkovich](https://community.glideapps.com/u/Inna_berkovich)\
**Post date:** [May 6, 2025, 6:38pm UTC](https://community.glideapps.com/t/enabling-advanced-actions-on-a-collection-s-title-bar-causes-the-button-to-open-a-form-for-the-parent-item-instead-of-the-correct-child-item/81749/1 "2025-05-06T18:38:49Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [May 6, 2025, 6:46pm UTC](https://community.glideapps.com/t/enabling-advanced-actions-on-a-collection-s-title-bar-causes-the-button-to-open-a-form-for-the-parent-item-instead-of-the-correct-child-item/81749/2 "2025-05-06T18:46:25Z")

</div>

Forms can write to any table. You just need to change the destination source table for the form.

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\
**Post date:** [November 2, 2025, 6:46pm UTC](https://community.glideapps.com/t/enabling-advanced-actions-on-a-collection-s-title-bar-causes-the-button-to-open-a-form-for-the-parent-item-instead-of-the-correct-child-item/81749/3 "2025-11-02T18:46:53Z")

</div>

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.