4

You have to change property type from bool? to bool: public bool PropertyDetailsInOffer { get; set; } bool values will be rendered as checkboxes for supported UI Hints, otherwise rendering as a string value.


3

You can achieve the same using Sitecore PowerShell Extensions to get or modify the items. Reference : https://doc.sitecorepowershell.com/working-with-items You need to write a Script that recurse through the templates tree and get all items. Then you can check value of the the Source field that contains or starts with StartSearchLocation = {11111111-1111-...


3

In vanilla JavaScript, the convention is to use camelCase for field names, and PascalCase for class names. In React, the convention is to use PascalCase only for component names. So to answer your question, I'd recommend camelCase for the actual field names, and utilizing display names for the Content Author's readability sake.


2

No, this is not possible that two items based on the same template will not have the same fields. If you need this kind of items then you need to create two separate templates that can use a single base template with the common fields and specific fields on the template itself.


1

It's a common mistake - you need to assign the Insert Options on the Standard Values for the desired template; never on the template itself. edit: I would reset the Insert Options field on the Home item. Select the item. select the versions ribbon, click Reset. Select the Insert Options field. When you do that, you will undo any custom changes made to the ...


1

Why would you use standard values on SXA page templates? You should use page designs... It is logical that the variants are not found as your template does not live in a site (and your page does) and variants are defined per site. But as mentioned, use page designs: https://doc.sitecore.com/developers/sxa/93/sitecore-experience-accelerator/en/page-designs....


1

Let's say you start with a template like the following: Then the following script will move items to a newly created section like this: Using this sample, you can build in whatever logic you want. Keep in mind that if you are wanting to move fields between templates then you need to change the inheritance first. # Get the template I want to change $...


1

I can at least answer part two of your question, as I had to update that myself. At least on v9.3, the source query for the "Allowed in templates" field is query:$templates|$rvSystemTemplates Specifically, $rvSystemTemplates is driven by configuration. You can add the following config file to get your templates to show up in the list <...


1

Layout service will not do anything with the field names when responding to any item request, you will be seeing field name in JSON response. It's basically our design to define an appropriate name(s) for fields. As per your ex- if you created a field with name "Page Title" then it will be returned as "Page Title". Layout Service will only serialize field ...


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