Hi Qamar

I still may have misunderstood what you are trying to achieve, but if we focus on route hijacking, that looks closest to what you have so far - you can find some more information about route hijacking here: https://our.umbraco.com/documentation/reference/routing/custom-controllers

Essentially you need to create an MVC controller that inherits RenderMvcController, with a name matching the convention documenttypealiasController, where documenttypealias matches the alias of the document type of the page you want to hijack.

So first question is do you have a Document Type called: ApqcrDirSearch ?

With this controller in place, matching this convention, When you request a url for your search page, Umbraco will look on the controller for an Action that matches the 'template' name that the page is published with.

So second question is do you have a template called ApqcrDirSearch ?

(if it doesn't find a matching action to the template it will call the default Index action)

The 'Action' on your hijacked MVC controller needs to return an ActionResult, what the default RenderMvcController is doing for all non hijacked routing requests is:

  public ActionResult Index(RenderModel model)
    {
        return CurrentTemplate(model);
    }

So for your custom hijacking of the route you need an action method that accepts the RenderModel parameter (Umbraco will populate this with all the properties of the page you are hijacking), you can use this to create your new ViewModel, enrich the model with your list of search results, and then pass this model to your view via the CurrentTemplate helper..

eg

      public ActionResult ApqcrDirSearch(RenderModel model, string ID, string lname)
        {
// create your new view model
ApqcrDirSearchViewModel vm = new ApqcrDirSearchViewModel(model.Content);
// populate the SearchResults property from your sql query..
//etc
//vm.SearchResults = ...
// send the model to the view
            return CurrentTemplate(vm);
        }

So now we need to tell your view to expect a model of type ApqcrDirSearchViewModel otherwise we get the error that it was expecting the default RenderModel...

@using USNStarterKit.USNModels
@inherits Umbraco.Web.Mvc.UmbracoViewPage<ApqcrDirSearchViewModel>

now the Model property inside your view will have a SearchResults property containing your search results.

@foreach (var searchResult in Model.SearchResults){
// loop through the search results
}

1. It's ok to create the model and controller in the same folder as the existing ones. (Often you'll create them in a separate class library project but that is a whole different topic of conversation to worry about when you have it working)

2. Your template is your view, when you have

   return CurrentTemplate(vm);

Umbraco will look to see which template the page is published with and send the model to that view, if you want to instead divert it to a different custom view you would need to return this explicitly eg

return View("~/Views/ApqcrDirSearchView.cshtml",vm);

(I'd stick with the CurrentTemplate approach for now)

Main thing is whichever view you end up using you need to tell it which model is coming it's way, so make sure you have:

@using USNStarterKit.USNModels
@inherits Umbraco.Web.Mvc.UmbracoViewPage<ApqcrDirSearchViewModel>

at the top of the view, so that it matches the ApqcrDirSearchViewModel you are sending to it from the controlller.

is working on a reply...