SaveItemConfiguration/GetItemConfiguration fails with specific string patterns in Management Client 2025 R3

MIP
, , , ,
1

I’m running into an issue when using SaveItemConfiguration and GetItemConfiguration, and I’m hoping someone can help me understand what’s going wrong.

This happens in Management Client 2025 R3.

Steps to reproduce

  • Save
FQID fqid = new FQID(EnvironmentManager.Instance.MasterSite.ServerId)
{
    ObjectId = Guid.NewGuid(),
    Kind = TestConfigPluginDefinition.TestConfigPluginKind
};
 
item = new Item(fqid, "TestConfigItem");
item.Properties["TestConfigProperty"] = content;
Configuration.Instance.SaveItemConfiguration(TestConfigPluginDefinition.TestConfigPluginId, item);
  • Get
List<Item> items = new List<Item>();
items = Configuration.Instance.GetItemConfigurations(
    TestConfigPluginDefinition.TestConfigPluginId,
    null,
    TestConfigPluginDefinition.TestConfigPluginKind);

Observed behavior

The issue only occurs for certain values of content.

Causes an error

{“Cameras”:[{“Name”:“ABCDEFG 111111-1111-11[1-22]”}]}

{“C”:[{“Name”:“ABCDEFG 111111-1111-11[1-22]”}]}

{[{“ABCD”:“ABCDEFG 111111-1111-11[1-22]”}]}

Works normally (no error)

{“Cameras”:[{“Name”:“ABCDEFG 11111-1111-11[1-22]”}]}

{“C”:[{“Name”:“ABCDEF 111111-1111-11[1-22]”}]}

{“C”:[{“ABCDE”:“ABCDEFG 111111-1111[1-22]”}]}

Question

Does anyone know what could be triggering this?

Specifically:

Is there a known validation/parsing rule that rejects strings containing patterns like 111111-1111-11[1-22]?

Is this expected behavior, or does it look like a bug in 2025 R3?

Any insights (or suggested workarounds) would be greatly appreciated. Thanks!

2

I reproduced your observations. I have reported this to Milestone Development and we will have to await their feedback.

3

A patch for the Management Client is now in testing. I will update you when it is available.