We had a similar issue with a solution we were building. We had some venue models that had a list of courses that referenced that venue. When indexing the list would update with what courses were at that venue. However, when we updated any of the courses, the list did not update.

To get around this we have an event initializable module that hooks into the publish event and checks to see if the item being published is one of the types that needs to update the referenced courses. If it is it will work out what model needed to be updated by getting the content reference (or list of them) and force a re-index of the venue.

Here is an example:

private void FindEventIndex(ContentEventArgs e)
{
    var itemType = e.Content.GetOriginalType();
    var basePageMatchType = new[]
    {
        typeof(CourseBaseProduct),
        typeof(CourseVenueProduct),
        typeof(CourseScheduleVariant)
    };

    if (itemType.InheritsAnyClass(basePageMatchType))
    {
        var contentRepository = ServiceLocator.Current.GetInstance<IContentLoader>();
        var content = contentRepository.Get<IContent>(e.ContentLink);
        Task.Run(() => CourseReindexingService.Service.ReindexReleatedVenues(content));
    }
}

Then this will run a service that will update the venue in the index using the following code:

public async Task ReindexReleatedVenues(IContent contentObject)
{
    var itemType = contentObject.GetOriginalType();

    if (itemType == typeof(CourseScheduleVariant))
    {
        try
        {
            var courseScheduleVariant = ContentLoaderService.Service.Get<CourseScheduleVariant>
                (contentObject.ContentLink);

            if (!ContentReference.IsNullOrEmpty(courseScheduleVariant.ParentCourseVenueProduct.Venue))
            {
                var relatedVenue = ContentLoaderService.Service.Get<VenueContentItem>
                    (courseScheduleVariant.ParentCourseVenueProduct.Venue);

                if (relatedVenue != null)
                {
                    FindClientService.Service.Index(relatedVenue);
                }
            }
        }
        catch (Exception ex)
        {
            LoggerService.Service.Log(Level.Error, "Failed to index a single venue from a schedule variant.", ex);
        }
    }
}

I don't know if this is something that you would want to do but this is the way we got around the issue. It does mean that it will re-index the specified item in the index and the information will be up to date though

Hi Steve,

Thanks for your info. I will check if this can work for me. Acting on the publish event is a good idea anyway.

I'm not sure if the model I'm using allows me to retrieve the products related to a segment yet, but I guess I will find out :)

I'll let you know the outcome.

Thnx,

Pierre