Invalid Node Names Behave Inconsistently

This forum allows users to post and respond to "How Do I Do ....." questions. The information contained in this forum has not been validated by K-Rise Systems and, as such, K-Rise Systems cannot guarantee the accuracy of the information.
Post Reply
JefferyD
Posts: 178
Joined: August 31st, 2021, 11:37 am
Contact:
Contact JefferyD

Invalid Node Names Behave Inconsistently

Unread post by JefferyD »

Service names prevent a lot of invalid characters, but one thing they do allow are invalid first characters.

For example, numbers and hyphens are not valid as the first character of a node name.

When using invalid names for services like "2CSN2" or "-CSN-b", the invalid characters seem like they are escaped upon execution to be "_x0032_CSN2" and "_x002D_CSN-b" respectively.
image.png

When using the assistant for referencing those services however, it provides the unescaped version which then causes other errors.
image.png

When using invalid names for services parameters like "1param", no escaping happens at all.
image.png

Invalid service parameter names cause parsing errors that can be seen in the logs.
The log image also shows how the invalid service names were escaped.
image.png
word count: 123
Tags:
Bug
Top
SteveCap
Posts: 329
Joined: August 26th, 2021, 9:18 am
Contact:
Contact SteveCap

Re: Invalid Node Names Behave Inconsistently

Unread post by SteveCap »

Task #11300 has been created. This post will be updated when it has been completed.
word count: 15
Top
Post Reply

Return to “General Forum”