Ritu Madan
+4
Jan 17, 2024
visibility 2171
star star star star star
(0 votes)

Custom form element with dependencies

Episerver Forms are cool as is. They provide solid ground to build basic forms out of the box. But often times, we have custom needs that require us to customize or add to the out of the box functionality.

In my case, I needed a custom form element that can support some unique requirements and at the same time I needed this to support the built in dependency logic.

For those of you unfamiliar with the forms dependency logic, see the Optimizely document here.

Read the complete blog here for all the fun details on how this was achieved with minor code tweaks.

Jan 17, 2024

Comments

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |