Roman Hutnyk

Roman Hutnyk Bits Orchestra

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.

Roman ranks #2 in the community leaderboard with total of 4104 reputation points.


Editing Custom Module Data - Part 2

Roman Hutnyk    —       —    Article

Recently I've shared an idea of how you could provide live site users with edit interface for custom module data. As you might know, perfection has no boundaries... This time I want to share some improvement, those will allow you to reuse the same web part for literally any object within your application.

REST Service Proxy

Roman Hutnyk    —       —    Article

Kentico provides us with REST service which is extremely handy when building Single Page Application or native mobile app as it allows us to retrieve any kind of data we need and goes even further than that - allows to manipulate that data creating new or editing existing objects or pages, applying workflow actions to a page, etc. However there are cases, where REST almost covers our needs. In this post I'm going to introduce an approach that might help you to hit your target.

Editing Custom Module Data on the Live Site

Roman Hutnyk    —       —    Article

Despite the fact that Kentico provides nice interface for managing data inside of the custom modules, sometimes there is a need to provide user to do so on the live site. There are appropriate web parts for editing pages, working with online forms or custom tables, but I couldn't find any control that provides similar functionality for custom module class. In this post I want to share with you solution I found.

Building a parent-child relationship with forms

Roman Hutnyk    —       —    Article

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

Custom Table vs Module

Roman Hutnyk    —       —    Article

Recently I attended Kentico South group micro summit. During one of the presentation interesting discussion has appeared: which one is it better to use - Custom Table or Module class. There were different opinions as well as arguments for or against each of those approaches.

After Kentico introduced custom Modules in version 8, I liked this feature and use it a lot. However Kentico did not removed Custom Tables and, I believe, there was some good reason behind this. So I decided to investigate that reason and give you "apple to apple" comparison.


See all Authors