Umbraco v14+ Known Issues and Gotchas

This page documents known issues and gotchas that practitioners encounter when working with Umbraco v14+, along with workarounds and fixes.

Issue 1: PropertyValidationService Duplicate Property Errors

Symptoms: After migrating from v7 to v8 to v13 to v14, saving Document Types fails with validation errors about duplicate properties.

Root Cause: Older migrations created duplicate properties in Document Types. v13 allowed this, but v14’s PropertyValidationService enforces uniqueness.

Fix: Identify and remove duplicate properties before upgrading to v14.

SQL Query to Find Duplicates:

SELECT cmsPropertyType.contentTypeId, cmsPropertyType.Alias, COUNT(*)
FROM cmsPropertyType
GROUP BY cmsPropertyType.contentTypeId, cmsPropertyType.Alias
HAVING COUNT(*) > 1

Issue 2: Block Grid Custom Views Not Fully Supported Until v14.2

Symptoms: Custom views for Block Grid blocks don’t work as expected in v14.0/v14.1.

Root Cause: Bellissima requires Web Components for custom block views. Full support delayed until v14.2.

Workaround: Use default Block Grid rendering until v14.2.

Status: Fixed in v14.2+

Issue 3: Umbraco Forms Migration v8 to v10+ Challenges

Symptoms: Forms created in v8 don’t migrate cleanly to v10+, losing field configurations or workflows.

Root Cause: Umbraco Forms schema changes between v8 and v10+.

Workaround:

1. Export forms as JSON in v8
2. Manually recreate in v10+ (schema incompatibilities prevent automatic migration)
3. Test all form workflows, notifications, and conditional logic

Issue 4: Azure + Examine File Locking

Symptoms: On Azure Web Apps, Examine indexes experience file locking issues, causing search failures.

Workaround: Use SQL-based Examine indexes instead of file-based Lucene indexes on Azure.

Issue 5: Large Content Trees (10,000+ nodes) Performance

Symptoms: Backoffice performance degrades with content trees exceeding 10,000 nodes.

Workaround:

• Organize content into folders
• Enable List View for large sections
• Use child action filters to limit tree node expansion