Per Nergård (MVP)
+2
Jun 5, 2026
visibility 438
star star star star star
(0 votes)

Automatic assign of content reference properties on content creation

A long time ago I was tired of configuring setting properties on a settings page when deploying new functionality that needed global settings, so I did a way of accomplishaing that with attributes from the settings page.

Earlier this week I got tired of it again and did another version for CMS 13 but this time I did it from the other way around with an attribute on the content type. 

Old blog post here: 2019

So the idea is that when building a new function and we need to configure a settings property to point to a new content type for some shared functionality you could configure that via an attribute on the content type so after deploy you just create your new page and it automatically wires up the setting for you.  Done in an Alloy site so thats why I use StartPage.

Maybe not a super big problem if you just delploying a new features but if setting up a boilerplate solution of some sort from scratch it will make your life much easier.

// Auto-match: the settings property whose [AllowedTypes] most specifically accepts ContactPage is used.
[RegisterIn(typeof(StartPage))]
public class ContactPage : SitePageData { }

// Explicit property: recommended when the settings property allows a broad base type (e.g. PageData).
[RegisterIn(typeof(StartPage), nameof(StartPage.ContactsPageLink))]
public class ContactPage : SitePageData { }

// React on creation instead of publish.
[RegisterIn(typeof(StartPage), Trigger = RegisterTrigger.Created)]
public class ContactPage : SitePageData { }


Code over at my GitHub. Pnergard AutoRegister

Jun 05, 2026

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 |