Skip to main content
The First Step
December 4, 2024

NetSuite contact matching conflict

  • December 4, 2024
  • 14 replies
  • 485 views

Good afternoon, support team,

 

We are in the progress of deploying the RingCentral CRM extension in NetSuite ERP as a replacement of soon decommissioned Tenfold CRM adapter (end of December 2024).

While testing the RingCentral CRM extension, we came across the significant roadblock which doesn’t allow to recognize the contact record for log of call registration (on the level of contact)

Issue

After completing the call from NetSuite contact record, user gets the below error message.

The call log is then not registered neither on the contact level (for obvious reason of not being able to find the match), or on the company level either.

Error message

 

Scenario

This event occurs in the scenario when company record hosts multiple contact records with the same “Main Phone”. When user is calling the main line from the contact record - the activity is not recognized due to the missing match.

Company view - list of contacts

 

Native NetSuite behaviors governs the main phone number on the contact level. Contact form is designed in such a way that it pulls main phone number of the company into the main phone field of the contact record. The field id is also the same.

 

Root cause analysis

We believe that RingCentral extension does not find a match of the CRM contact to register the call log because it searches the contact by the Main Phone field, which could be 1 to Many (as Native NetSuite workflow) as illustrated above. 

 

Complication 

With the above described scenario, we are having issue of releasing the extension back to the sales force as a replacement of Tenfold adapter, simple because large portion of calling activity will not be recognized in the ERP as a registry of CRM call.

 

Reaching out to the community to verify if anyone is experiencing the same block and was able to find the way around. Any input form the community is very valuable to us.

In parallel we are trying to find a way to contact RingCentral product team to validate this assumption and find the prompt fix to accommodate the tenfold termination date approaching in less than a month.

 

Sincerely,

Julia Nikolaeva

 

 

14 replies

sushilmall
Employee
Employee
January 23, 2025

Hi ​@Julia Nikolaeva

Has this issue been resolved? If not, would it be possible to schedule a call for live debugging?

Thank You

Sushil Mall

The First Step
January 23, 2025

Good day, Sushil, 

The issue still persists. I’ve forwarded the link of my availabilities to your DM. Feel free to book the best time for you at earliest convenience.

 

Thank you,

Julia

ByrneReese
Community Manager
Product Manager
January 30, 2025

@Julia Nikolaeva I understand you met with ​@sushilmall. He reports the problem has been resolved. Can you confirm?

The First Step
February 4, 2025

Good day, Byrne, Sushil,

 

Last week we have received the confirmation from our internal user community that the extension is functioning as expected. We may now proceed with closing the case.

 

Using this opportunity to thank you both for your incredible support and guidance throughout the stabilization stage on our instance. We highly appreciate your strong assistance in resolving issues and maintaining open communication channels during this time.

 

We also had great experience with you advanced support team, Eric Pada, whose extensive care for our case and continuous status updates were invaluable.

 

With kind wishes to your team for the great month of February.

 

Sincerely,

Julia Nikolaeva   |   Director MIS

Quadbridge