What are the alternatives to developing two DotNetNuke modules differing only in the back end business process?

In a custom system development the client wanted me to develop two separate modules. However these two modules are similar (in UI and nature of data displayed each is basically listing a set of records); they both differ only on the data queried, i.e. the criterion of data fetch is slightly different.

So I thought of developing a single module and allowing the DNN administrator to configure the module in a page with settings that depended on how she/he wanted data in the page.

1. However I am not sure that my thoughts are correct. Is this really possible? How should it map to the DNN architecture?

2. Is there anoth开发者_开发技巧er alternative you may suggest? I don't really wish to develop a whole module just for the purpose of a change in query. It won't help my client or me.

Yes this is possible you can just set a property in the module settings on the preferred action the admin wants at that specific time.

Have you looked at the reports module that ships with DotNetNuke, it covers what you seem to require. Alternatively you could implement templating as a module setting, which would allow you to install 2 different instances of the module, or even just one and copy it (module settings are indpendant)