Hi,

It's GREAT that in v3.0 there is some ability to control the relationship
behaviour. Specifically, the abiltity to specify how child tables cascade
changes to the parent ownership. However, it appears that a key option is
missing - the combination of Cascade Active and Cascade Owned.

Example, I have an account owned by Bob, which has:
- Task 1 - Active - Jane
- Task 2 - Active - Bob
- Task 3 - Closed - Bob

I change the account owner to Bill. With a Casade Active relationship with
tasks, the result is:
- Account Owner - Bill
- Task 1 - Active - Bill (Wrong)
- Task 2 - Active - Bill (OK)
- Task 3 - Closed - Bob (OK)

The issue is that Jane's task is now assigned to Bill. This is not
appropriate because the task is truly something that Jane should do.

So then you try the whole thing with the Cascade Owned relationship,
resulting in
- Account Owner - Bill
- Task 1 - Active - Jane(OK)
- Task 2 - Active - Bill (OK)
- Task 3 - Closed - Bill (Wrong)

This situation sees us losing the history of who originally owned the task.

So in reality what is needed is a Cascade Active Owned, which will result in:
- Account Owner - Bill
- Task 1 - Active - Jane
- Task 2 - Active - Bill
- Task 3 - Closed - Bob

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/Businesssol...oft.public.crm