3

You need to register your custom field in ~/App_Config/FieldTypes.config. Once done, rebuild the Link Database. From this point on, the field references will get updated automatically when the item updates.


3

Segmentation rules ONLY work against xDB contacts. If you have any properties in the user profile (aka asp.net members profile properties), then this will never work. You need to push those properties to a custom xDB facet. Segmentation rules are just predicates that are added the xDB search query.


2

I have managed to create a solution for that. Please find code below: public class EnumCheckList : Checklist { public string Source { get; set; } protected override void OnLoad(EventArgs e) { if (Sitecore.Context.ClientPage.IsEvent) { ReadCheckedItemsFromRequest(); } else { if (...


1

We had a very similar scenario with a custom image field inheriting from Sitecore Image field. Tried all of the above, without any success whatsoever getting the references added to link database. The way we solved it was to use the namespace for the field we inherit from when registering the field type within <fieldTypes>: <fieldType name="Our ...


1

It turns out that for the Form editor to work, all field type templates must have a standard values. By decompiling the DLL that contains the action for the API controller for the SPEAK interface of the form editor, I found that internally it runs a pipeline, and the first processor has an Assert that throws if the template for the field type does not have ...


1

For this purpose, I would use the iframe field type, which is IMO the most flexible solution for custom field types. You can find more information about the iframe field type here: Cascading Droplist field in Sitecore https://trnktms.com/2017/04/06/sitecore-iframe-field-basics/ The advantege is that you have the full control of the presentation and stored ...


Only top voted, non community-wiki answers of a minimum length are eligible