# Naming Standards & Validation Rules

A Dashboard is a visual interface used to display reports, metrics, and analytics for monitoring and decision-making.

#### Validation Rules

<table><thead><tr><th width="235">Property</th><th>Value</th></tr></thead><tbody><tr><td>Blank Allowed</td><td>No</td></tr><tr><td>Max Length</td><td>255 characters</td></tr><tr><td>Allowed Characters</td><td>Alphabets (A–Z, a–z), Numbers (0–9), Spaces, Underscore (_)</td></tr><tr><td>Disallowed Characters</td><td>Any character not matching the allowed regex, including: `! @ # $ % ^ &#x26; * ( ) + = { } [ ] : ; &#x3C; > ? / \</td></tr><tr><td>Start Character Restriction</td><td>No explicit restriction. Name must contain only allowed characters.</td></tr><tr><td>Regex / Notes</td><td><code>^[A-Za-z0-9 _]+$</code></td></tr></tbody></table>

#### Valid Examples

* Sales Dashboard
* Customer\_Insights
* Data Quality 2024
* Revenue\_Report
* Sales\_Report\_2024
* 2024 Dashboard
* \_InternalDashboard

#### Invalid Examples

* Sales\@Dashboard → Contains special character
* Revenue#2024 → Contains restricted symbol
* Data-Quality → Contains hyphen (-)
* Dashboard.Name → Contains dot (.)
* Report/Data → Contains slash (/)
* Revenue!Dashboard → Contains invalid character

#### System Behavior on Validation Failure

* Prevents saving the Dashboard.
* Displays a validation error message.
* Requires correction before saving.

#### Best Practices

* Use clear and descriptive Dashboard names.
* Use underscores (\_) instead of special characters.
* Keep names concise and within 255 characters.
* Maintain consistent naming conventions across Dashboards.
* Avoid unnecessary symbols and punctuation.

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ovaledge.com/release8.1/dashboards/naming-standards-and-validation-rules.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.