Databases
StackOverflow2013
Postsdbo
POIdetification between multiple DotNetNuke module definitions
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIdetification between multiple DotNetNuke module definitions
    text
    copied!<p>I have build a module in DotNetNuke 6 that contains multiple module definitions. A module can be added on multiple pages (tabs) and multiple module can be added to one page (tab). Problem is that I can't find an identifier that ties all my module definitions together from one instance.</p> <p><code>DesktopModuleId</code> is only unique for every module installed (not per instance and page).</p> <p><code>ModuleId</code> is unique for every module instance <strong>and definition</strong>.</p> <p><code>TabModuleId</code> is unique for every module instance and tab <strong>and definition</strong>.</p> <p><em>So what I'm looking for is a way to identify which module definitions belong to each other the moment I put a module on the page.</em></p> <p>I found a forum post which explains the same problem and someone suggested to look at the <code>ModuleId</code> for every definition and check if they are sequential. I find that very hackies.</p> <p>Edit:<br/> The module I'm developing contains a number of different definitions, but let's say we have 3 (view, edit and settings). When I install the module I have to set a category I'm gonna use for the module, say I want it to be a blog module. All 3 definitions will then get data from the database with their same unique id (supposedly). Now I install again the same module, I want to choose another category (portfolio) and only get that data. The way DNN works now, I can't separate my blog items from my portfolio items as there's no way to know that my 3 blog definitions belong to each other and are separate of the other 3 portfolio definitions. I hope this make sense...</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload