Skip to main content
Solved

Error when saving path on assystETM Message Format JSON

  • November 6, 2024
  • 4 replies
  • 41 views
R
Sidekick (Customer)
Forum|alt.badge.img+7

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. 

Best answer by Paul McCulloch

There’s not a problem reference for this. However I can see it is fixed in the latest version (1.9).

View original
Did this topic help you find an answer to your question?

4 replies

P
Hero (Employee)
Forum|alt.badge.img+10

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

R
Sidekick (Customer)
Forum|alt.badge.img+7
Paul McCulloch wrote:

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?

P
Hero (Employee)
Forum|alt.badge.img+10
  • Paul McCulloch
  • Hero (Employee)
  • 67 replies
  • Answer
  • December 2, 2024

There’s not a problem reference for this. However I can see it is fixed in the latest version (1.9).

R
Sidekick (Customer)
Forum|alt.badge.img+7
Paul McCulloch wrote:

There’s not a problem reference for this. However I can see it is fixed in the latest version (1.9).

Thank you very much for the response. 

I’m thrilled to see it fixed, and am looking forward to deploying 24R2 in our test environment.

Reply


Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings