Note that the issue was arised by a real customer that didn’t understand the behaviour. Keeping the current behaviour is specially strange when the user is clicking on “view”-type locations where quantity will always be 0 if children are not considered.
Even more, we always discourage adding children to storage-type locations and recomend using view locations only. The reason is that it is hard to know the quantity of the location without including its children.
I would personally do in one of theses too alternatives:
- As Àngel suggests, create two actions. Though it has the problem that it makes the interface more complex.
- Always include children and prevent creating children on storage-type locations. I think this is the best option because it prevents the aforementioned problems.