Hoping I can get some advice from the experts on here on how to best approach a certain scenario I need a solution for...
Say, we are currently on a umbraco page which has a property on it and I need to navigate and persist this property value to another page which has a form on it based on a custom model, but also need to still have access to the umbraco content for that document also.
Currently what I'm doing (and is working currently) is when navigating from PageA to PageB I hijack PageB route with a custom controller and action, I grab the value from the query string ie '/PageB?name=Ted', build up a custom view model that derives from RenderModel and pass that to the CurrentTemplate.
Also, on PageB I have an umbraco form (based on the custom model) and post it back to a separate SurfaceController to handle the values.
Does this seem the most effiecient way to perform this task?
Routing Advice Required
Hi Guys,
Hoping I can get some advice from the experts on here on how to best approach a certain scenario I need a solution for...
Say, we are currently on a umbraco page which has a property on it and I need to navigate and persist this property value to another page which has a form on it based on a custom model, but also need to still have access to the umbraco content for that document also.
All ideas and approaches welcome!
Some further info...
Currently what I'm doing (and is working currently) is when navigating from PageA to PageB I hijack PageB route with a custom controller and action, I grab the value from the query string ie '/PageB?name=Ted', build up a custom view model that derives from RenderModel and pass that to the CurrentTemplate.
Also, on PageB I have an umbraco form (based on the custom model) and post it back to a separate SurfaceController to handle the values.
Does this seem the most effiecient way to perform this task?
Thanks again!
is working on a reply...