Closed ritchiecarroll closed 3 months ago
I guess this still doesn't fix the case where you update the device names manually.
I guess this still doesn't fix the case where you update the device names manually.
No, guess not. However, in this case at least the record is highlighted as a duplicate / already existing, so there's user feedback on record being duplicated.
I'll see if I can handle this use case as well.
I guess this still doesn't fix the case where you update the device names manually.
This should do it: https://github.com/GridProtectionAlliance/gsf/pull/261/commits/32c1b9a90c4a5bf9fe0ca5b1031d4cae8bf7d803
Any "new device", by manual entry or otherwise, gets unqiue ID vallidation.
Fixes "Violation of UNIQUE KEY constraint 'UK_UniqueID'" for config frames that contain existing device acronyms and user selects "Use Source Prefix", which makes device acronyms unique, but was using UniqueID from existing device acronym.