# Access child objects inside aggregate data **URL:** \ **Category:** Bug reports\ **Created:** [December 19, 2024, 11:47am UTC](https://community.appfarm.io/t/access-child-objects-inside-aggregate-data/1572 "2024-12-19T11:47:36Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![daniel](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/daniel/32/2882_2.png) [@daniel](https://community.appfarm.io/u/daniel)\ **Post date:** [December 19, 2024, 11:47am UTC](https://community.appfarm.io/t/access-child-objects-inside-aggregate-data/1572/1 "2024-12-19T11:47:36Z")
Hi, I am using the new aggregate data component. I am trying to filter my data source based on a property on a child object to my data source. However, this does not seem to be possible. I can not access any of the properties on my child object. My child object is called “Trip” ![Screenshot 2024-12-19 123152](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/2X/4/4df383141cc1f0330c1570c26d060aa6f21e8ba0.png) I have found a work around, which is to store the information I need from trip on the parent object “Trip Expenses”. My reqest is for it to be possible to access child object properties in the aggregate data component. ---
**Author:** ![Olav](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/olav/32/63_2.png) [@Olav](https://community.appfarm.io/u/Olav)\ **Post date:** [December 20, 2024, 9:19am UTC](https://community.appfarm.io/t/access-child-objects-inside-aggregate-data/1572/2 "2024-12-20T09:19:07Z")
Hi, Daniel! Great to see that you are using the new Aggregate Data action node! The kind of filters on deep data bindings you’re requesting is not currently supported in Appfarm, and probably won’t be anytime soon. Filters on deep data bindings could have major implications for performance, and we instead advise users to do what you have done here and denormalize data. There is a drawback in having to store values in multiple places, but performance-wise this is the way to go currently. ---
**Author:** ![Olav](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/olav/32/63_2.png) [@Olav](https://community.appfarm.io/u/Olav)\ **Post date:** [June 11, 2026, 1:52pm UTC](https://community.appfarm.io/t/access-child-objects-inside-aggregate-data/1572/3 "2026-06-11T13:52:07Z")
Hello, the possibility to group by and aggregate on nested properties is implemented in [version 149](https://community.appfarm.io/t/release-notes-149/2379). Note that this feature is available only for solutions that run the [Data Aggregation Service](https://policies.appfarm.io/glossary/product-glossary#data-aggregation-service). ---
**Author:** ![daniel](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/daniel/32/2882_2.png) [@daniel](https://community.appfarm.io/u/daniel)\ **Post date:** [June 11, 2026, 2:51pm UTC](https://community.appfarm.io/t/access-child-objects-inside-aggregate-data/1572/4 "2026-06-11T14:51:56Z")
That is great news! I have one question regarding this feature. In your earlier comment you mentioned that “Filters on deep data bindings could have major implications for performance, and we instead advise users to do what you have done here and denormalize data.” Is there a major performance trade of when using deep data bindings in the aggregate data component? ---
**Author:** ![Olav](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/olav/32/63_2.png) [@Olav](https://community.appfarm.io/u/Olav)\ **Post date:** [June 12, 2026, 6:20am UTC](https://community.appfarm.io/t/access-child-objects-inside-aggregate-data/1572/5 "2026-06-12T06:20:41Z")
Hi! Building aggregations using deep data bindings has the potential to produce heavy queries that can put significant strain on the database. That is why this new feature is bundled with the [Data Aggregation Service](https://policies.appfarm.io/glossary/product-glossary#data-aggregation-service) - to ensure that you have the appropriate infrastructure to handle it.