Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesmodules referencing another modulemodules referencing another module's data
Previous
 
Next
New Post
12/22/2009 4:04 PM
 

Can one module save a record with a foreign key to a record in another module's table?

For example, I have an Events module on a page and I have saved a bunch of races on the calendar.

I'd like to write a module that allows the logged in user to select one of the events entered on the calendar and record a result for that event, then show a list of all their entered results.

I understand that modules are meant to be modular and perhaps this goes against the design philosophy of DNN, but it seems like I should be able to do this (it works for user data, right?), I'm just not sure where I would start.

Can anyone suggest a way to make this work, or perhaps a different way to go about it?

 
New Post
12/22/2009 6:20 PM
 

 The Event module lets you put HTML into an event description, so there's no reason why you couldn't format that link any way you like... including to a landing page where your "personal results" application would be.  I've used this technique on several things using the Reports module, where I provide links to a page with and instance of the reports module that looks for a query string parameter specifying the userid, but will default to the userid of the logged in user if not there (ie. navigated to directly).


Scott Willhite, Co-Founder DNN

"It is only with the heart that one can see rightly... what is essential is invisible to the eye. "
~ Antoine de Saint-Exupéry

 
New Post
12/22/2009 6:47 PM
 

sure you can create a custom module with any data reference, even to existing modules, however, this is NOT recommended, due to upgrade issues, if the base module changes its data structure and the FK reference interferes with the upgrade. you should rely on the business layer of the other module and your module should clear references in business layer - this would work even with both modules using different data stores.

However, be aware, that modules, other than the DNN framework itself, do not necessarily provide version backwards compatibility, because this is a quite rare use case. I.e. you should test your module with any new version explicitely


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesmodules referencing another modulemodules referencing another module's data


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out