Data Sets Validation – Feature Toggle
This page explains how the Data Sets Validation Feature Toggle lets you remove certain backend label restrictions—such as blocking spaces, special characters, or uppercase letters—so labels can match
What is the Data Sets Validation Feature Toggle?
By default, Data Sets backend labels are restricted to:
Only lowercase letters (a–z)
Only numbers (0–9)
No spaces
No special characters
No uppercase letters
The Data Sets Validation Feature Toggle allows you to selectively remove these restrictions, making it easier to match your backend labels to your preferred formatting.
You can disable one, some, or all of these validations as needed.

How it Works
This setting is configured by our Support team. If you need any of the default validations removed, please contact Support and specify which rules you would like disabled.
Available options:
Spaces – allows spaces in backend labels
Special Characters – allows symbols such as &, %, @, _, -
Upper Case – allows capital letters
Note: Even with validations removed, duplicate keys work as normal.
You cannot create two values that are exactly the same in casing (e.g. value and value).
You can create two values with different casing (e.g. value and Value).
Removing default validation can introduce system-to-system integration risks:
Special Characters
Certain symbols may cause issues when values are sent to, or stored in, other systems:
Ampersand (&) – can break URLs or query strings without proper encoding
Percent (%) – may be misinterpreted in URL encoding
At symbol (@) – sometimes reserved for email/username parsing
Hash/Pound (#) – can truncate URLs or cause fragment misinterpretation
Forward/Backward Slash (/ or \) – may be treated as directory separators
Quotes (", ') – can cause parsing errors in JSON, XML, or SQL strings
Angle Brackets (<, >) – may be flagged as unsafe HTML
Equals (=) – can disrupt key/value pair parsing
Spaces (Especially Leading or Trailing)
Leading or trailing spaces are visually hard to detect but can cause mismatches between systems
They can break search, sorting, or matching logic
May require special handling in APIs or ETL processes
Uppercase Letters
If the receiving system is case-sensitive, changing case rules could result in duplicate or conflicting records
May cause unexpected matching failures
Best Practice
We recommend keeping backend labels strictly alphanumeric, lowercase, and without spaces unless:
There is a confirmed business requirement
All integrated systems have been tested to handle the chosen characters and formatting safely
Example Scenarios
Scenario
Validation Rules Removed
Before (Default)
After (Toggle Enabled)
Allow spaces only
Spaces
❌ new value
✅ new value
Allow special characters + uppercase
Special Characters, Upper Case
❌ NEW_V&LUE
✅ NEW_V&LUE
Allow all validations
Spaces, Special Characters, Upper Case
❌ Project &X 2025
✅ Project &X 2025
✅ = Allowed
❌ = Not allowed
How to Request This Change
Please raise a Support ticket including the following details:
Subject: Request to Enable Data Sets Validation Feature Toggle
Body:
Last updated

