Sitecore systitle mapping and isFacet sorting
We have some questions about @systitle for sitecore sources:
It seems like @systitle is derived from Item.Name fore sitecore sources. However, throughout our application we use a template with a "Title" field, and would prefer @systitle map to this. The reason is our Title field contains "uncleansed" characters that sitecore strips out when it creates the Item.Name property. Also, we have external data sources for which we have code already using the @systitle field, although the source may not have its own "title" field. We're trying to unite the "title" concept across our sources and @systitle field seemed like the way to go, except it isn't aligned with our true "title" concept in Sitecore. a. Is there a simple config setting we can change to do this, i.e. point @systitle to our Item.Fields["Title"] instead of Item.Name? b. Or could we cause @systitle to be a computed field where we could force it to fall back to Item.Name only if "Title" isn't available for the item? c. Is it possible to use aliases per source? E.g. our sitecore source alias "Title" to "Title" but all our other sources alias "Title" to @systitle?
We need to be able to sort and startswith @systitle. a. Is turning it into a facet field only possible with the admin gui, or is there a way to do it in the config file as with e.g. our computed fields or non-system fields? We try but it doesn't seem to take.
Answer to question 1:
- "systitle" and the "title" Coveo fields should be the same.
- The field which is set as title is not Item.Name, but Item.DisplayName.
- This article might be useful to you.
- Aliases are not supported in C4SC, but this would be a great feature to add, I will request this to the Sitecore team.
Answer to question 2:
C4SC does not edit CES system fields. In other words, you need to configure this field as facet using the administration console. In your Sitecore configuration, ensure that the field is defined in the externalFields section of your configuration if you need to manipulate it from Sitecore side.