title: What are the alternatives to developing two DotNetNuke modules differing only in the back end business process?
body: <p>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.</p>
  
  <p>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.</p>
  
  <ol>
  <li><p>However I am not sure that my thoughts are correct. Is this really possible? How should it map to the DNN architecture?</p></li>
  <li><p>Is there another 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.</p></li>
  </ol>