Ability to enforce a naming rule/validation

The ability to require that objects be created to conform to a specific naming convention has been requested a couple of times.

For example, meters need to follow a convention like M####-## where the # represent a number. The -## may follow a convention of first digit is a 0 if it's a linear meter (pulse meter) and a 1 if it's orifice based. The next digit represent the run number.

The naming convention could be as simples enforcing specific characters or preventing specific characters or spaces in a name.

If the features was enabled afterwards, it would create a list of non-conforming objects so that they could be reviewed and fixed.

Expectation A customer could create a validation rule using something like a regular expression to ensure that the object naming conventions and third party interface requirements are met.
Idea business value This helps enforce consistency and data cleanliness within an organization. It can also help ensure that names meet the requirements for sending data to external systems. For example, Measurement Advisor and Realtime Gas have different requirements for a valid meter name.
Idea Type	Improvement
Idea priority	2 – Limited use to my company

Attach files

Enter a subject

Please enter your email address

RELATED IDEAS

Ability to enforce a naming rule/validation