The link ControlWithIEDName is not built when one IED name is a substring of another IED name in the file

[ADehouck]

When an IED name is the substring of another IED name in the file, the "ControlWithIEDName" link is not built correctly

Example with that file : LGOS.zip

The file contains

• one IED named "fake1"
• another IED named "fake12"

When RiseClipse parses the path in "setSrcRef" :

          <LN lnClass="LGOS" lnType="LGOS1" inst="1" prefix="">
            <DOI name="GoCBRef" desc="">
              <DAI name="setSrcRef">
                <Val>fake12lDevice1/LLN0.gcb1</Val>

RiseClipse raises the following WARNING, and the explicit link is not created.

WARNING: [SCL/ExplicitLinks] while resolving link to ControlWithIEDName from LN lnClass="LGOS": found several IED whose name is the start of fake12lDevice1/LLN0.gcb1 on line 248 at line 244

Request
Could RiseClipse try harder to build that link ?

Given the value

fake12lDevice1/LLN0.gcb1

RiseClipse could apply a matching strategy :

• Try to find an IED named "fake1" and then check for an LDevice with instance "2lDevice1" => NO
• then try an IED named "fake12" and check for an LDevice with instance "lDevice1" => YES

If no combination corresponds to a valid (IED, LDevice) pair, then raise the WARNING.

[ADehouck]

Tested, thanks !