I tried to reproduce. I get a consistent behavior: If the ShortcutDefined is true there is a shortcut in Smart Client, Management Client or anywhere I look. if the ShortcutDefined is false there is no shortcut anywhere I look.
I wonder if the error was in the old VMS not the Configuration API / SDK.
My theory is-
In current MIP SDK version the Configuration API returns on Shortcut a default value “0” instead of null or undefined, there is no way the value returned can be “”.
If the older VMS interpreted Shortcut “” as a valid value that should mean that ShortcutDefined should be ignored, then the observations makes sense..
An easy workaround would be that if Shortcut is “” or 0 then ShortcutDefined should be set to false and Shortcut to 0.
I have no XProtect 2024 R1 test setup, but can set it up if necessary. if my theory fits your observations and testing I hope you will go with that.
You tested a newer MIP SDK but still use XProtect 2024 R1, correct?