What are orphaned properties?
Properties in the Availability Search Engine can have a hierarchical structure- a parent property with child properties beneath it. For example, a holiday park might be a parent property with individual lodges or pitches as children.
An orphaned property is a child property whose parent has been removed or is no longer present in the data coming from the Availability Search Engine. Because the child's parent no longer exists, the CMS cannot place it correctly in the hierarchy.
Where to see orphaned properties
Orphaned properties appear in a dedicated Orphaned view within Availability Search > Properties. If you have any, they will be listed there.
What to do about them
Orphaned properties are handled automatically during a sync according to the system's configuration. Depending on the setup, the CMS may attempt to re-attach them to a new parent, promote them to stand-alone properties, or move them to the trash. You do not usually need to resolve orphans manually.
If you are seeing a large number of orphaned properties, or entries that were linked to properties are no longer resolving correctly, contact DestinationCore to review the sync configuration.
An orphaned property is a child property whose parent has been removed or is no longer present in the data coming from the Availability Search Engine. Because the child's parent no longer exists, the CMS cannot place it correctly in the hierarchy.
Where to see orphaned properties
Orphaned properties appear in a dedicated Orphaned view within Availability Search > Properties. If you have any, they will be listed there.
What to do about them
Orphaned properties are handled automatically during a sync according to the system's configuration. Depending on the setup, the CMS may attempt to re-attach them to a new parent, promote them to stand-alone properties, or move them to the trash. You do not usually need to resolve orphans manually.
If you are seeing a large number of orphaned properties, or entries that were linked to properties are no longer resolving correctly, contact DestinationCore to review the sync configuration.