Error: only one primary phone type allowed per type - when processing profile update transactions

When trying to process profile updates including replacement phone numbers in the NetCommunity plugin, an error message may be displayed "only one primary phone type allowed per type" and the transaction does not process.

When the constituent record is opened no primary phone types are ticked.

 
We have evaluated this issue as a bug and we have determined it will not be addressed in the program in its current state. In this case, we believe the risks and challenges outweigh the potential benefit of resolving this issue. We strive to select the most impactful changes and issues to address with each release to accelerate the rate at which we deliver new features while sustaining the highest level of quality for our customers.


If you encounter this message when processing profile updates, review the following tips to help resolve this message: 

1. Remove the duplicate phone type or manually update the constituent record. If there are no duplicates, proceed to the following steps. 


2. If there are only phone (phones, emails, links, etc.) in the plug-in, move the dot at the bottom to "Add the downloaded information as a new address for this constituent." and process the transaction. (Note: If there are just phone (phones, emails, links, etc.) updates, then this won't affect the existing preferred address in RE 7.94 and higher.)


3. If there are address and phone updates to process:
  • Note the address updates (screenshots, separate screen, etc.) 
  • Open the constituent from the plug-in
  • Manually update the address
  • Save and close the constituent
  • In the plug-in, uncheck the option to process the address update
  • Move the dot at the bottom to "Add the downloaded information as a new address for this constituent."
  • Process the transaction

4. If you are hesitant about processing the update through the plug-in when this message appears:
  • Note the updates needed (screenshots, move to other screen, etc.)
  • Open the constituent from the plug-in
  • Make any updates manually to the record
  • Save and close the constituent record to return to the plug-in
  • Delete the transaction from the plug-in

5. If the steps above do not resolve the message, close the plug-in, edit the constituent record outside of it, and then return to the plug-in to process or delete the transaction. 
 

Steps to Duplicate

  1. Log onto RE Database
  2. Browse to NetCommunity plugin and profile updates.
  3. Process transaction for affected record.

Environment

 Blackbaud NetCommunity
 6.64

Was this article helpful?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.