How to emulate components in interactive scheduling

[Sam Karli]

Hi,

I have a GDL libpart that I develop, and I'm about to check whether listing works for it.

This is a wall accessory placing wall panels into a wall. The old style listing works using components.

My problem is how to do this using interactive scheduling.

What you see here is a part of an interactive scheduling:

Per row there is a wall having multiple panels having their own names (both represented in listing parameters).

Note that in the 1st column (40 cm panel type) every panel has the same name and in the 3rd column these differ.
Is there a way of summing/counting the items that it sums the (1st/) 2nd column (as these panels are the same, having the same names) and sums the (3rd/) 4th column in a way that it sums somehow only those that are of the same type (note that here all names differ; so btw nothing to sum)? 

So in this example in the 2nd column there should be a sum of (2+2+0+2+1=) 7 and in the 4th column 1 of every type?

In excel it is not complicated.

In the old style calculation it can be easily done by components.

How to do this using interactive schedulnig.
Note that as this is a GDL development i can create any listing parameter, the question is about summing those.

Operating system used: Windows 10

[Barry Kelly]

Have you tried the Field Merge options?

Barry.

[Lingwisyer]

I do not believe this will sum the values if they are based on a parameter instead of a straight up quantities listing... Unless they changed how it worked with the field merger update.

[Sam Karli]

A far as I have checked if i mark this for the differing panels (3rd/4th col), it doesn't sum the 1st and 2nd rows (not a surprise, then this separates every rows having different special panels). This is the way it should work.

Actually this is why I'm looking for a component-like behavior.

My problem is that I need a component-like behavior, but for a more modern (like classification/property based) element filtering, and

Having interactive scheduling I don't seem to be able to reproduce the component-like behavior

Having old school calculating I can do this but I cannot select elements, like, based on properties.