sfdc-SupportDevelopment / npsp

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

1-1 Contact Not Getting Created when not System Admin #312

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.Create Contact with no Org to create 1-1 contact
2.Correctly creating 1-1 Contact as a System Admin.  Not correctly creating as 
any other profile.

What is the expected output? What do you see instead?
1-1 contacts are being created by a System Admin profile but not correctly 
created by any other profile.  

What version of the packages are you using?
Contact/Org Package 2.1.2 

Please provide any additional information below.

I have installed the NPO Starter Pack Contacts/Organizations and have set it to 
1-1 contacts.  It is working fine as a system administrator but when I try with 
any other profile, the Organization name is not populating with the contact 
name during create.

My developer and I have checked everywhere possible and can't find the issue.  
Oddly enough, it is working just fine in our Sandbox account. 

My developer checked the debug log in Production and it shows the shadow  
Account has been created but we can't find it anywhere in the database.

I have provided Support login access to the account - Org ID: 00D400000007H9h

We will be going live next week with this and need to resolve the issue soon.

Original issue reported on code.google.com by jshaffe...@gmail.com on 6 Dec 2011 at 2:51

GoogleCodeExporter commented 8 years ago
Can you provide an example Account?  The debug log from a non-Sys-Admin user 
would be very helpful as well.

Original comment by kbro...@gmail.com on 6 Dec 2011 at 3:03

GoogleCodeExporter commented 8 years ago
Hi, thanks for your quick response.

1 to 1 Contacts we tried to create as a non-sys ad user:  
https://na2.salesforce.com/0034000000oWKTv?srPos=1&srKp=003
https://na2.salesforce.com/0034000000oWJQ6

My developer sent me this regarding the debug log:
"I was able to identify the following line, which means that the Account record 
is being inserted too.
DML_BEGIN|[342]|Op:Insert|Type:Account|Rows:1 "

Original comment by jshaffe...@gmail.com on 6 Dec 2011 at 3:22

GoogleCodeExporter commented 8 years ago
Could you have the developer run the full debug log and include that as well? 
If I had to guess, its likely Dupeblocker preventing the insert (as its a 
duplicate name), that's a common issue, but I can't be certain until we can 
examine the whole log for a non-admin user. You can also grant login access to 
a non-admin user and I can check that way as well.  

Original comment by kbro...@gmail.com on 6 Dec 2011 at 3:28

GoogleCodeExporter commented 8 years ago
Here you go.

Original comment by jshaffe...@gmail.com on 6 Dec 2011 at 3:38

Attachments:

GoogleCodeExporter commented 8 years ago
So there's a two things:
1.  Dupeblocker can often cause this issue, it might be good to test turning it 
off completely temporarily, and see if that resolves the issue. 

2.  There is an older version of the Nonprofit Starter Pack (its actually 
pre-NPSP) that may be interfering with the code, its called 'Donations and 
Fundraising 2'. You'll want to remove that completely as well.

Original comment by kbro...@gmail.com on 6 Dec 2011 at 3:45

GoogleCodeExporter commented 8 years ago
Ok, I tried to disable all the scenarios in Dupeblocker by indicating "Do 
Nothing" but still a problem.

when I try to uninstall the package you reference, it is saying that many of 
the pieces are in use and can't uninstall.  See image.  Doesn't seem like I 
would be able to remove that package without messing with the other packages.

Original comment by jshaffe...@gmail.com on 6 Dec 2011 at 3:57

Attachments:

GoogleCodeExporter commented 8 years ago
You may need to remove certain links and components from existing page layouts, 
etc. to completely remove the package. You'll just need to work through the 
dependencies listed, but it will not have an effect on other packages (that's 
the design of the managed package)

Original comment by kbro...@gmail.com on 6 Dec 2011 at 4:02

GoogleCodeExporter commented 8 years ago
well, unfortunately, after all of that, it didn't work still.  any other ideas?

Original comment by jshaffe...@gmail.com on 6 Dec 2011 at 5:11

GoogleCodeExporter commented 8 years ago
Well, it took completely uninstalling Dupeblocker to get this to work.  So not 
sure if I will ever be able to install dupeblocker for this Org or not.  Have 
you ever heard of that? 

Original comment by jshaffe...@gmail.com on 6 Dec 2011 at 5:59

GoogleCodeExporter commented 8 years ago
That's a common issue, their triggers are setup to block Accounts that appear 
to be duplicates, which a 1x1 Account is.  You can generally avoid it by very 
carefully setting up your rules, though I'm not certain of the exact setup. You 
can also consider using the Individual Account Model as well.  It may also be 
helpful to post to this forum and see if others have found ways to workaround 
the issues:
http://groups.google.com/group/npsf

Original comment by kbro...@gmail.com on 6 Dec 2011 at 6:02

GoogleCodeExporter commented 8 years ago

Original comment by kbro...@gmail.com on 6 Jan 2012 at 7:24