Bhuvarahan / npsp

Automatically exported from code.google.com/p/npsp
0 stars 0 forks source link

Once a Contact gets a one-to-one Account, that can't be changed to a new one-to-one Account #132

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Create a new Contact with no Account
2. Edit the new Contact, changing the Account lookup to blank
3. See that the Account field gets filled in with the existing one-to-one 
Account

What is the expected output? What do you see instead?

If a Contact gets created in the wrong one-to-one Account, it would be nice to 
be able to switch it 
to a new one-to-one Account. You can currently switch to a regular Account, but 
when you blank 
that out, you get back to the one-to-one Account.

Should we ditch the functionality where the one-to-one account gets filled 
automatically? Or 
should we add some way to blank it out for real?

Original issue reported on code.google.com by gok...@gmail.com on 29 Oct 2009 at 1:49

GoogleCodeExporter commented 8 years ago
Should we disallow the creation of a Contact in a one-to-one Account that 
already has a Contact in it? that 
might be a low overhead way to minimize this problem

Original comment by gok...@gmail.com on 29 Oct 2009 at 1:56

GoogleCodeExporter commented 8 years ago

Original comment by gok...@gmail.com on 6 Nov 2009 at 11:41

GoogleCodeExporter commented 8 years ago

Original comment by gok...@gmail.com on 6 Nov 2009 at 11:43

GoogleCodeExporter commented 8 years ago

Original comment by gok...@gmail.com on 6 Nov 2009 at 11:44

GoogleCodeExporter commented 8 years ago
Made it so that a new one-to-one contact can't be related to a one-to-one 
account that already exists.

Original comment by gok...@gmail.com on 9 Mar 2010 at 4:47

GoogleCodeExporter commented 8 years ago

Original comment by gok...@gmail.com on 9 Mar 2010 at 4:47