CGMES. UUIDs with a leading underscore are considered valid master resource ids #2896
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
The issue was raised when exporting an updated SSH of an IIDM network that had valid UUID in its identifiables, but prefixed with an underscore. When the SSH was exported using the
cgmes
naming strategy, these prefixed identifiers were considered not valid and "fixed": replaced by newly created ones. This meant that the references to the original objects in the CGMES EQ instance file were lost.What is the new behavior (if this is a feature change)?
UUIDs with a leading
"_"
character are considered valid Master Resource Identifiers.A specific unit test to check the scenario where the issue was first raised has been added.