Naming Standards & Validation Rules

Data Catalog Objects represent technical metadata assets used for data discovery, governance, lineage, and analytics. These objects include Databases, Tables, Table Columns, Files, File Columns, Reports, Report Columns, APIs, API Attributes, and Codes.

Validation Rules

Property	Value
Blank Allowed	Yes (null allowed)
Maximum Length	Not explicitly specified
Allowed Characters	Alphabets, Numbers, Spaces, and any characters except disallowed characters
Disallowed Characters	Comma (,) and configured concatenation delimiter
Pattern Validation	No strict regex validation enforced
Null Value Behavior	Validation is skipped when the value is null

Examples

Valid Examples

• Customer Database

• Sales Table 2024

• Employee Report

• API Response Data

• File Column Name

• PII Code

Invalid Examples

• Data,Object → Contains comma

• Table|Column → Contains configured delimiter

• Code,Value → Contains comma

System Behavior on Validation Failure

• The system prevents saving the object when validation fails.

• Validation error messages are displayed.

• Correct the object name before proceeding.

• If the value is null, validation is skipped.

Best Practices

• Use meaningful and descriptive object names.

• Maintain consistent naming conventions across objects.

• Avoid commas and configured delimiters.

• Follow organizational metadata naming standards.

• Use standardized names for better search and governance visibility.

---

Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA