C&P Temporary Contact Merge Error: Too many namespaces accessed: 10

[btaoregon]

We got the following error when attempting to merge a Temp Contact
Too many namespaces accessed: 10
Error is in expression '{!saveItem}' in component <apex:commandButton> in page cnp_paas:temporarycontact: (CnP_PaaS_EVT)
An unexpected error has occurred. Your solution provider has been notified. (CnP_PaaS_EVT)

What would cause this?

[CnP.Support]

Good day!

Please see: https://developer.salesforce.com/for...000000096TrIAI

It seems like you have too many applications trying to perform actions on the Contact. Per Salesforce:

"In a single transaction, you can only reference 10 unique namespaces. For example, suppose you have an object that executes a class in a managed package when the object is updated. Then that class updates a second object, which in turn executes a different class in a different package. Even though the second package wasn’t accessed directly by the first, because it occurs in the same transaction, it’s included in the number of namespaces being accessed in a single transaction."

I recommend you revisit all the applications you have installed that are trying to trigger after creating a contact. While Salesforce allows for installing anything you want to install in the AppExchange it has very strict rules and limitations on how they can be used.

I hope I have answered your question.

Please let us know if we can be of any further assistance.

[btaoregon]

OK. That's clear. Thanks!

[btaoregon]

I got the error again when attempting to merge one particular contact: Adam L. What's the best way to review Applications that are accessing the contact? I'm a bit lost in the DEBUG log...What to search for?

[CnP.Support]

Good day!

The following apps are acting when we try to complete a transaction by processing the Temporary Contact.

1. APXTConga4
2. cazoomi
3. CnP_PaaS
4. GW_Auctions
5. kell01
6. npe01
7. npe03
8. npo02
9. sbxd
10. sbxe1
11. CnP_PaaS_EVT

Salesforce does not allow more than 10 apps to act on an object .

Are you using all these apps?

[btaoregon]

We are using all those apps. I talked to the Auctions for Salesforce folks, and David Habib says that they're not touching the Contact record. Are you sure that's triggering?

[CnP.Support]

Good day @BTAOregon!

Please note that the issue is NOT necessarily the contact object. When a temporary contact is being processed a transaction is being created. A transaction touches the following non-C&P objects (Other namespaces):

• Account
• Contact
• Opportunity
• Products / Price Books if using Opportunity Products
• Campaign
• Campaign Member
• Tasks if set to be created in the notification

As for the Salesforce limits please see the note from Salesforce's manual:

"In a single transaction, you can only reference 10 unique namespaces. For example, suppose you have an object that executes a class in a managed package when the object is updated. Then that class updates a second object, which in turn executes a different class in a different package. Even though the second package wasn’t accessed directly by the first, because it occurs in the same transaction, it’s included in the number of namespaces being accessed in a single transaction."

So if you have any other application touching any of these objects then they count towards the namespace limitations. Needless to say if you are using any field from any application (namespace) in any of these objects it will count towards the namespace involvement, for example adding "Membership" field from another application to the Contact object.

Simply stated- this is not a Click & Pledge issue as we are processing the contacts, etc. as instructed. Other applications are set to act on our actions and their count exceeds 10 per Salesforce limitations.

The following triggers are acting on each of the objects that we touch:

• Account:
  • UpdateContactMembershipFields
• Contact :
  • npe5
  • cazoomi
  • npo02
  • npe01
  • npe4
  • kello2
  • GW_Volunteers
• Opportunity:
  • GW_Auctions
  • npe03
  • npo02
  • npe01
  • kell01
  • sbxd
  • sbxe1
• Campaign:
  • GW_Auctions
  • GW_Volunteers
• Campaignmember:
  • GW_Auctions
  • cazoomi
  • npe4
  • sbxe1
• Task:
  • kell01
• Custom trigger:
  • MakeMembershipForRecurringInstallment using npe03 object

Here are images from your instance & the triggers on each of these objects. We created custom views & deleted them.

Account:



Contact:





Opportunity



Campaign:



Campaign Member:




I hope the above documentation provides assistance for figuring out which ones you can disable or at least postpone to after Click & Pledge has completed its tasks.

Please let us know if we can be of any further assistance.