# Nested Properties

**URL:** <https://pug.phocassoftware.com/t/nested-properties/2656>\
**Category:** Product Ideas\
**Created:** [February 26, 2024, 9:23pm UTC](https://pug.phocassoftware.com/t/nested-properties/2656 "2024-02-26T21:23:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![scottmunroe](https://avatars.discourse-cdn.com/v4/letter/s/ed655f/32.png) [@scottmunroe](https://pug.phocassoftware.com/u/scottmunroe)\
**Post date:** [February 26, 2024, 9:23pm UTC](https://pug.phocassoftware.com/t/nested-properties/2656/1 "2024-02-26T21:23:00Z")

</div>

We are trying to use nested columns to create report which shows inventory by part and can expanded to show qty in individual warehouses.  
The nested columns will roll-up meaurse such as Qty On Hand, but we also need to show properties such as Last Receipt. Properties can only be included for the item, which in this case would be the warehouse.

We can build a key to use as a dimension which would be in the format ‘Part-Warehouse’, but that would not be practical because the code can not be suppressed and that would not work for us.

We have deselected the code many times in non-nested mode to show key properties without the underlying key. Can we please have this feature in nested mode?

---

<div class="post-metadata">

**Author:** ![JonKemp](https://sea1.discourse-cdn.com/flex015/user_avatar/pug.phocassoftware.com/jonkemp/32/334_2.png) [@JonKemp](https://pug.phocassoftware.com/u/JonKemp)\
**Post date:** [April 2, 2024, 9:48am UTC](https://pug.phocassoftware.com/t/nested-properties/2656/2 "2024-04-02T09:48:45Z")

</div>

Hi @scottmunroe ,

This unfortunaltey has been a long standing gripe of mine. The only means of mitigation will be to create a deddicated dimension, My DB has swollen in size due to this limiting factor (I have many example of where the “Code” is something I need to remove). Here is the original post I made back in 2019:

> [@Nesting mode - removal of code](https://pug.phocassoftware.com/t/nesting-mode-removal-of-code/1065/5):
>
> What I don’t understand is that in typical queries, the Code property can be excluded. It’s only when you enter Nested Grid that the code property becomes grayed out. I get that the code is required as a key in order to perform the joins tying the data sets together, but why is that information necessary to be displayed? This is starting to cause issues with regards to being able to send reporting out via automation to outside clients. On one hand, I can subscribe to the report, and forward i…

Reagrds,

Jon