Issues with SugarCRM Integration

[Phil-STIC]

Hi,

I am currently facing two issues while integrating SugarCRM with 3CX. Please note, I have created the XML using the 3CX template generator.

1. ContactID Handling:
   When performing either a lookup or contact creation scenario, I receive the ContactID in the response as shown in the attached XML. The issue is that in subsequent scenarios (call creation), I tried many possible ways to pass the ContactID, but it did not work. Can you please provide guidance on how to correctly pass the ContactID in follow-up scenarios to ensure that calls are properly linked to the contacts?
   
   
2. Contact Creation Control:In the contact creation scenario, there is a checkbox that, when enabled, creates a contact. This is functioning as expected. However, I need to run the scenario such that if a contact is found during the lookup, the contact should not be created again. Essentially, I want to restrict the contact creation so that it only occurs when the contact is not found during the lookup. I did not find any settings in the 3CX template generator to make that happen. Can you please advise on how to configure the integration to achieve this behavior?

I have attached the XML response I receive for reference.

Thank you for your help!

 

[edossantos_sipcaller]

ContactID Handling:
When performing either a lookup or contact creation scenario, I receive the ContactID in the response as shown in the attached XML. The issue is that in subsequent scenarios (call creation), I tried many possible ways to pass the ContactID, but it did not work. Can you please provide guidance on how to correctly pass the ContactID in follow-up scenarios to ensure that calls are properly linked to the contacts?

You can't pass values from a contact lookup scenario to another. If you need this, you will need to chain these scenarios. You can pass a variable from a scenario to a "Next" scenario only.

1. Contact Creation Control:In the contact creation scenario, there is a checkbox that, when enabled, creates a contact. This is functioning as expected. However, I need to run the scenario such that if a contact is found during the lookup, the contact should not be created again. Essentially, I want to restrict the contact creation so that it only occurs when the contact is not found during the lookup. I did not find any settings in the 3CX template generator to make that happen. Can you please advise on how to configure the integration to achieve this behavior?

Your SkipIf expression should consider the value of the variable FoundRecordCount. Here you have all the variables you can use:
https://www.3cx.com/docs/crm-template-xml-description/#h.vcivldjsa1lz

 

[Phil-STIC]

Thanks a lot, I'll check it out!

 

[Phil-STIC]

I have one more question, Is there a unique identifier, such as a callID, provided by 3CX for each call record? I need this identifier for creating call records.
I thought it was "EntityId", but this variable refers to the contact ID and is not posted in the call from 3CX to CRM.

Thank you for your help!

 

[Evolute IT]

I have one more question, Is there a unique identifier, such as a callID, provided by 3CX for each call record? I need this identifier for creating call records.
I thought it was "EntityId", but this variable refers to the contact ID and is not posted in the call from 3CX to CRM.

Thank you for your help!

No, there's no Call ID available in the CRM integration. You can always generate an identifier with something like "[DateTime]+[Agent]+[Number]" in a field somewhere in your XML.

 

[Phil-STIC]

Ok thanks for the tip.

 

[Phil-STIC]

@ConceptsWeb , @edossantos_sipcaller

Hello, I'm still stuck and would like to ask for your help once again...

I have successfully implemented the data passing and contact creation check. However, I’m encountering an issue with my scenario chaining. Currently, when a contact is not found, I chain the scenario to contact creation and then to call creation. When a contact is found, the contact creation is halted, but the call creation step is also skipped because the initial chaining skips over the contact creation.

I need a solution to chain two scenarios in the "Next" operation. Specifically, if a contact is not found, it should follow the predefined path for both contact and call creation. If a contact is found, it should skip the contact creation and proceed directly to the call creation step.

Please see the attached XML for reference.

Many thanks for your help.

 

[Evolute IT]

@ConceptsWeb , @edossantos_sipcaller

Hello, I'm still stuck and would like to ask for your help once again...

I have successfully implemented the data passing and contact creation check. However, I’m encountering an issue with my scenario chaining. Currently, when a contact is not found, I chain the scenario to contact creation and then to call creation. When a contact is found, the contact creation is halted, but the call creation step is also skipped because the initial chaining skips over the contact creation.

I need a solution to chain two scenarios in the "Next" operation. Specifically, if a contact is not found, it should follow the predefined path for both contact and call creation. If a contact is found, it should skip the contact creation and proceed directly to the call creation step.

Please see the attached XML for reference.

Many thanks for your help.

Try to enable "AllowEmpty=true" to the Outputs element of your lookup chain. Specially the two first scenarios.