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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0MS CRM User Registration IntegrationMS CRM User Registration Integration
Previous
 
Next
New Post
6/12/2006 2:14 PM
 
Hi everyone... I need to integrate the user registration of MS CRM 3.0 into DNN 4.x. Everytime a user registers or updates their profile we need to add/modify the CRM DB. What should we do? Should we have triggers? Should we create new authentication/profile modules that connects to the MS CRM DB? Any help appreciated...
 
New Post
6/13/2006 5:53 PM
 
Depending on your actual requirements you may consider these two options:
- create a new register module and do all the extra stuff just there. Take the base register.ascx code as a template and modify and enhance as you need.
- if you need much more control on the whole process you should consider creating your own membership provider. If you just need to plug some code in specific events (add, update) you can use again the default provider as a template. Or even just inherit from it and modify the parts you need to change.
Finally set the new provider as the default one in web.config.



Vicenç Masanas
Banyoles, Girona - Spain

Disgrafic.com    PSD to DNN
 
New Post
6/13/2006 6:12 PM
 

This topic is more MS CRM related than DotNetNuke and MS CRM is so complex. If MS CRM is like Lego(R) , DotNetNuke will be more like Duplo(R).

I am developing on both platforms but never thought on integration. You want to access and modify CDM db? Download the SDK and start reading. You should  never touch any of the SQL data inside CRM! Don't ever think about.

Saying that you will like to know hat the CRM 3.0 development is extremely powerful using webservices. I love it. You could access and modify all entities inside using its interface.

CRM depends on Active Directory. So if you setup DNN with the ActiveDirectory connector you will be able to create something like a SingleSignOn. So somebody will be able to write a suitable module for you.

I think you might want to use DNN as a Customer FrontEnd? There is no technical barrier though you must setup an connector user and use its credentials as an general connector to CRM like you are used with SQL Connection Strings. Please note that this setup might violate your CRM licenses, you will need ONE CRM license for every user (=real person) which reads or writes to MS CRM even if he just visits DNN.

 
New Post
6/14/2006 10:04 AM
 
Thanks for all the help. I do not want to use single sign on. DNN is the customer front end and we use CRM as our internal app. All we want is to have either a centralized db for customers or synchronized versions of it. By what you told me I think we're going to go with the web services which will require me to change DNN code, something I was trying to avoid. That is why I asked about DB triggers. Thanks again...
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0MS CRM User Registration IntegrationMS CRM User Registration Integration


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