Hi All,

It looks like "form And Lists" standard DNN module is a very good candidate to make custom forms to handle lookup data and small production tables. Is that approach described somewhere already?

Still an issue with localization exists (am I missing something?): it would be useful for this "form And Lists" module to have ResourceKey defined for custom fields' labels, help strings and custom fields' grid header captions. Then  localization values can be defined in SharedResource but it would be better to have localization resources to be defined in

...\DesktopModules\UserDefinedTable\App_LocalResources\CustomModules\{{ModuleName}}

and for every {{ModuleName}} folder to have defined several custom resource files for used locales, e.g.:

- system.resx (deafult system locale)

- ru-RU.resx - Russian

- nl-BE.resx - Dutch (Belgium)

- pt-pt.resx - Portugal

etc.

That  method of keeping and using localization resources would be also useful IMO for modules as XMODPro etc.

As for using "form and Lists" data as lookup tables - that should work well provided there will be additional "form And List" table defining moduleId and lookup table name of individual lookup "form and List" tables and then custom UDFs/views can be developed to simulate true flat custom lookup tables...

"Reinventing the wheel"? Is that approach already broadly used in DNN community and described somewhere? Please post then the links on that info here.

Thank you.

--Shamil

OK, Sebastian. I should have been more accurate with this thread subject line - I intended to use "form And List" AKA UserDefinedTable but misspelled the subject line.

<<< please do not mix up FnL (aka UDT in DNN3 and 4) with lists core feature. Lists is designed to be a simple id-value lookup table with parent >>>

I'm not sure I understand what "lists core feature" do you mean? - I mean there is no "Lists" module in DNN5.1.4 I use. Do you mean by "lists" just a concept/principle of organizing simple id-value tuples' set into lookup tables? What other type of parent tables lookup tables could have except possible parent table defining lookup table type in the case all(/most of the) lookup tables' data are "packed" into two generic tables' rows?

Thank you.

--Shamil

OK, I see it now, thank you for the hint (so much to learn and develop in DNN in so short time - I still do not have the whole true picture of DNN admin and host UI).

AFAIS there is no export/import actions for this module (DNN 5.1.4) - so I will just use bcp out/bcp in or other data export/import methods to transfer DNN's Lists tables' data from my development system to my production system...

And if those Lists could be ever possible to use as a source for "form And List" forms' fields (e.g. a la' MS Access combo-boxes) that would be really useful. I checked and I do not see such a feature currently implemented.

Thank you.

--Shamil