Other: HVR - Increase Max Number of character for naming channels and location
The more we are adding new channels and locations in our hubs, the harder it is to find 12 characters understandable and meaningful names.
Could you increase the max number of characters for those names?
-
Hi Caroline,
Historically the channel and location name(s) are used - combined with a prefix, and separators - to create HVR state tables. The state tables are the basis for loop detection, and may be useful for support or even regular maintenance cases. As these objects become database tables we have restricted ourselves to the shortest table name databases support (30 characters).
Before HVR 6 we used to limit the location name to 5 characters, with channels up to 12 characters. For HVR 6 - by changing some of our naming rules - we extended location names to allow for 12 characters, whilst keeping the channel name to 12 characters. Extending this would mean we either end up with hard to track state tables in the target, or run into problems naming the tables on some databases. Either way this would be a very extensive change that we are not prepared to do.
I recommend you come up with a naming convention for the 12 characters we allow, and use the description field to clarify the location or channel name.
Mark.
Please sign in to leave a comment.
Comments
1 comment