Hey Guys,

This module looks great and I have gone through the user module. I am almost ready to jump to start development using this module but I have few unanswered questions, If anybody can help me giving some insight it would be a great help. So here are my questions.

1) How are the UDT data are stored? Is it XML or RDMS style schema? When I say data I mean the actual data for instance Firstname: myFname, Lastname:  myLName

2) Once data are entered for multiple UDTs for instance Order and Order details, can I have a report using joining multiple UDTs? Can I show report with order and its details, total , subtotal etc. I am asking this question bcoz I am that familiar with XSLT.

3) Once UDT is created for instance Order, Can I modify the entry form the way I like it rather than using the default style?

4) Can we separate UDTs between portal/sites? For instance Site1 - > order UDT has 5 columns and for Site2 Order UDT has 15 columns

Any help would be much appreciated.

Thanks,

Thanks Sebastian for your response.

Looking at current data structure, joining UDT functionality would be difficult to provide.And unavailability of this feature makes UDT unusable for bigger application where multiple entites have to be linked to provide meaningful module.

I am not sure why approach is taken to store all UDTs data in a single table. This means all UDT data would flood one single table and app performace would be drastically affected within no time of app age.

But thanks anyway for your response. Good work keep it up.

As you correcly said its best suits for data collection sites. What I mean by big site is sophisticated site. Writing own module is one of the options but if there are addition of fields to your table you need to change your module and redeploy it again. For instance we have order system when today we have 10 fields to be captured and we developed our own module to support these 10 fields, now for another portal we need exact similiar order system but order should capture 20 fields. Now to sufice this we need to change our module but the crux is the first oder system should not be affected. When I say order system its just not order table but there are other tables involved.

I fully appreciate your effort for UDT but in the scenarios what I just mentioned it doesnt fit. I would appreciate if you have knowlege of any other approach or module within DNN which fits on above requirements.

Thanks.