Instance Discovery, Performance tab and attached DCIs

[Tursiops]

I keep running into a problem when using templates that hold instance discovery DCIs which are to be attached to another DCI for display on the Performance tab.
In the template itself everything looks fine.
But as soon as the template is applied, the Performance tab will only show the "primary" DCI, not the attached one(s).
When I check the actual DCIs that are not showing, I receive a pop-up as I open them, stating

'Resolve DCI name' has encountered a problem.
Cannot resolve DCI name: Invalid DCI ID

The actual instance DCI itself already produces the above error message, hence all instances do, too.

To make matters more confusing, this doesn't always happen.
I have some instance discovery DCIs using the NetXMS agent which work just fine.
Now I just added some for network interfaces via SNMP and none of them work properly.

And just as I typed all of that, I think I found the issue (still leaving all the above text in case it helps someone in the future).
It's the order of the DCIs for instance discovery.
The first DCI in the list (by DCI ID, not name) must be the "primary", otherwise the "discovered" primary DCI doesn't exist by the time the second/third/etc. are trying to attach to them, hence the process fails. Makes sense, but feels counter-intuitive having to watch the order in which DCIs are entered when setting them up.

No idea if that's something that could be worked around in the code to make it less reliant on the order in which DCIs are entered? For example don't "attach" the DCIs until Instance Discovery has been completed?

[victor]

Hi,

yes, that's a problem. I think that configuration for combining DCIs into single chart should be changed to use some sort of a key - then you just specify same free form key for all DCIs you want on one chart and system combines them. This will eliminate current complexity and bugs. The only issue is that current configurations may break down during migration.

Best regards,
Victor