Skip to main content

Are there any special considerations or configuration that must be performed to allow for the usage of longer paths when saving a Message Format as JSON?

I seem to be unable to save a new Message format with Base Message Format as JSON and Path as anything more than 3 characters.  Attempts at longer paths such as /devices causes an error:  

Error

Path (JsonExpression) exceeds the configured maximum length of 3


The Assyst Wiki (assystETM Message Formats:JSON) does not mention any limitations in Path, nor mention how to configure the maximum length. 

Hi Richard, 

I’m afraid this is a bug. The workaround is to not use a Message Format and to just specify the required path in the Channel itself.

 

Paul

Hi Richard, 

I’m afraid this is a bug. The workaround is to not use a Message Format and to just specify the required path in the Channel itself.

 

Paul

Thank you very much for the quick reply

Is there a Problem record associated with this bug, so that we may identify the problem as solved in a future release note, or follow up on the status if needs be?

Reply


Terms & ConditionsCookie settings