Forum Discussion
1 Reply
- Former Member
In Enterprise Search configuration, if the native_file property of the Part item type is linked to the File item type, but discovery paths are only configurable for relationships, you have a few options to achieve the desired configuration. Since Enterprise Search allows configuring the discovery path for relationships but not for direct properties, the best approach is to replace or supplement the native_file property with a relationship between Part and File.
-
Create a Relationship Between Part and File
- Instead of (or in addition to) using
native_fileas a property, define a relationship between Part and File. - For example, create a relationship like
PartHasFilethat linksParttoFile.
- Instead of (or in addition to) using
-
Configure the Discovery Path for the Relationship
- In the Enterprise Search Configuration, configure the discovery path to traverse from Part to File through this new relationship.
- This way, the search engine will properly index the
Fileitem type for the correspondingPart.
-
Keep the
native_fileProperty (If Necessary)- If the
native_fileproperty is still needed for other functionalities, keep it. - Ensure that the relationship is kept in sync with this property using a business rule or workflow.
- If the
If modifying the schema by adding a relationship is not an option Slice Master, another possible workaround is using a computed property that dynamically retrieves the linked
Filebased on thenative_fileproperty.Steps to Implement a Computed Property
- Define a computed property on the Part item that retrieves the linked
Fileitem. - Ensure that Enterprise Search indexes this computed property.
- Configure Enterprise Search to use the computed property instead of a relationship.
-