Building a parent-child relationship with forms


In this post I'd like to walk you through a process of building parent-child relation with the forms. Those, who know Kentico and available range of features could ask absolutely obvious question: why would I build parent-child relation with forms while there are modules, or, at least, custom tables? I can see two good reasons for doing this:

parent object is already created and there is cost related with conversion it to a module class
it allows non-technical users, such as content editors, creation of the parent-child data structure

Read more in Roman's blog

Share this article on   LinkedIn Google+

Roman Hutnyk

Kentico enthusiast and MVP, Solution architect at Bits Orchestra. I'm working with Kentico since version 5.5 R2. I'm always looking for advanced solution and best practice. Feel free to contact me in case of any questions you have.