Skip to main content

#Cicero토론 중인 항목 0개

We recently switched our NPSP org to Google Geocoding for address verification from the Cicero NPSP connector (RIP). It has mostly worked as expected, but I noticed that we've received a handful of

"REQUEST_DENIED: indicates that your request was denied." errors since we switched over a week ago (see below):Google Geocoding Address Verification errors when using # symbolAll of the addresses that were rejected include the # (number symbol/pound sign) character, which is a pretty common shorthand for unit/apt number. I tested and confirmed that removing the # character fixes the issue.

 

Has anyone else come across this issue? If yes, what workarounds/solutions were used? #NPSP #Address Verification Errors #Google #Cicero

답변 1개
  1. 2024년 6월 10일 오후 4:12

    I also came across this issue - but I didn't come up with a solution - just letting you know you're not alone. If you switch the # symbol with things like "Unit" or "Ste" or "Apt," it can verify the record. Thinking about it now, I would think a before-save flow (so it happens before the verification takes place, I think) that replaces the "#" with "Unit" (or some word like that) might work.

0/9000

Just got an email that the Cicero API for NPSP is being decommissioned on June 1st!  Boooo!

Apparently this is a result of the acquisition of Cicero by Melissa Data Corporation. For those affected, what are your plans? Which is better for address verification - Google or Smarty Streets?  For those of us that are losing the super cool legislative data that Cicero provided, is there any good option other than doing a manual export/import/update?   

#NPSP #Cicero

답변 2개
  1. 2024년 4월 9일 오후 8:34

    @Robert Foley I was going to ask the same question, appreciate the update from Cicero. Our government relations team will be grumpy about losing the state legislative district info, but we'll probably use Cicero District Match with periodic batch imports for that moving forward (until another solution pops up).

     

    We haven't decided on next steps yet. We used SmartyStreets on our pre-Salesforce system and it did the trick, so that might be our play. Haven't used the NPSP integration though, so I can't vouch for that. Hopefully it's still functional!

     

    We're also considering whether we'll want to start verifying addresses before they hit Salesforce. Most of our addresses come into Salesforce via FormAssembly web forms, and they have an integration with Loqate that would theoretically pre-scrub incoming addresses. We'll still need to supplement that with District Match batch updates, but it should kind of work.

0/9000

If anyone has any advice, lmk, i see the fields but no data. I also got an email error

"Salesforce reported the below errors as NPSP was attempting to execute its batch jobs, or at a time when it was unable to display error messages directly to a user. It's likely that NPSP was attempting to update summary fields on Accounts and Contacts, but was unable to save certain records. This failure might have been caused by a variety of issues unrelated to NPSP, such as custom code or validation rules."

답변 2개
  1. 2020년 1월 15일 오후 6:21

    Hello @Sunyoung Lie​ !

     

    Check out this spreadsheet of App Comparisons where you can find additional resources about #Cicero​.

     

    There is a section where you can see their blog post about setting this product up in Salesforce as well as a link to reach out for direct support for Cicero.

     

    I hope this helps!

     

    Best,

    Emonni

0/9000