?
Solved

Queries on Relationships in MS-CRM

Posted on 2010-11-26
1
Medium Priority
?
649 Views
Last Modified: 2012-05-10
Hi,

I have following queries about relationships in MS-CRM

1) It is said when 1:N relationship is created between system entity and custom entity it is called as parental relationship and if 1 to N relationship is created between Custom entity and System entity it is called as referential relationship. My quesiton is what difference the concept of parental and referential relationship make in terms of functionality

2) There are certain unsupported entity relationships they are 1 to Many customer and 1 to 1 and any to any. It is said Only Opportunity or case has to be associated with accounts or contacts. Is it not possible to associate any other custom enities to account or contact using relationship i am not clear in this point

3) What is cascade userowned behaviour?

Could any of you anwer these queries
0
Comment
Question by:PrasadSKLN
1 Comment
 
LVL 30

Accepted Solution

by:
Feridun Kadir earned 2000 total points
ID: 34216382
In a 1:many relationship there are cascading rules which define what happens to child records when an action is taken on the parent record. For example, an account can have many contacts. If an account is deleted what should happen to the contacts? This is called the cascading behaviour.   For each of the possible actions, there is an option as to what should happen. For example, for the delete action you can choose cacade all which means that all contacts linked to the account will be deleted. Or you could choose Cascade User Owned, which means that if the account is deleted, only the contacts owned by the user is deleting the account will be deleted.

There are pre-defined definitions of cascading behaviour. One is parental which sets all the cascade actions to All - so if an account is deleted then all contacts are deleted. Another one is referential which means if an account is deleted, don't delete the contacts but remove the link in Parent Customer to the account (which has been deleted).

When you create a relationship you can define whether the relationship behaviour is parental, referential or configurable. There are some restrictions in that if you create a 1:many relationship between a system and a custom entity then the behaviour cannot be parental.

With regard to the customer entity , this is a special virtual entity where when a users chooses a parent customer they can choose either an account or contact as the parent customer. You can't create relationships that offer this choice.

Opportunities and cases can have custom entities linked to them.

Hope this answers your questions.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Article by: Leon
Software Metering within our group of companies has always been an afterthought until auditing of software and licensing became a pain point. Orchestrator and SCCM metering gave us the answer and it was an exciting process.
Deploying a Microsoft Access application in a Citrix environment is not difficult but takes a few steps. However, Citrix system people are often of little help, as they typically know next to nothing about Access. The script provided here will take …
Viewers will learn the different options available in the Backstage view in Excel 2013.
The viewer will learn how to create a normally distributed random variable in Excel, use a normal distribution to simulate the return on an investment over a period of years, Create a Monte Carlo simulation using a normal random variable, and calcul…

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question