Bhuvarahan / npsp

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

Data From Previous Record Pre-Populates When Using "Create New..." Button on Sidebar #82

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. View an existing Contact Record
2. Create a new contact, by clicking the "Create New..." button on the sidebar

What is the expected output? What do you see instead?
I expect to see a blank Contact record.  Instead, I see that the
Organization Name is pre-populated with the organization name of the
previously viewed contact.  Sometimes, other fields are populated as well.

What version of the product are you using? On what operating system?
Contacts and Organizations 1.57

Please provide any additional information below.
This problem also occurs with Accounts and possibly other types of records.

Original issue reported on code.google.com by golive...@gmail.com on 24 Jun 2009 at 2:26

GoogleCodeExporter commented 8 years ago
This is actually a Salesforce.com 'feature'. When you have recently visited an 
Account, the account field is 
populated by default. There isn't an easy fix to this that we've come up with.

We tried to override the New Contact button to always blank this out, but it 
caused other problems:

http://code.google.com/p/npsp/issues/detail?id=1

http://code.google.com/p/npsp/issues/detail?id=2

So we removed the override and are living with the default Saleforce.com 
behavior. If you have any ideas of 
how we could better deal with this situation, I'd love input.

Original comment by gok...@gmail.com on 24 Jun 2009 at 5:59

GoogleCodeExporter commented 8 years ago

Original comment by gok...@gmail.com on 24 Jun 2009 at 5:59

GoogleCodeExporter commented 8 years ago
Thank you for looking into this so quickly.  I don't have any ideas on how to 
resolve
the issue.  However, this problem, if not addressed, will eventually compromise 
data
integrity.  I am going to remove the Create New button so that users must use 
the
tabs in order to create new contacts, accounts, etc.  More steps are required 
with
this approach, but at least we eliminate the possibility of users accidentally
linking new contacts to the wrong organizations.  

I'd love to hear how others are addressing the issue.

Original comment by golive...@gmail.com on 29 Jun 2009 at 4:15

GoogleCodeExporter commented 8 years ago
this is standard salesforce funcationality. We fixed the Account name issue--in 
the one-to-one model you 
definitely don't want to put a contact in the last contact's Account. But we 
can't easily fix the UI.

Original comment by gok...@gmail.com on 13 Apr 2010 at 8:48