Great Ideas. Always Flowing.

We are not happy until you are happy. Client satisfaction guaranteed. Whatever your needs and requirements, we have the skills and resources for the job!

Quick login...


Or... now make it easy with Facebook Integration
Connect via Facebook



Top Sellers

Frustrated over the lack of customization for your user's registration fields? Dynamically setup your DNN Portal with custom registration fields, layout, questions, and other core integration options......

Ultra Video Gallery is a brother product of Ultra Media Gallery, UVG allows you to upload videos in various format and automatically encode them to flv or H264 format, you also can add videos from internet or record live videos from your webcam.

Build high performance, completely customizable data-entry forms and views driven by your DNN and external databases. New built-in tools make it a snap to quickly create data entry forms, data views, and even database tables. Plus, add your own HTML, CSS, Javascript, SQL commands, stored procedures,

The most advanced DotNetNuke shopping cart on the planet. Easy to use e-Commerce, Secure Shopping Cart Software and SEO friendly. B2C / B2B Ecommerce Sites.

One stop solution for events calendar and events registration! FREE DOWNLOAD is available now!

Am I missing the obvious?
Last Post 06-11-2007 03:22 PM by Mike Schoonmaker. 2 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Mike SchoonmakerUser is Offline
skipping stones
skipping stones
Posts:11
Avatar

--
06-11-2007 08:30 AM

    I'm struggling with the Dynamic Registration documentation.

    For instance, there is a very short paragraph about core DNN fields and Dynamic Fields, but it doesn't say how many Dynamic Fields can be mapped to Core fields.

    What do I do with the other dynamic fields once I've mapped a single core field to a dynamic field?

    The documentation started off like a well written walkthrough/tutorial, but as you try to get past the repetition of screenshots, the doc content seems to wane quite a bit.

    Am I just thick or what? Perhaps it's just me!

    Mike SchoonmakerUser is Offline
    skipping stones
    skipping stones
    Posts:11
    Avatar

    --
    06-11-2007 03:22 PM
    Still having a problem with this.

    While I can get the SQL statement for the listbox to populate the listbox, and I can get the selection into the DynamicRegistration_QuestionResponse table in the database (I verified this), if I attempt to go to the user's profile, the SQL statements blow away the user's chosen profile settings.

    Others must be having this same issue - so, where are the answers?
    Chad NashUser is Offline
    Posts:5260
    Avatar

    --
    06-12-2007 10:52 AM

    Mike,

    Hi. Much of this has to do with the fact that core fields (and core extended fields) have changed throughout the history of DotNetNuke and therefore Dynamic Registration as well. The real purpose of the core field integration is to keep your Dynamic Registration in sync with DotNetNuke. This isn't necessary except in cases for example where you might use another module to import users and you want them to have their DNN data displayed within Dynamic Registration or if you used the core manage users area or somehow modified the core data without using Dynamic Registration. Because of this we allow the ability to 'link' core fields directly with dynamic fields. This means that every time the user saved their data its saved in both the Dynamic Registration tables and also the core tables. If a field is linked and you change the core fields it will pull those values in instead of Dynamic Registration etc...

    Basically you can link/map as many dynamic fields with core fields as you would like. If you decide not to map a field there is no harm in doing this, only if you wanted to export user data or access that data within the core somewhere and then you might have problems. Modules such as our Dynamic User Directory module support both accessing the core data and the Dynamic Registration data directly so it wouldn't matter for modules like that example but it might matter if you were using another 3rd party tool to manage users with etc..

    Hope this helps with understanding the purpose of mapping DNN fields with Dynamic Fields etc...

    -Chad

    You are not authorized to post a reply.


     
     

    Join our mailing list...

    Get current news and events the easy way
    Subscribe Me

    Recent Blogs...

     
    Copyright 2005 - 2011 by Data Springs, Inc.
     
  • film izle
  • 720 izle
  • film
  • sinema izle
  • film makinesi
  • T�rk�e dublaj film
  • film izle
  • film izle
  • baglan film izle
  • sinema izle
  • 1080 film izle
  • film mercegi