CRM integration - "Invalid XML File"

[Mark Phillips]

I have created a custom CRM integration using the 3CX Server-Side CRM Template Generator. It works perfectly when testing within the template generator. However, when trying to upload into the 3CX system I receive a beautifully cryptic error "Invalid XML file" with no further clues.

Are there any log files which will help reveal the source of the problem?

The XML checks out with no errors when run through an XML validator.

As a test, I have copied and pasted the XML from one of the other preset CRM integrations into my code editor, saved it as XML and am able to upload it back into 3CX - so this doesn't appear to be a file format issue.

 

[Mark Phillips]

Okay I am making progress.

The "Invalid XML File" error was being caused by the output parameter "Contact::ContactID" - which despite being present as an Output parameter was causing the script upload to fail. The XML description clearly states:

Contact lookup outputs (string): every output generated during contact lookup can be used in the Report Call scenario. For example, if your contact lookup scenario generates an output with name “ContactID”, then you can access the value using [Contact::ContactID]. The prefix “Contact::” is used to reference contact lookup outputs.

However, that is not the case. If I change the Output Parameter to use one of the predefined fields (such as MobilePhone2) then the "Invalid XML File" error is not thrown and the template is uploaded successfully.

Is there a mismatch between the documentation and the functionality V15.5?

 

[Mark Phillips]

It appears the documentation refers to functionality that is only available in V16... it would be really helpful if the documentation made reference to this.

 

[edossantos]

Yes, the documentation is updated including the latest features from v16. Please wait a few weeks for the final release of v16, then you will be able to use all the features.

 

[Mark Phillips]

I have tested with the v16 beta and can confirm everything works as expected. I just wish the documentation had identified thr functionality as v16 only as it would have saved me hours of time trying to get it to work in v15.5sp6

 

[edossantos]

Thanks for the feedback Mark, we will improve the documentation.