Groups vs nesting

[stuart]

Hi -

Can someone explain the benefits / disadvantages of using nested values of a single type as opposed to creating parent groups. e.g. using the following approach for locations (or people) as opposed to having a separate parent group that any children would get added to.

Thanks

[stuart]

@jess ? Can you advise me here? Keen to know the pros/cons for each method before going too far with one or other approach.

[jess]

Are you able to clarify the two different approaches you are wanting to compare? From your screenshot, it looks like one approach is to create a location such as UK and then add other locations that are inside the UK (such as London) and assign UK as their parent. I’m not too sure what you mean by a “separate parent group and any children would get added to”. In terms of using parent/child relationships, for entities it is mainly an organisational thing, however we are looking to enhancing this so that filters and relationships take better advantage of this.

[Peter_T]

@stuart

Can someone explain the benefits / disadvantages of using nested values of a single type as opposed to creating parent groups

If you use groups, the children don’t have to be the same type as the parents. Groups themselves do not have to be of a concrete type, but can be more abstract. Here is an example:

In your example you use nesting optimally, in my example grouping is advantageous.

Cheers,
Peter